Bruce Gray:
# Having said that, I see that nested "#ifndef __GNUC__",
# #ifndef __BORLAND", "#ifndef __MARS__", etc will be
# sub-optimal. The better choice is to only make the pragmas
# visible to the specific compiler that understands them. Now
# that I have done more checking, I think that c
[EMAIL PROTECTED] (via RT) wrote:
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #19516]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19516 >
Whitespace sensitive imcc issue...
Thanks for
Bruce Gray (via RT) wrote:
# New Ticket Created by Bruce Gray
# Please include the string: [perl #19511]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19511 >
Thanks applied.
leo
At 10:00 PM -0600 12/27/02, Bruce Gray wrote:
[cc'ed to Brent Dax for his specific attention]
On Fri, 27 Dec 2002 20:34:33 -0500, "Dan Sugalski" wrote:
At 1:22 AM + 12/27/02, Bruce Gray (via RT) wrote:
The gcc compiler in MinGW (win32) emits warnings for invalid
pragmas in win32.h (platform
Do you have a recommendation between GLOBAL and LXR?
I'd suggest LXR. It understands perl files out-of-the-box, is more
easily modified (it's written in perl, and does jit html generation),
and handles cvs. Downsides are a greater system complexity (it's
database-backed), a more involved inst