To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.nqcOpen lugnet.robotics.rcx.nqc in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / NQC / 382
381  |  383
Subject: 
Re: NQC default output file
Newsgroups: 
lugnet.robotics.rcx.nqc
Date: 
Thu, 13 Jan 2000 20:46:16 GMT
Viewed: 
4607 times
  
I don't think it's nonintuitive.  I think it makes sense to have the output
go to the same directory as the input.  That way you can have a directory
set up for the executable with only read/execute permissions, and yet have
all of your source & object code in another directory with r/w permissions.

At 08:34 PM 1/13/00 +0000, you wrote:
> I was checking to see if NQC already does have an option to spit bytecodes
> to stdout (-L would work, if rcxcomm would understand the format) and I came
> across something that seems nonintuitive to me. The default output file is
> "named the same as the input file, but with an extension of '.rcx' instead
> of '.nqc'", according to the user manual. Wouldn't it make more sense to use
> the basename of the file and output to the current directory?
> 
> In order to test nqc, I was doing
> 
>  jadzia:~$ nqc /usr/doc/nqc-2.1.b2/test.nqc
> 
> and nothing happened! (Oh yeah, this brings up another problem -- if it
> can't write the file, it ought to complain!) When I copied the file to /tmp,
> and did
> 
> jadzia:~$ nqc /tmp/test.nqc
> 
> I ended up with test.rcx in /tmp/, not ~. This is exactly as documented, of
> course, but not what I expect to happen.
> 
> --
> Matthew Miller                      --->                  mattdm@mattdm.org
> Quotes 'R' Us                       --->             http://quotes-r-us.org/



Message has 1 Reply:
  Re: NQC default output file
 
(...) I don't want the outfile to go where the executable is -- I want it to go to the current working directory. So nqc goes in /usr/local/bin, and I can run it from "binaries" directory on source files that might be located elsewhere (the test.nqc (...) (27 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)

Message is in Reply To:
  NQC default output file
 
I was checking to see if NQC already does have an option to spit bytecodes to stdout (-L would work, if rcxcomm would understand the format) and I came across something that seems nonintuitive to me. The default output file is "named the same as the (...) (27 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)

5 Messages in This Thread:


Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR