[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: octave and LLVM google summer of code project
From: |
John W. Eaton |
Subject: |
Re: octave and LLVM google summer of code project |
Date: |
Sun, 20 Apr 2008 10:41:29 -0400 |
On 20-Apr-2008, dbateman wrote:
| should work. Otherwise do a replacement like
|
| unwind_protect
| <block1>
| unwind_protect_cleanup
| <block2>
| end_unwind_protect
|
| with
|
| try
| <block1>
| catch
| <block2>
| rethrow(lasterror())
| end
Unless the replacement is done automatically, then I think the problem
is that we then have two branches of the code. My guess is that each
branch would tend to evolve independently and I don't see that as a
very desirable situation.
jwe
- octave and LLVM google summer of code project, Duncan Sands, 2008/04/08
- Re: octave and LLVM google summer of code project, David Bateman, 2008/04/08
- Re: octave and LLVM google summer of code project, John W. Eaton, 2008/04/08
- Re: octave and LLVM google summer of code project, Duncan Sands, 2008/04/09
- Re: octave and LLVM google summer of code project, David Bateman, 2008/04/09
- Re: octave and LLVM google summer of code project, Eugene I, 2008/04/19
- Re: octave and LLVM google summer of code project, dbateman, 2008/04/19
- Re: octave and LLVM google summer of code project, Eugene I, 2008/04/19
- Re: octave and LLVM google summer of code project, dbateman, 2008/04/20
- Re: octave and LLVM google summer of code project, John W. Eaton, 2008/04/20
- Re: octave and LLVM google summer of code project,
John W. Eaton <=
- Re: octave and LLVM google summer of code project, Eugene I, 2008/04/20
- Re: octave and LLVM google summer of code project, John W. Eaton, 2008/04/20
- Re: octave and LLVM google summer of code project, Eugene I, 2008/04/20
- Re: octave and LLVM google summer of code project, John W. Eaton, 2008/04/20
- Re: octave and LLVM google summer of code project, Eugene I, 2008/04/22
Re: octave and LLVM google summer of code project, Wolfgang_M, 2008/04/15