Hi Seb,

I agree with you that this discussion comes from the language
(compiler) limitation. Namespaces would be a powerfull sollution, but
we should realy concider if we want ask Kyle to implement this. We (I,
amongst others) asked him to add 18F support and it seems that it
hardly is used. And based on the complexity of such support, there are
no doubt remaining issues, resulting in less use.
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.

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.
The second scarce resource is ram (file memory). This is used for
procedure/function parameters and can't be saved that easy.
The third resouce - flash - is the least of my concerns.

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.

Joep

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to