At 10:16 AM 8/16/00 -0400, Chaim Frenkel wrote:
One issue that haven't seen addressed, is how to _not_ have exceptions.
I want to use a core module (non-core can do anything they want) but
I'd like to write it in procedural mode.
try {
$obj-method
On Wed, Aug 16, 2000 at 12:36:42PM -0700, Peter Scott wrote:
If you use a switch statement and want implicit rethrow (and I do), then
your exception handler somehow has to look inside the switch to see if an
exception was handled. Even if that's possible, it implies a level of
At 09:29 AM 8/16/00 -0500, Jonathan Scott Duff wrote:
Let me draw another picture (with "try" and "catch" this time):
try {
# code that may cause exceptions
} catch { # catches ALL exceptions
switch ($@-^_) {
alue would be the specified value.
If not specified then it would be the same as a return with no
arguments.
But what of RFC 70, which wants the option for exceptions in system calls
to cause program death?
Also I don't like code deciding to do something different depending on a
context that's possibly
I have moved this to [EMAIL PROTECTED]
Jonathan Scott Duff wrote:
Okay, imagine something for me:
# some code here that may cause an exception
exceptions {# when thrown, we end up here
switch ($@-^_) {
case canFoo
Jonathan Scott Duff [EMAIL PROTECTED] writes:
On Sun, Aug 13, 2000 at 10:51:24PM -0700, Peter Scott wrote:
Could be. I'd be interested in seeing non-OOP proposals that do what I
want exceptions to do, I have a hard time imagining one.
Well, what is it that you want exceptions to do
301 - 306 of 306 matches
Mail list logo
