The possibilities aren't really that limited. For example, if you want to
read the Nth item in a file, just close it, re-open, and read till you get
there. It may be slow, but it works!

In the early days of computers, almost all data processing was done on
serial access devices. There were all sorts of clever algorithms created to
do this as efficiently as possible. (Merge Sort is one that comes to mind.)

Have a read of the Knuth "Art of Computer Programming" series for example.
I actually really enjoy the challenge of working around the limits of the
language. But maybe I'm a masochist.

Regards
Gordon
<gbe### [at] birdcameroncomau>

Margus Ramst <mar### [at] peakeduee> wrote in article
<36d4436c.0@news.povray.org>...
> 
> Thomas Willhalm wrote:
> >
> >How about writing them to a file with the new #read and #write
directives?
> >There is also a new clock_delta constant. In my opinion, this should be
> >all that you need. (No, I don't have the time to try to write such
macros.)
> >
> 
> 
> This would be plausible, if these directives were a bit more
configurable.
> Right now #read just reads a number of params from the start, you can't
> specify an offset to the read. This severely limits its possibilities.
> Believe me, I've tried.
> 
> Margus
> 
> 
>

Post a reply to this message