Mail Archives: djgpp/2001/10/16/10:49:01
ROLAND <roland_asmann AT yahoo DOT com> wrote:
>> To avoid that, you should supply an action for this
>> rule, so Bison
>> doesn't have to insert a "default action" for you:
>>
>> iunit: label {}
>>
> I'm afraid it doesn't work for me.
> I also left out a part of the BSION-code.
There's really not much sense left discussing this in the DJGPP newsgroup.
This is strictly Bison-specific, now, so please ask any further questions
in a different newsgroup.
> This is the correct code:
[...]
No, it isn't. That's still *far* from being complete enough to be able
to reproduce the problem, so nobody will be able to help you with
this.
> And furthermore, I now have trouble with the commands access and
> stat.
Access() and stat() aren't "commands", they're library functions.
Please try to get your terminology right.
[...]
> Here is the code where things go wrong:
> if (access(cnffilename, R_OK) != 0 ||
> stat(cnffilename, &pathstatus) != 0 ||
> (pathstatus.st_mode & S_IFMT) != S_IFREG) {
Again, this snippet is far too small to offer any meaningful help
about it. For starters, you don't give any idea what the contents and
type of variable "cnffilename" might be. Only a rough guess remains
possible: it could be a filename that's outright illegal on a DOS
platform, e.g. a name starting with a '.', on raw DOS.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -