> > > And about stack level use analysis: as I said, it would be nice if we > had an overview of the worst cases. The assembler file should be a > good base to do this and I thought about it quite a few times too (to > build in perl, that is). But I did not come to it yet. I'll give it > some thought (it is in my head now),
Please give a try with python :) and I'll (or you) be able to add a new action to jallib.py: jallib.py stack file.asm ... Seb -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
