Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Weirdness with scoping/context of exception variables

Description

It's difficult to explain, but this code demonstrates it:

This outputs:

It's because of the reused name `e` in the exception handling. Note this is NOT a problem on ColdFusion. I do not what I ought to be expecting here (although I clearly didn't write that code expecting it to have problems!)

If I change either `e` declarations to something else, the code works as expected.

Environment

None

Activity

Show:

Michael Offner 5 October 2015 at 13:29

Adam Cameron 5 October 2015 at 13:17

It was probably fixed along the way then, I s'pose. I just tested on 5.0.0.65-BETA and it's fine too.

Michael Offner 5 October 2015 at 13:05
Edited

with 5.0.0.82-SNAPSHOT i'm getting

Adam Cameron 28 May 2015 at 20:05

Just an observation here, in case it helps. This code works fine on Lucee 4.5; it's only broken on 5.

Fixed

Details

Assignee

Reporter

Priority

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Created 26 April 2015 at 13:05
Updated 6 October 2015 at 17:00
Resolved 6 October 2015 at 17:00