I'm afraid this is "expected behavior" due to an intended change. The {} will no longer define a literal ( like the <> ), but just enclose a "set of tokens". Since the number of tokens in a line is limited to 150 currently, your line exceeds the limit by far.
The change in the semantics was done because the previous implementation was not quite Masm-compatible ( Masm also won't accept your line! ).
You'll have to modify your source. The easiest workaround is to use <> instead of {}:
> But now I get an "A2168: General Failure" wich points to the last line of the structure array.
You'll have to provide a full test case then. Because for me there is no such error, using exactly the same version.
Here's the full source that I feed to jwasm, I managed to reconstruct this from your first test case snippets:
Hi Japhet,
I get with JWasm v2.08pre(08/05/2012) an error "Error A2062: Too many tokens in a line" for this code:
Listing:
Regards
Greenhorn
Here's the rest of repuired data for testing (incl. tchar.inc) …
I'm afraid this is "expected behavior" due to an intended change. The {} will no longer define a literal ( like the <> ), but just enclose a "set of tokens". Since the number of tokens in a line is limited to 150 currently, your line exceeds the limit by far.
The change in the semantics was done because the previous implementation was not quite Masm-compatible ( Masm also won't accept your line! ).
You'll have to modify your source. The easiest workaround is to use <> instead of {}:
< RGB( 0, 0, 0), cstrBlack >,
< RGB(255, 255, 255), cstrWhite >,
…
{ RGB(255, 255, 255), cstrWhite },
a bit more investigation did convince me that I'll have to revert the change and restore the {}-literals again.
Thanks for the quick reply and fix, japheth.
But now I get an "A2168: General Failure" wich points to the last line of the structure array.
The listing file looks fine without any error messages.
Used JWasm RC1.
Greenhorn
> But now I get an "A2168: General Failure" wich points to the last line of the structure array.
You'll have to provide a full test case then. Because for me there is no such error, using exactly the same version.
Here's the full source that I feed to jwasm, I managed to reconstruct this from your first test case snippets:
I made a Bug Tracker and attached the corresponding file.