 | | Thoughts sought on final newlines
|
|
A (URL) recent discussion> lead me to observe that Bricksmith saves models without a final newline (ie, CRLF - no "line ending"): (...) Since one line that ended differently from others lead to complications here, I wondered if it might elsewhere. I (...) (17 years ago, 19-Oct-07, to lugnet.cad.dev, lugnet.cad.dev.mac, FTX)
|
| |
| | Re: Thoughts sought on final newlines
|
|
(...) We had a discussion about this item some times ago. I can not find the thread right now. The conclusion was: The user should not mind about that, the programer should. So if you write a prog for LDraw compatible files, you should check for (...) (17 years ago, 20-Oct-07, to lugnet.cad.dev, lugnet.cad.dev.mac, FTX)
|
| |
| | Re: Thoughts sought on final newlines
|
|
(...) I echo Mike. This is a programmers issue (is it honestly that hard to check? I would say no) and not something that should be put into the spec. -Orion (17 years ago, 20-Oct-07, to lugnet.cad.dev, lugnet.cad.dev.mac, FTX)
|
| |
| | Re: Thoughts sought on final newlines
|
|
(...) FWIW I'm pretty sure ldglite saves with a newline (of some sort) after every line. And my opinion is that all programs that *create* ldraw data should do that. It's just common courtesy. After all, we have no control over third party (...) (17 years ago, 20-Oct-07, to lugnet.cad.dev, lugnet.cad.dev.mac, FTX)
|
| |
| | Re: Thoughts sought on final newlines
|
|
(...) I agree fully on this. A text line is not complete until you have specified the end of it (with EOLN). A LDRAW model consists of text lines, and should IMO end with EOLN. Windows expects 'text' files to end with EOLN, and mistreats them if (...) (17 years ago, 20-Oct-07, to lugnet.cad.dev, lugnet.cad.dev.mac)
|
