|
From: Ethan A M. <merritt@u.washington.edu> - 2006-04-08 19:17:40
|
On Saturday 08 April 2006 11:28 am, Daniel J Sebald wrote:
>
> >> Enable general binary data file reading (EXPERIMENTAL)
> >> Enable X11 polygon info in binary, not ascii (EXPERIMENTAL)
> >
> > I have mixed feelings about these. They do work, but the code is so
> > tangled that at some point we may have to rip it apart and re-do it.
>
> I don't think that is the case.
> [...]
> The implementation of that is hidden behind the scenes at a low level
> such that plot3d/graph3d never needs to worry about such things.
Yeah, but my gripe is with this:
lascaux [333] grep -c 'BINARY_DATA' datafile.c pl*.c
datafile.c:30
plot2d.c:3
plot3d.c:5
The code in datafile.c has become practically unreadable
>> Enable string variables (EXPERIMENTAL)
> I like the string variables,
> I just wish there were some way of incorporating them at a higher level.
> I mean, binary is really meant for large data files in my mind.
> If strings don't work for binary, that's OK.
I think you are confused here. The "string variables" configuration option
refers to support for an internal data type STRING.
It affects mostly command line parsing and expression evaluation. E.g.
myfilename = "datafile_" . sprintf("%g", A+B)
splot myfilename
I am unaware of any bad interaction with binary data files, but if there
is one please let me know.
--
Ethan A Merritt
Biomolecular Structure Center
University of Washington, Seattle 98195-7742
|