Bernhard Schmalhofer
2008-11-18 11:44:28 UTC
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #60632]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60632 >
This sounds sane and should be implemented. Takers are welcome.
# Please include the string: [perl #60632]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60632 >
The latest version of Sun's compiler,
cc: Sun Ceres C 5.10 SunOS_i386 2008/10/22
needs the following patch to compile parrot. The problem appears to be
# NOTE: when CONST_STRING gets used it and any macro invocations
# that it is used in *should not* be split across more than one
# line, because some compilers generate line numbers in such cases
# differently from the way gcc does this (a case in point is
# Intel's C compiler, icc) and hence the #defined CONST_STRING
# won't be found by the compiler.
Shouldn't there be a coding standard to enforce *that*?cc: Sun Ceres C 5.10 SunOS_i386 2008/10/22
needs the following patch to compile parrot. The problem appears to be
# NOTE: when CONST_STRING gets used it and any macro invocations
# that it is used in *should not* be split across more than one
# line, because some compilers generate line numbers in such cases
# differently from the way gcc does this (a case in point is
# Intel's C compiler, icc) and hence the #defined CONST_STRING
# won't be found by the compiler.
This sounds sane and should be implemented. Takers are welcome.