Le 19/10/2012 06:53, Tim Cook nous fit lire :
> How about adding a #binaryread command or something, that's supplementary?

what would be the usage of it ?
I mean, the SDL is able to handle floating point, vector up to 5
dimensions of floating point, and string of text (and I might be
forgetting some things like square matrix). It cannot handle a binary
blob like a PNG or JPG image or a collection of traced photons directly
(not in a generic way for more manipulation)

#write is there to help you write on the fly files (for simulation:
iteration k-1 saves its data for the next one), as well as easing export.

reading back such file with #read is an option when its content is only
a collection of numbers (which most simulation are just happy with).
more complex files might get in via #include (yes, it's perverse: you
have to spend more time in the #write part to generate a valid SDL
sub-script)

If you expect the SDL to become a multipurpose scripting facility for
importing from something else, I think you might be flogging the wrong
horse.

Post a reply to this message