FWD » Core Development » Base Language

This issue affects the FWD conversion when passing a CHARACTER literal as an argument to a class method expecting a LONGCHAR parameter. The converter omits the required new longchar(...) wrapper, causing a type mismatch in the generated Java code.

Conversion Test Case¶

Convert the following 4GL class (e.g., unittests/TestCharacterLiteralConversion.cls):

CLASS unittests.TestCharacterLiteralConversion:

  METHOD PUBLIC VOID methodWithLongcharParameter(INPUT arg AS LONGCHAR):
      RETURN.
  END METHOD.

  METHOD PUBLIC VOID test():
     methodWithLongcharParameter('a').
   END METHOD.
END CLASS.

This defines a method accepting LONGCHAR and calls it with a literal ('a').

Expected Behavior (Correct Conversion)¶

The generated Java should promote the literal via explicit LONGCHAR construction:

methodWithLongcharParameter(new longchar("a"));

Actual Behavior (FWD Converter)¶

The literal is passed directly as a Java String literal:

methodWithLongcharParameter("a");

This causes a compilation error (type mismatch: String not assignable to longchar).

Vladimir Tsichevski wrote:

This is a regression, this issue did not exist in trunk rev. 14527 when the task #7184 was worked on.

Seems this issue does not exist. Other issues mentioned in #7184 do exist still: the longchar constructor is applied two times to a string literal instead of one.