Subject:
|
Re: LF vs. CRLF in server .DAT script
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Tue, 2 Mar 1999 07:15:42 GMT
|
Viewed:
|
975 times
|
| |
|
|
Re: CR/LF, what a waste of bandwidth! 1/2 :)
Re: \010: Was it really a GPF? LDLite should have hit the
characters, recognized them as garbage, and ignored the
line, and maybe exit-ed without doing anything. If it was a
GPF, I'll try and duplicate the problem.
-gyug
Todd Lehman wrote:
>
> [Added lugnet.cad.dev & lugnet.cad to newsgroups list; followups set to
> lugnet.cad.dev]
>
> In lugnet.admin.general, wilsonj@xoommail.com (jonathan wilson) writes:
> > i have discovered an anoying problem with lugnet.cad.dat • [...]
> You're right -- the data being output by the ldraw.cgi script was only using
> LF when it should have been using CRLF. The script was written specifically
> to work with LDLITE, which handles plain-LF newlines, but since LDLITE can
> save files to disk and since LDRAW and LEDIT are DOS programs, CRLF is better
> all-around. LDAO is a Windows app but Windows still uses CRLF. • [...]
> p.s. Paul: while testing the change to the script, I accidentally wrote
> print "$_\013\010";
> when I meant to write
> print "$_\013\012";
> \010 is ASCII backspace and it caused LDLITE 1.5 to GPF on me. No biggie but
> you probably wanna know.
|
|
Message has 1 Reply:
 | | Re: LF vs. CRLF in server .DAT script
|
| (...) Indeed! Full-on :-( (...) Oh. Sorry, it probably wasn't a GPF. After all these years I'm still in the habit of saying something "GPF'd on me." I don't even think that's what MS calls it anymore. Well anyhow, the screen flashed and then LDLITE (...) (26 years ago, 3-Mar-99, to lugnet.cad.dev)
|
Message is in Reply To:
6 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
