Hi Klaus,
(Saturday May 09 1998 20:00) Klaus Meinhard to Ted Menks about: parsing
 TM>> But how does one go about it, when there's a greater number of
 TM>> different parameters on each line? The only ways I found to "parse"
 TM>> such a line of data, is by:
 KM> Well, what comes to mind is: give every data field a fixed length and
 KM> parse that with @instr. Should do the job, no?
Thanks, Klaus. That's a good one.
I can tell you exactly why I didn't think of that myself...
1. It'll make the parsing routine rather longwinded (unless I'm overlooking
   sumpin' ofcourse )
2. As soon as the syntax becomes a bit more complicated than the average, 
our
   option would tend to make for rather long lines in the datafile, 
onsisting
   of a lot of white-space.
But just now I'm thinking about something else: what would happen if we'd 
check the line for embedded "" and ``, and then eventually set up a 
parsing-section where @word uses only " and ` as word-separators?
I'm not sure if this would offer us a short, fast solution (which is what I'm 
always looking for), but is there any other reason why it wouldn't work?
(This brain-storm is really *happening*... )
{
  Hello, Peter H. are you with us? Any idea's? It might help improve IniRead, 
 and would help me actually *make* IniWrite   :)
  No, I didn't forget... I'm still working on it... It's just not going 
anywhere yet... :(
}
Prosperity and a long life,
  Ted Menks  2:2449/236.51 / 2:284/412.51  PGPkey: 2048/1B2ACCED (by RRQ)
... If at first you don't succeed, have somebody else do it for you!
--- 4Dos v6.01a ---
(2:2449/236.51)
---------------