Joseph F. Ryan wrote:
# New Ticket Created by "Clinton A. Pierce"
# Please include the string: [perl #21729]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt2/Ticket/Display.html?id=21729 >
Example:
set I0, 1e20
end
Results in:
(error) line 2: parse error, unexpected IDENTIFIER, expecting >'\n'
Didn't create output asm.
A larger example is BASIC's Connect-4 game:
c:> cd parrot\languages\basic\compiler
c:> compile.pl samples\conn4.bas
c:> ..\..\..\languages\imcc\imcc.exe TARG_test.pasm
Results in:
(error) line 4329: parse error, unexpected IDENTIFIER, expecting '\n'
Didn't create output asm.
Should it, though? Although it would be pretty convienient, I think
that handling scientific notation would be an unnecessary complication
for IMCC, and it would be better handled by the compilers that target
it. (As in, the compiler converts scientific notation to decimal form
during compilition to IMCC code.)
First it's my understanding that the Parrot assembler does support
scientific notation, so IMCC should also. Second we need to handle
BigFloat values and I don't really want to have to express 1e12345
as a 12345+ length char string. On a related note does IMCC have a
token or line length limit?
--
Mark Biggar
[EMAIL PROTECTED]
[EMAIL PROTECTED]
