Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

objj not dealing well with non ASCII characters

#108

The charCode() of a non ascii char is correct when compiling at run time a .j file, but fails in objj.

Test case included.

Reported by cacaodev · October 14th, 2008 @ 09:48 AM

State: resolved
Milestone: 0.6
Assigned to: Tom Robinson Tom Robinson

Activity

  1. Tom Robinson
    Tom Robinson
    • State changed from new to verified

    This appears to be a problem with Rhino, the JS interpreter we use in objj. I'll look into it more.

    October 17th, 2008 @ 12:00 PM

  2. Tom Robinson
    Tom Robinson

    Confirmed bug in Java and/or Rhino:

    http://groups.google.com/group/m...

    October 17th, 2008 @ 11:05 PM

  3. admin (at 280north)
    admin (at 280north)
    • State changed from verified to resolved

    (from [32fd299d1dccf28a84ec1206bfe6c1a866e63f85]) Fixed encoding issue with objj console.

    [#108 objj not dealing well with non ASCII characters state:resolved responsible:tlrobinson] http://github.com/280north/cappu...

    October 18th, 2008 @ 06:46 PM

  4. Tom Robinson
    Tom Robinson
    • Milestone set to 0.6
    • Tag changed from foundation, patch, preprocessor to objj, tool

    It seems to be a bug in Java (or not a bug?), and the Rhino guys put a fix in the Rhino shell, but objj doesn't actually rely on the Rhino shell, so I also put a fix in objj.

    It now treats stdin as UTF-8, so if you're on a system where it's something other than UTF-8 or ASCII it might break.

    October 18th, 2008 @ 06:48 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.