Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!ucbvax!decwrl!orc!mipos3!iwarp.intel.com!news
From: merlyn@iwarp.intel.com (Randal Schwartz)
Newsgroups: comp.lang.perl
Subject: ";#" (was: Re: perl will not open block-special files)
Message-ID: <1990Feb11.202154.25195@iwarp.intel.com>
Date: 11 Feb 90 20:21:54 GMT
References: <1108@etnibsd.UUCP>
Sender: news@iwarp.intel.com
Reply-To: merlyn@iwarp.intel.com (Randal Schwartz)
Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA
Lines: 14
In-Reply-To: vsh@etnibsd.UUCP (Steve Harris)

In article <1108@etnibsd.UUCP>, vsh@etnibsd (Steve Harris) writes:
| Also, in the scripts in the perl library, every comment line begins
| with ";#", not just "#".  Why is this?  (Inquiring minds, etc.)

A file preprocessed with the -P switch can do *nasty* things to lines
that are meant as Perl comment but resemble preprocessor directives.
The ;# is harmless to Perl, and keeps cpp's mits off of it.

Just another Perl hacker,
-- 
/=Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ==========\
| on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III      |
| merlyn@iwarp.intel.com ...!any-MX-mailer-like-uunet!iwarp.intel.com!merlyn |
\=Cute Quote: "Welcome to Portland, Oregon, home of the California Raisins!"=/