MichaelJF <mi-### [at] t-onlinede> wrote:
> 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.
> >

> 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.

I understand what you want, I was simply answering why #read was designed
as it was.

-- 
                                                          - Warp

Post a reply to this message