diff options
| author | nanbor <nanbor@ae88bc3d-4319-0410-8dbf-d08b4c9d3795> | 1998-05-05 08:04:33 +0000 |
|---|---|---|
| committer | nanbor <nanbor@ae88bc3d-4319-0410-8dbf-d08b4c9d3795> | 1998-05-05 08:04:33 +0000 |
| commit | 8afe7419bf8678e1b0afc02044a174b85ba0fb9c (patch) | |
| tree | 12ee16eb3a2d5b0ccf638e3f99124a35691159e6 /docs/CE-status.txt | |
| parent | b535149d98a90b0ba64065e71dadb18d40f3cf51 (diff) | |
| download | ATCD-8afe7419bf8678e1b0afc02044a174b85ba0fb9c.tar.gz | |
*** empty log message ***
Diffstat (limited to 'docs/CE-status.txt')
| -rw-r--r-- | docs/CE-status.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/CE-status.txt b/docs/CE-status.txt index 28f48609a6a..1b54b9c5c2d 100644 --- a/docs/CE-status.txt +++ b/docs/CE-status.txt @@ -7,8 +7,8 @@ simple conversion. However, the tricky part here is, FILETIME is the total 100ns elapse since _1601_ (why the heck did Microsoft choose this time?) whereas POSIX timeval gives you the - accumulated time since 1970. This leads to data overflow in - timeval struture which ACE uses internally for its + accumulated time in us since 1970. This leads to data overflow + in timeval struture which ACE uses internally for its ACE_Time_Value. This also confuses ACE_OS::ctime, which, under CE, is a home-brewed implementation, and corrupt the whole program image. I don't know of a way to deal with this yet |