In article <401aeca9@news.povray.org>, war### [at] tagpovrayorg says...
>   You would be downgrading the versatility of the #read command. You would
> have to turn off almost all interpretation of the input data, which would
> break many things badly.
> 

Just my own 2 cents, but A) if you can't get it to do what you want, how 
is that versatile? and B) last I checked #read is used for pulling in 
data from a file, not SDL, which is more normally included with and 
'include' directive.

What you seem to be implying is that both the SDL parser and the #read 
command use the same system to retrieve data and that because of this it 
ignores the rules used by probably 90% of all programs, which nearly 
universally consider newlines as a break in the data. Now, if this was 
BASIC, I would shrug my shoulders and use a 'lineinput' command, then 
something else to split the line into the correct data. However, your 
'versatile' command can't do that either. The reality is it works one way 
and one way only, and the way it works is broken for the output of most 
programs you want to use it with. Unlike AngleWyrm though, I think a 
better solution is some sort of line-input type command that will 
actually read only up to the break. Combined with something like the 
split command most languages have, you could break each such line up any 
bloody way you want.

Versatility implies the ability to deal with *any* data, not just the 
stuff you think everyone should be using imho.

-- 
void main () {

    call functional_code()
  else
    call crash_windows();
}

Post a reply to this message