On Tuesday, January 20, 2004, at 06:03 PM, Robert Spier wrote:
If you respond to this message, with the ticket id and brief reason why it can be closed, i.e. "patch applied", "patch rejected", "bad idea".. I'll do the labor of updating the ticketing system.
-R
18044: Assembler doesn't return a useful exit status
assemble.pl is dead - original issue resolved, followup sent, though we still don't return on bad usage as the follow up poster requested.
19670: [PASM] bug in i/o (read on stdin)
Sent followup via RT - still can't get unbuffered STDIN, though the main issue is resolved.
20666: Assemble.pl Reports Incorrect Line Numbers after Removal of Macros
assemble.pl is dead.
21729: IMCC doesn't handle scientific notation constants
The thrust was "assemble.pl" supports them, imcc doesn't, but they should agree.
Since assemble.pl is dead, the question is moot, IMCC notation wins. (no followup sent.)
22183: imcc doesn't support \e
Yes it does. (patch was applied but never closed) (no followup sent)
22521: IMCC causes seegfault with many perlarrays and perlhashes 22617: IMCC duplicate labels in different subs cause wrong branch
Leo fixed these, but they were never closed
22718: core function index() returns -1 when search string contains spaces
This appears to be fixed.
22922: Parrot threading!
This wasn't really a bug. More of a question that Dan seems to have answered.
22995: [PATCH] op cmp INT STR STRDan applied this, never closed.
23299: Dynamic type handling in IMCC
There is a very long discussion which appears to be rendered academic by the fact that the poster's original code now works (presuming you add the missing "end" as the last opcode.)
... and then I got bored.
--
Will "Coke" Coleda will at coleda dot com
