Hi Vasile,

2010/4/8 vasile surducan <[email protected]>:
> ARM (extended to DSP) and FPGA. For the FPGA  translation should be from Jal
> to Verilog or VHDL.
VHDL is like Python for me - I've put in to little effort to understand...

> For ARM, a translation from Jal to C, then a compilation under C (as I have
> understood is planned) imply a good knowledge of C even for the Jal user...
> so once C is well known why to bother with this weird combination?
For me this is an experiment to see what it takes to translate jal
into C. If this works, C is and intermediate language where you don't
need extensive knowledge of.
Like you, I don't see much added value of programming parts in C and
parts in JAL. And personaly - if a system has a proper C compiler, I'd
prefere that over JAL...

> Maybe will be much easy to define an ARM family and try to generate the
> output code directly for that one?
Sounds like a nice project too and I am convinced it will  generate
better code than the path via C.

I'm just like a young dog: I see something that looks interesting and
get involved. For now this is the grammar and the 'dot at the horizon'
is the translator from JAL to C. We might not get at that specific
point, but as long we have fun on the way it's okay with me. And maybe
it produce something usefull, like a JAL grammar definition in antlr,
that can be used for your JAL-to-ARM compiler.

> In that way, generic libraries conversion should be easier?
What do you mean with generic libraries conversion?

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