On Tue, Jul 29, 2003 at 09:11:15AM -0700 it came to pass that Mr. Nobody wrote: > I don't think it's worth adding extra overhead to lexical variables just to > support broken pasm. There are many ways to crash parrot with bad code - but > it's OK, since compilers of higher level languages simply won't generate > them. :)
I would call an "if (!pad) return 0;" hardly extra overhead (4 instructions on an Intel x86). There is a lot of stuff you can not do if this is the sort of overhead you are worried about. I was unaware that the entire parrot VM can crash due to bad code. I would argue that this is undesirable behaviour, because compiler writers are not perfect (as your smiley seems to indicate... :) I'd rather have a parrot thread crash with a more or less intelligeble error code than have the entire VM crash. However, this is a discussion that deserves a place (as far as it has not already taken place) of its own instead of being tagged to an unimportant issue such as this one... Anyway, the problem is obvious and so is the "solution". I leave it to the parrot gurus whether to include it in the source tree or not... ++Jos.es -- ek is so lug jy vlieg deur my sonder jou is ek sonder patroon "Breyten Breytenbach"
