> > The lesson learned: we need to be sure functionality will be used (and > thus, tested in the process) before we ask Kyle to add it.
Is there any votes about new features for the compiler ? AFAIK, I did not see any, and could help to set priority. Maybe that's also because before jallib, there's no central repository, so everyone is copying libraries here and there, and modify them where they should (must) not. "Allowing" to modify libs just clear the debate: no need to have top layer, just rewrite your own. Of course, this is not what we want, but maybe that will be another benefit of jallib: centralize libraries will also centralize feature requests. > Pragma nostack - if it does what I think it does - solves part of the > most urgent issue: stack usage. But I doubt that it can remove the > stack use if a procedure of function has a return value. Yes, IIRC that's what said in the pragmajal.txt file. BTW: who asked for this nice feature ? Is Kyle just added it because it was possible/easy ? A neat (and maybe not so complex to implement) sollution for the issue > described is when 'is' also works to create alliasses for functions > and procedures (with the exact same calling structure), like: > > procedure serial'put is serial_hardware'put > > or something alike. > Definitively, pointer to function and procedures. If you have this, you're closed to functional programming. Maybe we could talk again about this once the release is done, and provide hypothetical jal code examples, to see it would really help us (and others). Seb --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
