From: <Sha...@si...> - 2007-10-05 23:10:52
|
Neil wrote: > I did notice one slight difference of behaviour from what I was > expecting: the GDLPP environment variable points to the *directory* > containing gdlpp, rather than gdlpp itself. This doesn't allow you > to have, for example, a test version of gdlpp in the same directory > as the standard one but with a different name. Not a problem, just > different. If we keep the current behaviour, then maybe the env var > should be called GDLPPDIR? My preference, however, would be for the > env var to point to the executable file, as this is slightly more flexible. Okay, I've changed this so that it always expects a full file name, and if GDLPP is not defined, it will use the directory of the current EXE and assume the name is "gdlpp". > > By the way, this seemed to act a little flaky... > > Could it be due to the presence of spaces in the path to gdlpp? > Either the env var or the location of the compiler. To get around > this, you would need to put double-quotes around the command name in > the command line that is going to be run to invoke gdlpp > (ParserTreeWalker.cpp:123). Don't think I had any spaces in any of the names, but I've gone ahead and put quote marks around the name of the program and the name of the input file, just to be on the safe side. |