#read by whole line - everything gets read into one long string.
This would allow user parsing of the string, regardless of data types,
structure, number of entries, etc.

matrix <>, but allowing x, y, and z in the definitions of the coefficients.
This would allow the desirable but elusive non-linear scaling of primitives, and
well as other interesting transformations such as progressive rotations.
With this, we could "effortlessly" do things with primitives that are currently
only possible with isosurfaces.

Speed parsing - I believe that we currently have mechanisms in the parser to
pretty much ignore everything between /* and */, and anything that starts with
//

The idea would be to selectively / switchably mimic that behavior in order to
"scan" an include file and not have to character-by-character parse every
(unneeded) line.
Kinda like the dreaded GOTO, but since we're progressively parsing a file in a
linear fashion, I think it's appropriate and would be ok.
This is related to the Monolithic Include File idea - I'd want to have the
parser "glance" at the beginning of each line, and skip it until it reached a
block of code that I actually wanted to include.
Perhaps there could be a "file section" designator, where the parser skips
everything, until it hits that.  Like fseek ()

junk
junk
junk
[Parse this]
code
code
[end parsing
junk
junk
eof

Might be a better way to do that, but the key is that everything can reside in a
single include file, and there won't be a million puzzle pieces to get lost.

I had also once suggested support for other file formats to allow "bundling".
Like .tar

Not like this is an original idea:
https://news.povray.org/povray.programming/thread/%3C36C0CEFC.41AEA1BD%40bravo436.chem.mcgill.ca%3E/

- BW

Post a reply to this message