Looks like that problem was in 44 (and how knows how far back it goes).
I'll take a look when I start the script pod URI stuff, probably just a bug in the compiler's version of TypeParser which isn't handling FFI references correctly.
NOTE: Java FFI does work (at least the test suite fully passes)
brianMon 8 Feb 2010
Renamed from compilerJava broken? to Compiler TypeParser doesn't handle Java FFI
brianFri 26 Mar 2010
Since this problem cropped again, I took a look if there was a quick fix.
Fundamentally the syntax for FFI pods using [] was an extremely poor choice because it makes really difficult to parse FFI types versus map types.
So we just need to buckle down and define the final syntax for alternate pods as URIs, or whatever we decide. But the existing FFI syntax needs to change.
brianFri 7 May 2010
Ticket resolved in 1.0.53
I've fixed the compiler's TypeParser to handle FFI using the original [java]package syntax.
KevinKelley Mon 8 Feb 2010
Can't seem to even link the pod... this test:
yields this error:
brian Mon 8 Feb 2010
Promoted to ticket #965 and assigned to brian
Looks like that problem was in 44 (and how knows how far back it goes).
I'll take a look when I start the script pod URI stuff, probably just a bug in the compiler's version of TypeParser which isn't handling FFI references correctly.
NOTE: Java FFI does work (at least the test suite fully passes)
brian Mon 8 Feb 2010
Renamed from compilerJava broken? to Compiler TypeParser doesn't handle Java FFI
brian Fri 26 Mar 2010
Since this problem cropped again, I took a look if there was a quick fix.
Fundamentally the syntax for FFI pods using
[]
was an extremely poor choice because it makes really difficult to parse FFI types versus map types.So we just need to buckle down and define the final syntax for alternate pods as URIs, or whatever we decide. But the existing FFI syntax needs to change.
brian Fri 7 May 2010
Ticket resolved in 1.0.53
I've fixed the compiler's TypeParser to handle FFI using the original
[java]package
syntax.