Hi Mike,

2010/4/28 m...@watty <[email protected]>:
> It's a great achievement and no doubt good fun.
I sure is fun :)

> But unless it exactly supports JALv2, no more, no less, it's
> effectively a different language.
You say this like it is a bad thing ;)
But serious: languages do evolve and by your definition, the adding of
alias created a new language. Some JAL features do not work on the all
devices (like calculations over 16 bits on 16F73), which by your
definition also create an other language. I concider this dialects,
and I also see subsets.

An other point you mentioned before was the actual definition of the
language. Behavior of JAL is not defined into all detail, which is
okay for me. I've tested quite a few of these details over the last
few weeks and learned how Kyle managed to get this working on the
not-so-supportive architecture of the (16F) pics. This does however
create limitations which are - as I said before - not described in the
manual and where the average use is not aware. And he does not need to
be aware of the details. Are those undocumented implementation details
part of the language? And should they be retained, even if they could
be changed for the better? Volatile is an obvious example: it
specifies how a variable behaves. But there is no description on how
variables behave without this keyword...

> Unless I was actually developing this  translator, I can't see the
> point for my ARM project.
Don't you? I'd expet you would like to use JAL over 'evil C' on your ARM...

Anyway, some people would like to have JAL support for other platforms
and this project may or may not lead to translator with an acceptable
level of compatibilty.
The only way practical you can have full compatibility (that is: from
a functional point of view, you can't determine the difference) is to
create a virtual machine (emulator, interpreter - whatever you call
it) that runs the actual hex code generated by the compiler.

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