On Tue, Nov 27, 2001 at 07:18:43PM -0500, Christopher C. Chimelis wrote:
On Tue, 27 Nov 2001, Daniel Jacobowitz wrote:
I look at this differently; it's our job to be accepting and GCC's job
to be conformant. With Joseph and others actively deprecating
extensions, that seems a better
On Tue, 27 Nov 2001, Daniel Jacobowitz wrote:
As with that bug, no, GCC should complain about dollars starting
identifiers. Try using b$c instead of $b.
Oddly enough, our powerpc gcc packages have --no-dollars-in-identifiers
enabled by default, despite gas having no problems handling things
On Tue, Nov 27, 2001 at 01:33:25PM -0500, Christopher C. Chimelis wrote:
On Tue, 27 Nov 2001, Daniel Jacobowitz wrote:
As with that bug, no, GCC should complain about dollars starting
identifiers. Try using b$c instead of $b.
Oddly enough, our powerpc gcc packages have
You won't be able to build X86 kernels if you do that :) Well, not
with things like NTFS support, at least.
That isn't really true, is it? Atleast in the NTFS code, I cannot find
such code (and I can't remember writing it, either :-).
I'm most strongly of the opinion that this isn't
On Tue, 27 Nov 2001, Martin v. Loewis wrote:
According to the GCC documentation, the rationale for this feature is
that traditional C allows it, but ISO C and ISO C++ disallow it.
So I'd say that, if all Debian packages either build fine without it,
or enable it when needed, turning it off
On Tue, 27 Nov 2001, Martin v. Loewis wrote:
That isn't really true, is it? Atleast in the NTFS code, I cannot find
such code (and I can't remember writing it, either :-).
Hehehe...I seem to remember seeing such code in the kernel source, but
that was some time ago and I haven't looked for it
On Tue, 27 Nov 2001, Daniel Jacobowitz wrote:
I could have sworn it was NTFS...
util.h:
typedef enum {
FILE_$Mft = 0,
FILE_$MftMirr = 1,
etc.
I'm fairly certain that DOLLARS_IN_IDENTIFIERS affects the legality of
that enum.
Yes, it does and you're correct.
7 matches
Mail list logo
