NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
That compiler tutorial...? (Score:1)
My main remaining problem now is to reliably recognize the code sections. They start and end with lines of Pascal comments containing nothing
Re:That compiler tutorial...? (Score:1)
I've been thinking about that. My first (hackish) solution was to add a <P> to any line that ended in a } or a ;, and then add a <BLOCKQUOTE> wrapper around every begin/end pair.
The results are easy to read but not monospaced. I realize it's a crappy solution, but it works. (Realistically, I should be writing a really thin parser, and maybe I will someday, but this is a one-shot job, etc.)
The results look like this:
***
{-----------------------------------------------------
------------------------------
You are what you think.
Style (Score:2)
I like your little conversations between self and me; it's effective for communicating in this medium. However, to an OO purist, shouldn't that be "self," and "this"? :)
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Re:Style (Score:1)
------------------------------
You are what you think.
Couldn't resist (Score:2)
"Screen on!"
"Text off!"
"How are you, gentlemen?"
"Take off every text!"
Please, somebody stop me, before I get hurt. I've never made an all your base are belong to us joke before...
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers