Ok, that sounds great, but doesn't solve the problem of MMC don't accepting TRACE statements with more than one parameter if I understand you correctly.
/H
Rob Bateman wrote:

i use a modified version of powerflasher's SOS debugger
(http://sos.powerflasher.com/)

in the showMessage method of the AbstractSocket class you can add a
trace() function that is ignored by mtasc but will output trace
statments using MMC.

Rob

On 9/1/05, Kelvin Luck <[EMAIL PROTECTED]> wrote:
Hmmm - not sure if you could use the hacked version of MTASC and the
ASSERT command as described here?

http://osflash.org/doku.php?id=mtasc_hacks

Not sure if ASSERT gets passed the class, file and line number that
TRACE gets but it could be worth a try...

Henrik Lindahl wrote:
Hi.
I need to be able to switch between compling with MTASC (with -trace)
and MMC. This is not possible for me right now as MMC complains about
too many parameters to trace().
Has anyone solved this?
-- Can trace be fooled to accept TRACE calls with 2 or more parameters
(and obviously loose line numbers etc.)? Is there another way to do this?
-- Is preprocessing an alternative? How should that be done?
-- MTASC hack to call TRACE something like MyTRACE and  then define a
dummy MyTRACE that MMC can compile against?

_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org





_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to