Wasn't you the one that wanted to reduce the amount of syntax in Pike?
Yes, but who said I had to make sense? :) Seriously, after using python for a while, I've realized that the pike range operator isn't very good...
Completely different topic: How was breakpoints supposed to work in unbug in principle? What role did the now disabled F_BREAKPOINT play?
Simple: Modify the byte code and insert an F_BREAKPOINT, then set a GDB breakpoint in o_breakpoint(). If I remember correctly, it then used a breakpoint inside the interpreter to ensure that it could put back the original opcode, execute it, and then put the F_BREAKPOINT back again...
/ Fredrik (Naranek) Hubinette (Real Build Master)
Previous text:
2004-01-23 01:31: Subject: Re: Sql interface
Wasn't you the one that wanted to reduce the amount of syntax in Pike?
Completely different topic: How was breakpoints supposed to work in unbug in principle? What role did the now disabled F_BREAKPOINT play?
/ Martin Nilsson (saturator)