[M3commit] CVS Update: cm3

Tony Hosking hosking at cs.purdue.edu
Fri Apr 9 18:59:24 CEST 2010

What's all the stuff in m3core/src/context?
If it is only for Windows why doesn't it go somewhere with all the Windows code?
I fear that the directory structure has become a little disorganised.

On 9 Apr 2010, at 11:28, Jay Krell wrote:

> CVSROOT:	/usr/cvs
> Changes by:	jkrell at birch.	10/04/09 11:28:42
> Modified files:
> 	cm3/m3-libs/m3core/src/: m3core.h 
> 	cm3/m3-libs/m3core/src/context/: tcontext.c 
> 	cm3/m3-libs/m3core/src/runtime/POSIX/: RTSignalC.c 
> 	cm3/m3-libs/m3core/src/thread/PTHREAD/: ThreadPThreadC.c 
> 	cm3/m3-libs/m3core/src/time/POSIX/: TimePosixC.c 
> 	cm3/m3-libs/m3core/src/unix/Common/: Ugrp.c Unetdb.c Usocket.c 
> 	                                     UtimeC.c 
> 	cm3/m3-libs/m3core/src/unix/Common/context/setjmp/: tcontext.c 
> 	cm3/m3-libs/m3core/src/unix/Common/context/sigaltstack/: 
> 	                                                         tcontext.c 
> Log message:
> 	in general remove the use of "typedef struct foo foo_t"
> 	or at least the subsequent uses of foo_t
> 	While I strongly favor this style -- terse typography
> 	to indicate a type -- it is just not worth the risk
> 	where we don't have adequate control to ensure it will work.
> 	Sun has introduced the same typedefs in some cases,
> 	which is somewhat noble of them, but then we get warnings.
> 	In this step, the actual typedefs remain, just the uses gone.

More information about the M3commit mailing list