Thank you for your informative post. Though the point I was trying to make is that Perl has a long story of not-completely-backward-compatible changes and it is not so unreasonable to think of a hypothetic
DEBUG specially named code block, although I bet that would ring a bell amongst p5l's developers. All in all I didn't say that was a problem, just reasoning on the issue. This is a meditation after all, isn't it?
OTOH in your list I see
#define KEY_NULL 0
but that doesn't seem to make its way into Perl. I mean we do not have a NULL specially named block nor special token, have we?
Also I don't see anything about CLONE (I've never used threads myself, BTW) in your excerpt from keywords.h. Maybe it's defined elsewhere...
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.