[M3commit] CVS Update: cm3
Jay Krell
jkrell at elego.de
Sun Sep 20 22:55:04 CEST 2009
CVSROOT: /usr/cvs
Changes by: jkrell at birch. 09/09/20 22:55:04
Modified files:
cm3/m3-libs/m3core/src/unix/Common/: UnixC.c Usocket.c
Usocket.i3 Utime.i3
UtimeC.c Utypes.i3 m3unix.h
cm3/m3-libs/m3core/src/unix/cygwin/: Usysdep.i3
cm3/m3-libs/m3core/src/unix/darwin-common/: Usysdep.i3
cm3/m3-libs/m3core/src/unix/freebsd-common/: Usysdep.i3
cm3/m3-libs/m3core/src/unix/hpux-common/: Usysdep.i3
cm3/m3-libs/m3core/src/unix/interix-common/: Usysdep.i3
cm3/m3-libs/m3core/src/unix/linux-common/: Usysdep.i3
cm3/m3-libs/m3core/src/unix/netbsd-common/: Usysdep.i3
cm3/m3-libs/m3core/src/unix/openbsd-common/: Usysdep.i3
cm3/m3-libs/m3core/src/unix/solaris-common/: Usysdep.i3
Log message:
Usysdep reduction
idealize time_t as INTEGER
actually I'd like to make it LONGINT
So far I haven't seen a 32bit Posix system with a 64bit time_t.
I think I've seen even 64bit Posix with 32bit time_t!
32bit Cygwin is threatening to go that way.
Windows already is this way by default.
They really all should.
LONGINT might be source incompatible so holding off on that.
and then all the related structs -- timespec, timeval, itimerval
This involves "copying wrappers".
And since the conversion functions are static in UtimeC.c,
move select and utimes wrappers to there.
split up Unix__Assertions into Unix__Assertions, Usocket__Assertions,
Utime__Assertions
We assert that struct linger can be passed through, except on Cygwin
and that timespec, timeval, itimerval are all as we expect
We will probably soon be using much less of all this code
but we can maybe leave it for some compatibility.
More information about the M3commit
mailing list