Re: Why except and always should be a seperate RFC.

2000-08-25 Thread David L. Nicol
perl5 sort of already has an C, in that DESTROY() methods are called on any blessed lexicals when the scope closes. Taking advantage of that for closing a file works if you hide your files in an object class or equivalent chicanery. Allowing user code into the list of things that perl does on s

Re: Why except and always should be a seperate RFC.

2000-08-24 Thread Glenn Linderman
Tony Olekshy wrote: > Other than for the except and always clauses, RFC 199 is very > similar to RFC 88. I like the idea behind except and always, > but I think the proposed implementation could be dramatically > simplified. > > The first thing to realize is that just because 119 doesn't say > "

Why except and always should be a seperate RFC.

2000-08-23 Thread Tony Olekshy
Other than for the except and always clauses, RFC 199 is very similar to RFC 88. I like the idea behind except and always, but I think the proposed implementation could be dramatically simplified. The first thing to realize is that just because 119 doesn't say "try" the doesn't mean it isn't the