Hi Olivers,

Great work! Wow, it generates a JAL source file of almost 100.000 lines of code 
but compiles fast.

Can you have a look at sample 16f1825_large_array.jal? It does not yet compile 
with this library and I can't see why. This is - I think - the only sample file 
that uses 4 large arrays. The error message is as follows:

d:\PIC\Projects\2020\New_Large_Array\16f1825_large_array.jal:81: 
"large_array_2" not defined
d:\PIC\Projects\2020\New_Large_Array\16f1825_large_array.jal:81: '=' expected 
(got 'const')
d:\PIC\Projects\2020\New_Large_Array\16f1825_large_array.jal:87: 
"large_array_3" not defined
d:\PIC\Projects\2020\New_Large_Array\16f1825_large_array.jal:87: '=' expected 
(got 'const')
d:\PIC\Projects\2020\New_Large_Array\16f1825_large_array.jal:93: 
"large_array_4" not defined
d:\PIC\Projects\2020\New_Large_Array\16f1825_large_array.jal:93: '=' expected 
(got 'var')
d:\PIC\Projects\2020\New_Large_Array\16f1825_large_array.jal:104: "word_array" 
not defined
d:\PIC\Projects\2020\New_Large_Array\16f1825_large_array.jal:104: 'end' 
expected (got 'word_array')
d:\PIC\Projects\2020\New_Large_Array\16f1825_large_array.jal:104: {FOR starts 
at d:\PIC\Projects\2020\New_Large_Array\16f1825_large_array.jal:103}
d:\PIC\Projects\2020\New_Large_Array\16f1825_large_array.jal:104: "word_array" 
not defined
d:\PIC\Projects\2020\New_Large_Array\16f1825_large_array.jal:104: 'end' 
expected (got 'word_array')
d:\PIC\Projects\2020\New_Large_Array\16f1825_large_array.jal:104: {FOREVER 
starts at d:\PIC\Projects\2020\New_Large_Array\16f1825_large_array.jal:98}
d:\PIC\Projects\2020\New_Large_Array\16f1825_large_array.jal:104: "word_array" 
not defined
d:\PIC\Projects\2020\New_Large_Array\16f1825_large_array.jal:104: unexpected 
token: word_array
14 errors, 0 warnings

Thanks

Kind regards,

Rob

________________________________
Van: 'Oliver Seitz' via jallib <[email protected]>
Verzonden: zaterdag 19 december 2020 19:52
Aan: 'Oliver Seitz' via jallib <[email protected]>
Onderwerp: Re: [jallib] Large_array update

Hi all!

Python was a very good recommendation, thank you Rob Hammerling :-)

I dropped the idea of the array with no index, that would have been a difficult 
and nearly useless addition.

Other bad news: The PIC14/byte*2 version needs one byte GPR more than the old 
lib, PIC16/byte*4 even four bytes more.

But that is it, all other versions need the same or less GPR. Execution time 
and code size are now even 12-25% smaller than with my last version, now my 
test program in the best cases needs little more than half the time compared to 
the original lib, code is between 300 and 1000 words smaller.

I did some tests, but only with one array at a time.

Greets,
Kiste



--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/2049291384.2558336.1608403923944%40mail.yahoo.com<https://groups.google.com/d/msgid/jallib/2049291384.2558336.1608403923944%40mail.yahoo.com?utm_medium=email&utm_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/AM0PR07MB62418A0BC3DFC89B67D54327E6C10%40AM0PR07MB6241.eurprd07.prod.outlook.com.

Reply via email to