Craig A. Berry:
# The culprit turns out to be the following section of code from
# yyparse in perly.c:
#
# #if YYDEBUG
# if ((yys = getenv("YYDEBUG")))
# {
# yyn = *yys;
# if (yyn >= '0' && yyn <= '9')
# yydebug = yyn - '0';
# }
# else SETERRNO(0,SS$_NORMAL);
# #endif
#
#
# As far as I can tell, the macro YYDEBUG will always be defined to
# true when DEBUGGING is enabled. I would think this would be a
# problem for anything involving errno that also involves parsing at
# run-time, and I don't see offhand why it would be a VMS-only problem.
# Or is it common for folks to have YYDEBUG defined in the environment,
# which would prevent the resetting of errno? There are no occurrences
# of the string "YYDEBUG" in the pod directory and so far I haven't
# found comments in the code that would give me any clue about what it
# is or why it resets errno. Any help appreciated.
YYDEBUG is a Yacc thing. If YYDEBUG is true, Yacc will include code to
emit status messages to help you figure out how the parse is going.
Sorry I can't help you with any of the other stuff--I'm not a VMS
hacker.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
#define private public
--Spotted in a C++ program just before a #include
