Subject:
|
Re: how does a line ends?
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Sat, 7 Apr 2007 23:46:32 GMT
|
Viewed:
|
1842 times
|
| |
|
|
In lugnet.cad, Travis Cobbs wrote:
| |
In lugnet.cad, Ross Crawford wrote:
Thanks, ROSCO. I took that code and modified it to use char instead of
_TCHAR, and got timings of 720-750ms, compared to the 750-780ms I got with
my original one. I then modified it to support CR and LF interchangeably,
and got back to the 750-780ms timings from my original code. So it seems
safe to say that the actual MS fgets function is done differently. (The one
you posted is for _TCHAR, which is two bytes when UNICODE is defined, and
one byte when UNICODE isn’t defined.)
Note that all of my timings have been done in release mode with optimizations
enabled. I’m not going to post any of these test routines due to the fact
that I’m unsure about the copyright restrictions. Sure the MS code is
public, but it doesn’t say to feel free to copy it.
|
Interesting. I looked at the C runtime library sources that came with MSVC++
6.0. The fgets() function there is definitely a little different than either
yours or the one ROSCO linked. It does have a couple calls for thread safety,
but otherwise pretty straightforward. I would assume that the fgets() in the
2005 edition is not much different, even nine years later. They do compare (c
== EOF) instead of calling feof().
|
|
Message is in Reply To:
 | | Re: how does a line ends?
|
| (...) Thanks, ROSCO. I took that code and modified it to use char instead of _TCHAR, and got timings of 720-750ms, compared to the 750-780ms I got with my original one. I then modified it to support CR and LF interchangeably, and got back to the (...) (18 years ago, 7-Apr-07, to lugnet.cad, FTX)
|
24 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
