i am not sure i understand the problem right but either way, did you mention
it to the developers? it sounds like something rather easy to fix (at least
for them)
On Fri, Jan 7, 2011 at 3:01 PM, Eli Billauer <e...@billauer.co.il> wrote:
> Gabor Szabo wrote:
>
> I don't understand. Is this FUD or do you have real examples?
>
>
> Google "Perl crash". Plenty of them. Which is a natural consequence of
> making changes in the code. We seem to agree on that:
>
> Sure any piece of code can - including the perl interpreter - will have bugs
> and new bugs might be introduced and it is always annoying to find that out
> but if the code is not touched then it won't make any progress either.
>
>
>
> As for the new fantastic feature,
>
> if ($condition) { ... }
>
> being equal to
>
> if ($condition) { die "not yet implemented" }
>
>
> Did that addition break your code?
>
>
>
> I didn't say it did. What I did say was that every programmer now has to
> know about this, or otherwise he or she will run someone else's script or
> module, get the "not yet implemented" message, and have no idea where it
> came from. I mean, the first thing I would do is to search the code for that
> string, and not find it. And then the modules. And submodules.
>
> And there's always the slim chance that this change happened to be the one
> causing a crash. Like any change. If this is what you call progress
> justifying playing with the code, we seem to differ.
>
>
> Eli
>
> --
> Web: http://www.billauer.co.il
>
>
> _______________________________________________
> Perl mailing list
> Perl@perl.org.il
> http://mail.perl.org.il/mailman/listinfo/perl
>
_______________________________________________
Perl mailing list
Perl@perl.org.il
http://mail.perl.org.il/mailman/listinfo/perl
