Does '#ident' really have the same semantics as '#undef'? Or
would it be more sensible to just ignore it?
That was what I was trying to do. Perhaps I failed. I didn't
really understand what the #undef code did. I just made a
qualified guess.
If ignoring is the answer I would
Francois Gouget wrote:
[snip]
But I would like to point out that even if you use gcc as the
pre-processor, as I did, wrc must still be aware of some directives
like '# line file' and '#pragma'. I seemed to me that this was not
always clear in the messages.
Yes, it was clear to me and
"Dimitrie O. Paun" wrote:
Indeed. The problem is that wrc has a semantical preprocessor instead of
a lexical preprocessor.
Why don't we simply use gcc preprocessor?
Because not everybody uses/has gcc to compile wine...
Greetings Bertho
Indeed. The problem is that wrc has a semantical preprocessor instead of
a lexical preprocessor.
Why don't we simply use gcc preprocessor?
Because not everybody uses/has gcc to compile wine...
And a 'standard' cpp would not do? (use autoconf magic: AC_PROG_CPP)
Ciao, Marcus
Why don't we simply use gcc preprocessor?
Because not everybody uses/has gcc to compile wine...
This is certainly NOT a reason:
(1) who is compiling Wine with anything else? Can it be done?
(2) they may not have a Unix OS to run it for. This does not mean that we
include a Unix like OS
Why don't we simply use gcc preprocessor?
Because not everybody uses/has gcc to compile wine...
This is certainly NOT a reason:
(1) who is compiling Wine with anything else? Can it be done?
I do. WineLib works fine with Solaris C.
Wine works for some applications using a gross hack
Patrik Stridvall writes:
It is a little more sensitive than the GNU C preprocessor,
it doesn't like lines ending with "\r\n" for example
but I can fix that it you decide to use it for wrc.
Developpment versions of GCC has to my knowledge some switch to make
them understand "\r\n", however
Fortunately, standard cpp
seems to be enough, but if we were to require GNU cpp, what
would be the (real) problem???
It is not a real problem but I prefer to minmize the depencies
whenever possible. You have heard the story about
"The straw that broke the {ass,donkey,mule}'s
gerard patel wrote:
At 02:15 PM 3/20/00 -0600, you wrote:
Whatever -- the point is that rewriting and reinvention of the wheel for the
single purpose that it is more convenient to have it included in wine is a
bit silly. We require a C compiler (for now we require gcc with is OK IMO),
Whow, small patch, big discussion!
Sorry for arriving late (the day at the office, time difference,
etc.)
On Mon, 20 Mar 2000, Dimitrie O. Paun wrote:
From: "Bertho Stultiens" [EMAIL PROTECTED]
Indeed. The problem is that wrc has a semantical preprocessor instead of
a
On Mon, 20 Mar 2000, Patrik Stridvall wrote:
[...]
Anyway, I have do some experimentation and I found out that
this simple patch implements a pre wrc call to the C preprocessor.
Works with both Solaris C/CPP and GNU C/CPP.
[...]
Index: wine/tools/wrc/parser.l
[...]
@@ -449,6 +450,14 @@
11 matches
Mail list logo
