POV-Ray : Newsgroups : povray.beta-test : the read-directive : Re: the read-directive Server Time
20 May 2024 13:03:57 EDT (-0400)
  Re: the read-directive  
From: MichaelJF
Date: 18 Oct 2012 11:40:01
Message: <web.5080229a399c00aa5b4143310@news.povray.org>
Warp <war### [at] tagpovrayorg> wrote:
> MichaelJF <mi-### [at] t-onlinede> wrote:
> > > #read was never intended to be a raw byte input stream. Instead, it was
> > > always intended to be used to read comma-separated lists of elements.
> > >
> > I can not see a reason for that.
>
> The reason is that reading a list of comma-separated values is very easy
> with #read. You don't have to parse anything.
>
> --
>                                                           - Warp

Hm, I think you didn't understand me. I will parse everything, or better I would
like to able to. Technically I can see no reason to use the comma or the \n as
seperator. Maybe there is a problem between the operating systems. What I would
like to do is to parse scene-files, e.g. mesh2 objects, change them and write
them to disk. The latter is possible, MakeGrass or MakeClouds are wonderful
examples for this technique. So please forgive me, that I propose such an
option.

Best regards,
Michael


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.