perl.perl6.language.errors

Re: $SIG{DIE} should be localized and cleared at the start of an eval block

17 Dec 2004 12:39:19 -0000

[email protected] ((PerlDiscuss - Perl Newsgroups and mailing lists)) • #311

RE: RFC 80 (v4) Exception objects and classes for builtins

Wed, 4 Oct 2000 09:58:03 -0500

[email protected] (David Grove) • #310

RFC 151 (v4) Merge C<$!>, C<$^E>, C<$@> and C<$?>

4 Oct 2000 06:21:39 -0000

[email protected] (Perl6 RFC Librarian) • #309

RFC 80 (v4) Exception objects and classes for builtins

4 Oct 2000 06:20:40 -0000

[email protected] (Perl6 RFC Librarian) • #308

RFC 96 (v2) A Base Class for Exception Objects

2 Oct 2000 00:32:45 -0000

[email protected] (Perl6 RFC Librarian) • #307

RFC 88 (v3) Omnibus Structured Exception/Error Handling Mechanism

2 Oct 2000 00:30:46 -0000

[email protected] (Perl6 RFC Librarian) • #306

RE: RFC 359 (v1) Improvement needed in error messages (both internal errors and die function).

Sun, 1 Oct 2000 08:37:03 -0500

[email protected] (David Grove) • #305

RFC 359 (v1) Improvement needed in error messages (both internal errors and die function).

1 Oct 2000 06:36:37 -0000

[email protected] (Perl6 RFC Librarian) • #304

RFC 1 (v1) Improvement needed in error messages (both internal errors and die function).

1 Oct 2000 06:36:24 -0000

[email protected] (Perl6 RFC Librarian) • #303

RFC 119 (v4) Object neutral error handling via exceptions

29 Sep 2000 03:21:31 -0000

[email protected] (Perl6 RFC Librarian) • #302

RFC 119 (v3) Object neutral error handling via exceptions

15 Sep 2000 05:54:32 -0000

[email protected] (Perl6 RFC Librarian) • #301

RFC 80 (v3) Exception objects and classes for builtins

14 Sep 2000 19:41:06 -0000

[email protected] (Perl6 RFC Librarian) • #300

Re: $a in @b (RFC 199)

Thu, 14 Sep 2000 14:06:21 -0400

[email protected] (John Porter) • #299

Re: $a in @b (RFC 199)

Thu, 14 Sep 2000 12:55:28 -0500

[email protected] ("David L. Nicol") • #298

RFC 151 (v3) Merge C<$!>, C<$^E>, C<$@> and C<$?>

13 Sep 2000 23:35:32 -0000

[email protected] (Perl6 RFC Librarian) • #297

Re: RFC 151 (v2) Merge C<$!>, C<$^E>, C<$@> and C<$?>

Thu, 07 Sep 2000 17:24:52 -0700

[email protected] (Peter Scott) • #296

Re: RFC 151 (v2) Merge C<$!>, C<$^E>, C<$@> and C<$?>

Thu, 07 Sep 2000 15:55:15 -0700

[email protected] (Nathan Wiger) • #295

RFC 151 (v2) Merge C<$!>, C<$^E>, C<$@> and C<$?>

6 Sep 2000 18:25:44 -0000

[email protected] (Perl6 RFC Librarian) • #294

Re: Structured exception handling should be a core module.

Tue, 29 Aug 2000 12:30:11 -0700

[email protected] (Peter Scott) • #293

Re: Structured exception handling should be a core module.

Tue, 29 Aug 2000 13:07:04 -0600

[email protected] (Tom Christiansen) • #292

Re: Structured exception handling should be a core module.

Tue, 29 Aug 2000 09:32:44 -0700

[email protected] (Peter Scott) • #291

Re: Structured exception handling should be a core module.

Mon, 28 Aug 2000 21:41:28 -0600

[email protected] (Tony Olekshy) • #290

Re: On the case for exception-based error handling.

Mon, 28 Aug 2000 19:28:51 -0700

[email protected] (Peter Scott) • #289

Re: Structured exception handling should be a core module.

Mon, 28 Aug 2000 19:21:18 -0700

[email protected] (Peter Scott) • #288

Re: Structured exception handling should be a core module.

Mon, 28 Aug 2000 17:44:18 -0700

[email protected] (Peter Scott) • #287

On RFC 88: Serendipity while throwing a string.

Mon, 28 Aug 2000 04:01:27 -0600

[email protected] (Tony Olekshy) • #286

Re: On the case for exception-based error handling.

Sun, 27 Aug 2000 12:16:42 -0400

[email protected] (Bennett Todd) • #285

Re: On the case for exception-based error handling.

Sun, 27 Aug 2000 09:03:07 -0700

[email protected] (Peter Scott) • #284

Re: On the case for exception-based error handling.

Sun, 27 Aug 2000 10:26:09 -0400

[email protected] (Bennett Todd) • #283

RFC 88 version 3 draft 1 is available via http.

Sun, 27 Aug 2000 07:18:25 -0600

[email protected] (Tony Olekshy) • #282

Re: Structured exception handling should be a core module.

Sat, 26 Aug 2000 05:34:39 -0600

[email protected] (Tony Olekshy) • #281

Re: $SIG{DIE} should be localized and cleared at the start of an eval block

Fri, 25 Aug 2000 13:11:01 -0600

[email protected] (Tom Christiansen) • #280

Re: $SIG{DIE} should be localized and cleared at the startof an eval block

Fri, 25 Aug 2000 11:44:30 -0700

[email protected] (Peter Scott) • #279

Re: Structured exception handling should be a core module.

Fri, 25 Aug 2000 10:13:12 +0200

[email protected] (Bart Lateur) • #278

$SIG{DIE} should be localized and cleared at the start of an eval block

Fri, 25 Aug 2000 10:13:04 +0200

[email protected] (Bart Lateur) • #277

Re: Structured exception handling should be a core module.

Fri, 25 Aug 2000 01:42:22 -0600

[email protected] (Tony Olekshy) • #276

Re: Structured exception handling should be a core module.

Thu, 24 Aug 2000 17:57:55 -0700

[email protected] (Peter Scott) • #275

Re: Structured exception handling should be a core module.

Thu, 24 Aug 2000 18:48:10 -0600

[email protected] (Tony Olekshy) • #274

Re: Structured exception handling should be a core module.

Thu, 24 Aug 2000 17:27:49 -0700

[email protected] (Peter Scott) • #273

Re: On the case for exception-based error handling.

Thu, 24 Aug 2000 18:17:34 -0600

[email protected] (Tony Olekshy) • #272

Structured exception handling should be a core module.

Thu, 24 Aug 2000 18:06:23 -0600

[email protected] (Tony Olekshy) • #271

Re: On the case for exception-based error handling.

Thu, 24 Aug 2000 18:07:36 -0600

[email protected] (Tony Olekshy) • #270

Re: RFC 140 (v1) One Should Not Get Away With Ignoring System Call Errors

24 Aug 2000 19:42:51 -0400

[email protected] (Chaim Frenkel) • #269

Re: Why "fatal" errors aren't special.

Thu, 24 Aug 2000 13:25:51 -0700

[email protected] (Glenn Linderman) • #268

Examples from RFC 88 redone using RFC 119 facilities [Was: Re: RFC 88 (v2) Omnibus Structured Exception/Error Handling Mechanism]

Thu, 24 Aug 2000 12:46:39 -0700

[email protected] (Glenn Linderman) • #267

Re: Why "fatal" errors aren't special.

Thu, 24 Aug 2000 11:26:22 -0700

[email protected] (Peter Scott) • #266

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

Thu, 24 Aug 2000 11:21:15 -0700

[email protected] (Glenn Linderman) • #265

Re: Why "fatal" errors aren't special.

Thu, 24 Aug 2000 11:21:09 -0700

[email protected] (Glenn Linderman) • #264

Re: Why $@ should be structured data.

Thu, 24 Aug 2000 11:21:05 -0700

[email protected] (Glenn Linderman) • #263

Re: RFC 119v2: Object neutral error handling via exceptions

Thu, 24 Aug 2000 11:21:02 -0700

[email protected] (Glenn Linderman) • #262

perl.perl6.language.errors

Re: $SIG{__DIE__} should be localized and cleared at the start of an eval block

RE: RFC 80 (v4) Exception objects and classes for builtins

RFC 151 (v4) Merge C<$!>, C<$^E>, C<$@> and C<$?>

RFC 80 (v4) Exception objects and classes for builtins

RFC 96 (v2) A Base Class for Exception Objects

RFC 88 (v3) Omnibus Structured Exception/Error Handling Mechanism

RE: RFC 359 (v1) Improvement needed in error messages (both internal errors and die function).

RFC 359 (v1) Improvement needed in error messages (both internal errors and die function).

RFC 1 (v1) Improvement needed in error messages (both internal errors and die function).

RFC 119 (v4) Object neutral error handling via exceptions

RFC 119 (v3) Object neutral error handling via exceptions

RFC 80 (v3) Exception objects and classes for builtins

Re: $a in @b (RFC 199)

Re: $a in @b (RFC 199)

RFC 151 (v3) Merge C<$!>, C<$^E>, C<$@> and C<$?>

Re: RFC 151 (v2) Merge C<$!>, C<$^E>, C<$@> and C<$?>

Re: RFC 151 (v2) Merge C<$!>, C<$^E>, C<$@> and C<$?>

RFC 151 (v2) Merge C<$!>, C<$^E>, C<$@> and C<$?>

Re: Structured exception handling should be a core module.

Re: Structured exception handling should be a core module.

Re: Structured exception handling should be a core module.

Re: Structured exception handling should be a core module.

Re: On the case for exception-based error handling.

Re: Structured exception handling should be a core module.

Re: Structured exception handling should be a core module.

On RFC 88: Serendipity while throwing a string.

Re: On the case for exception-based error handling.

Re: On the case for exception-based error handling.

Re: On the case for exception-based error handling.

RFC 88 version 3 draft 1 is available via http.

Re: Structured exception handling should be a core module.

Re: $SIG{__DIE__} should be localized and cleared at the start of an eval block

Re: $SIG{__DIE__} should be localized and cleared at the startof an eval block

Re: Structured exception handling should be a core module.

$SIG{__DIE__} should be localized and cleared at the start of an eval block

Re: Structured exception handling should be a core module.

Re: Structured exception handling should be a core module.

Re: Structured exception handling should be a core module.

Re: Structured exception handling should be a core module.

Re: On the case for exception-based error handling.

Structured exception handling should be a core module.

Re: On the case for exception-based error handling.

Re: RFC 140 (v1) One Should Not Get Away With Ignoring System Call Errors

Re: Why "fatal" errors aren't special.

Examples from RFC 88 redone using RFC 119 facilities [Was: Re: RFC 88 (v2) Omnibus Structured Exception/Error Handling Mechanism]

Re: Why "fatal" errors aren't special.

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

Re: Why "fatal" errors aren't special.

Re: Why $@ should be structured data.

Re: RFC 119v2: Object neutral error handling via exceptions

Re: $SIG{DIE} should be localized and cleared at the start of an eval block

Re: $SIG{DIE} should be localized and cleared at the start of an eval block

Re: $SIG{DIE} should be localized and cleared at the startof an eval block

$SIG{DIE} should be localized and cleared at the start of an eval block