On Nov 14, 2005, at 21:06, Nick Glencross wrote:
While nesting one begin/end line number directly inside another doesn't make much sense, my reasoning for this is for inlining of code where you nest a new filename/line/column and then these are popped to get back to the original calling location.
Either your compiler emits proper line/file directives for nested stuff or parrot handles these, if there is an .include "file". I don't see any reason to need kind of some end-directives.
So instead of .end-foo 1 .begin-foo 2 a simple: .foo 2 ought to be enough. Whenever foo changes, set a new value, done.
I also see your point about statements/line numbers, but again begin/ends can of course be arranged to model this too.
That's overkill and code bloat to me - sorry.
Nick
leo
