 | | Re: L3P v1.3 for Mac OSX
|
| (...) I do consider it an error. I have now made an L3fgets that can handle any line ending. I have uploaded an update (URL) try it on the original problem files. /Lars PS. Here is L3fgets, You can use it in ldglite if you like. As Paul DiLascia (...) (22 years ago, 11-Dec-02, to lugnet.cad.dev.mac)
| | | | | Re: L3P v1.3 for Mac OSX
|
| (...) Hey, thanks Lars. Where should I put it? L3Input.cpp, or a separate file like platform.c? Don (22 years ago, 11-Dec-02, to lugnet.cad.dev.mac)
| | | | | Re: L3P v1.3 for Mac OSX
|
| (...) I have put it in L3Input.cpp because I only used fgets there, but if you can benefit from L3fgets() elsewhere you can put it in L3fgets.c or in platform.c as you wish... /Lars (22 years ago, 11-Dec-02, to lugnet.cad.dev.mac)
| | | | | Re: L3P v1.3 for Mac OSX
|
| (...) I guess what I was trying to say (without actually saying it) was "Can I have the latest version of L3Input.cpp?" Don (22 years ago, 11-Dec-02, to lugnet.cad.dev.mac)
| | | | | Re: L3P v1.3 for Mac OSX
|
| (...) Umm, fgets already does what 2) says above (unless you mean when end of file is reached and the function returns NULL). I'm not actually sure what goes into the string when fgets returns NULL. If no line ending is found (either due to EOF (...) (22 years ago, 11-Dec-02, to lugnet.cad.dev.mac)
| | | | | Re: L3P v1.3 for Mac OSX
|
| (...) Right! I must have been sleeping or thinking of strncpy...? Please delete 2) from the comment. (...) According to the CRT source ungetc doesn't use fseek, but with L3fgets the need to open in text mode has gone, so I might as well open in (...) (22 years ago, 12-Dec-02, to lugnet.cad.dev.mac)
| |
