Warp wrote:
> 
> s1631001 <s16### [at] namtarqubacuk> wrote:
> : //$  this tells me I haven't finished this portion of code yet.
> 
>   Time is money? ;)

lol, no; $ is my standard "to do" symbol. I also sometimes use an
upside-down one to represent "don't have to do this!". Of course that's
in RL where I can write anything; in CL I use "z" for that instead...

-- 
signature{
  "Grey Knight"
  contact{ email "gre### [at] yahoocom" }
  site_of_week{ url "http://enphilistor.users4.50megs.com/" }
}

Post a reply to this message

That's a good idea, with the //:P

I hereby stake claim!

I was originally thinking of the /* and */ comments, but using //: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
>
> //@---new section---
>
> //@@---new sub-section---
>
> //@@@---new sub-sub-section---
>
> //#  instructions (how to use macro, etc)
>
> //_  this comment applies to all lines from here...
>
> //^  ...to here
>
> //!  this is really important!
>
> //$  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 "//:x" as a comment
> tag for some program denoted "x". Eg, a particle system could read
> "//:P" tags, so...
>
> //:P  mass(1.0)
>
> --
> signature{
>   "Grey Knight"
>   contact{ email "gre### [at] yahoocom" }
>   site_of_week{ url "http://enphilistor.users4.50megs.com/" }
> }

Post a reply to this message

"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

In article <3c190850$1@news.povray.org> , "John D. Gwinner" 
<jgw### [at] dazsicom> wrote:

> I was originally thinking of the /* and */ comments, but using //:P is
> better, as you can comment out an entire block by using /* and later */

Nested "/* */"-comments are supported in POV-Ray, no need to restrict
yourself to //-comments only for easier cemmenting-out of blocks of
comments.


    Thorsten

Post a reply to this message

Ohhhh my NS newsreader didn't like that. Tried to convert all occurences
of //* into file://* (for all *) Ugly...

-- 
signature{
  "Grey Knight"
  contact{ email "gre### [at] yahoocom" }
  site_of_week{ url "http://enphilistor.users4.50megs.com/" }
}

Post a reply to this message

Grey Knight <s16### [at] namtarqubacuk> wrote:
: Ohhhh my NS newsreader didn't like that. Tried to convert all occurences
: of //* into file://* (for all *) Ugly...

  The funny thing is that, AFAIK, you can't even turn that "feature" off.

  This is what MS considers "easy to use".

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

If you'll note, he said "NS" not "MS".

Not all the crappy software in the world is from MS, *lol*

My MS news reader didn't do it (IE 6) and is a bit more stable too.

In any event, I don't think we have to worry about it, // comments have been
in POV files (and C++) for a while ...

                  == John ==

"Warp" <war### [at] tagpovrayorg> wrote in message
news:3c1e1fa4@news.povray.org...
> Grey Knight <s16### [at] namtarqubacuk> wrote:
> : Ohhhh my NS newsreader didn't like that. Tried to convert all occurences
> : of //* into file://* (for all *) Ugly...
>
>   The funny thing is that, AFAIK, you can't even turn that "feature" off.
>
>   This is what MS considers "easy to use".

Post a reply to this message

Thorsten Froehlich wrote:
> Nested "/* */"-comments are supported in POV-Ray, no need to restrict
> yourself to //-comments only for easier cemmenting-out of blocks of
> comments.
> 
>     Thorsten

I wonder how POVray parses something like:

/*#declare TheString="random *\n gibberish"*/

-- 
signature{
  "Grey Knight"
  contact{ email "gre### [at] yahoocom" }
  site_of_week{ url "http://digilander.iol.it/jrgpov" }
}

Post a reply to this message