On Mon, Sep 17, 2001 at 11:01:32AM -0400, Dan Sugalski wrote: > While I'm not fond of segfaults myself, the place to check isn't in the > interpreter loop. My view is that if you screw up writing assembly code, you should be thankful that you get the protection of a segfault. Same happens if you construct horribly malformed bytecode in Perl 5, as I know only too well. :) -- Writing software is more fun than working.
- [PATCH] Bytecode bounds checking and TRACE_OPS Gregor N. Purdy
- Re: [PATCH] Bytecode bounds checking and TRACE_OPS Dan Sugalski
- Re: [PATCH] Bytecode bounds checking and TRACE_OPS Simon Cozens
- Re: [PATCH] Bytecode bounds checking and TRACE_OPS Gregor N. Purdy
- Re: [PATCH] Bytecode bounds checking and TRACE_OPS Dan Sugalski
- Re: [PATCH] Bytecode bounds checking and TRACE_OPS Gregor N. Purdy
- Re: [PATCH] Bytecode bounds checking and TRACE_OPS Simon Cozens
- Re: [PATCH] Bytecode bounds checking and TRACE_OPS Dan Sugalski
- Re: [PATCH] Bytecode bounds checking and TRACE_OPS Dan Sugalski
- Re: [PATCH] Bytecode bounds checking and TRACE_OPS Gregor N. Purdy
- Re: [PATCH] Bytecode bounds checking and TRACE_OPS Leon Brocard
