1. OSL and a new submission
Great work, Karl !
It's nice that you increased the size of sequences before
truncation in EX.ERR but what I'd really like to see is a statement to
change this amount programmatically,
say, in the form of:
set_dump_size("varName", size)
or something like that where size=0 indicates no limit. Perhaps, if the
first parameter were "" or 0, it would mean all sequences. Of course, what
we all REALLY, really want is a debugger in which we can scroll through
sequences, with indicators showing what indices a cursor is in, etc. ...big
project, I know. The readable output from '?' is also nice but why did you
choose single quotes instead of double? I did some testing with some very
contrived examples and found your output misleading:
s = {"one","two"}
? s
t = {"thr'ee","fo','ur","fi\"ve","si","","x", {83,69,86,{},69,78},
"eig{ht", {255,78,73,78,69}}
? t
OSL outputs:
{'one','two'}
{'thr'ee','fo','ur','fi"ve','si',{},'x',{83,69,86,{},69,78},'eig{ht',{255,78,73,78,69}}
The ... ,'fo','ur', ... would be mistaken for two sequences
instead of one because of the single quotes.
Anyway, I'm submitting a program I wrote in October called
FIXERR.EX which processes EX.ERR to a more readable form. The format I
chose is different from yours.
My program outputs (after processing EX.ERR from EX.EXE, NOT from OSL.EXE):
s = {{`one'},{`two'}}
t =
{{`thr'ee'},{`fo','ur'},{`fi"ve'},{`si'},{},{`x'},{`SEV',{},`EN'},{`ei
g{ht'},{255,`NINE'}}
In my notation, braces ( '{' and '}' ) are the only symbols used
to denote sequence boundaries. Thus, in the example above, ...
{255,`NINE'} ... is a single sequence. I sometimes preface strings with
a tag like this so it helps me in debugging. I may add code to give a
choice between this notation and a more conventional one like yours but the
program was fairly difficult for me.
Bob
