[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jacorb-bugs
Subject:    [jacorb-bugs] [Bug 304] Idl compiler generates invalid code for escaped const chars (chars beginning
From:       bugzilla-daemon () inf ! fu-berlin ! de
Date:       2002-12-12 15:29:17
Message-ID: E18MVH3-0005iG-00 () berners
[Download RAW message or body]

http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=304





------- Additional Comments From joonash@hotmail.com  2002-12-12 16:29 -------
It seems that the bug can be fixed by adding code that escapes
backslash-characters in line 2663 in parser.java:

--- CUT ---

case 102: // literal ::= QUOTE CH QUOTE 
{
  CUP$result = new Literal(/*literal*/75);

  ((Literal)CUP$result).string = "\'" +
BackslashEscaper.escape((/*c*/(java_cup.runtime.char_token)CUP$stack.elementAt(CUP$top-1)).char_val)
+ "\'";
  ((Literal)CUP$result).token =
(/*c*/(java_cup.runtime.char_token)CUP$stack.elementAt(CUP$top-1));
}

--- CUT ---

The BackslashEscaper.escape() -method just escapes the necessary chars and
returns corresponding String. I think this may not be the best possible solution
as I guess that the parser.java is generated from parser.cup -file.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

[prev in list] [next in list] [prev in thread] [next in thread]