Hi,

> Sorry,    I thought that the problem was with the COBOL program,  I was doing a

That's ok ... I thought it made for an interesting problem!

> I'll try to be more descriptive next time.

It's hard to know what information is important, and what information
isn't.

I spent a long time trying to understand an early SPLash! bug report,
where I heard the user on the phone saying that
   "if <expression> then ; else"
wasn't ignoring the semicolon like SPL did.  I hadn't realized that SPL
did this, so I entered it into SPL and got a syntax error, yet
the user insisted he didn't get an error.  (BTW, that's the only example of error
correction that the SPL compiler has.)

It took a long time before I realized that case might matter.  Sure enough,
the user was typing "; ELSE", and I was typing "; else" ... and SPL
was stupid enough to only handle all-uppercase "; ELSE".  The point is that
there was extra information available, but I didn't know enough to ask for it.
That's why I usually try to get people to cut/paste screen examples (although
that's harder in a multi-computer problem like the carriage return one).

--
Stan Sieler                                          [log in to unmask]
                                         http://www.allegro.com/sieler/