Re: [BLACKBOX] Possible compiler bug ?

From: [at]} <Aubrey.McIntosh{>
Date: Mon, 19 Dec 2011 20:28:46 -0600

The source debugger idea arises every few years. The members close to ETH express a fairly strong view that interactive debuggers lead to poor design practices, and that the trap viewer works very well. We found and fixed a compiler error in only a few email messages in 48 hours, this is astonishing.

I sometimes wonder about a special marker so that we can recompile a source to set (multiple) breakpoints, but an
  ASSERT(~debugThis IN debugModelist)
works with the system as it is, preserves an audit trail. I put such constants in a bottom level module.




On Mon, Dec 19, 2011 at 8:05 PM, <luowy{([at]})nowhere.xy


yes,should add this statement!
..

   IF y.mode # Reg THEN LoadR(y);rev := ~rev;END;

..

Does anybody have some idea or suggestion about build a source debugger for BB/Oberon??

add HALT() or Log.XXX is too tedious to trace bug.




----- Ô­ÎÄ -----
·¢¼þÈË: Aubrey.McIntosh{([at]})nowhere.xy
Ö÷¡¡Ìâ: Re: [BLACKBOX] Possible compiler bug ?

ʱ¡¡¼ä: 2011Äê12ÔÂ20ÈÕ 5:25:13

Also, add the statement rev := ~rev IF y.mode # Reg THEN LoadR(y); rev := ~rev END;(* &lt;&lt;&lt; add this line *)

-- 
Aubrey McIntosh, Ph.D.
1502 Devon Circle
Austin TX 78723-1814
http://home.grandecom.net/~amcintosh/aubrey/Search/
---- To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV{([at]})nowhere.xy

Received on Tue Dec 20 2011 - 03:28:46 UTC