[M3devel] [M3commit] CVS Update: cm3

[Tony Hosking]

Jay,

I am particularly disturbed by these changes you just committed  
because of the nasty reliance they impose on C in this part of the  
run-time library.  Part of the beauty of M3 is that its compiler and  
libraries are almost entirely programmed in Modula-3.  Your change  
here has been made to satisfy a need to debug a severely broken run- 
time system.  Better in such situations to use a standard debugger  
rather than pollute the Modula-3 code with nasty reliance on C.   If  
you need to use such hacks in your debugging please do so in your  
privately checked out working directories rather than imposing them  
on the rest of us by checking into the main tree.  If you need a  
debugging source tree in which to play then there is ample provision  
using CVS to fork a development branch that is off the main trunk.   
Shall I undo these hacks or will you?

It is important in a collaborative effort such as this to make sure  
that we all play nicely in the shared CVS space.  In this case I  
think you have regressed the code base by adding these C-based hacks.

Best,

-- Tony

On Jan 20, 2008, at 12:01 PM, Jay Krell wrote:

> CVSROOT:	/usr/cvs
> Changes by:	jkrell at birch.	08/01/20 12:01:09
>
> Modified files:
> 	cm3/m3-libs/m3core/src/runtime/common/: RTLinker.i3 RTLinker.m3
> 	                                        m3makefile
> Added files:
> 	cm3/m3-libs/m3core/src/runtime/common/: RTLinkerC.c
>
> Log message:
> 	allow RTLinker's tracing to work when things are more broken
> 	the default behavior is unchanged, and the behavior with  
> @M3tracelinker
> 	is preserved
> 	a change in behavior requires modifying RTLinkerC.c and rebuilding
> 	this also enables more verbose tracing