"John D. Gwinner" <jgw### [at] dazsicom> wrote in message
news:3c190850$1@news.povray.org...
> That's a good idea, with the file://:P
>
> I hereby stake claim!
>
> I was originally thinking of the /* and */ comments, but using file://:P is
> better, as you can comment out an entire block by using /* and later */
>
>                   == John ==
>
> "s1631001" <s16### [at] namtarqubacuk> wrote in message
> news:3C1### [at] namtarqubacuk...
> > When commenting my files, I often use different "types" of comment
> >
> > //  this is a general comment
> >
> > file://@---new section---
> >
> > file://@@---new sub-section---
> >
> > file://@@@---new sub-sub-section---
> >
> > file://#  instructions (how to use macro, etc)
> >
> > file://_  this comment applies to all lines from here...
> >
> > file://^  ...to here
> >
> > file://!  this is really important!
> >
> > file://$  this tells me I haven't finished this portion of code yet.
> >
> > //?  this piece of code does strange things, but I don't know why!
> >
> > Perhaps you could use something like this? Let's use "file://:x" as a
comment
> > tag for some program denoted "x". Eg, a particle system could read
> > "file://:P" tags, so...
> >
> > file://:P  mass(1.0)
> >
> > --
> > signature{
> >   "Grey Knight"
> >   contact{ email "gre### [at] yahoocom" }
> >   site_of_week{ url "http://enphilistor.users4.50megs.com/" }
> > }
>
>
No comment

--
- Nekar

http://nekar_xenos.tripod.com/metanoia/


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.298 / Virus Database: 161 - Release Date: 2001/11/13

Post a reply to this message