|Embeddable and Extensible Languages email@example.com (PlayDough) (2005-01-12)|
|Re: Embeddable and Extensible Languages firstname.lastname@example.org (Jean-Marc Bourguet) (2005-01-14)|
|Re: Embeddable and Extensible Languages email@example.com (Georgios Petasis) (2005-01-14)|
|Re: Embeddable and Extensible Languages firstname.lastname@example.org (2005-01-14)|
|Re: Embeddable and Extensible Languages Juergen.Kahrs@vr-web.de (=?ISO-8859-1?Q?J=FCrgen_Kahrs?=) (2005-01-14)|
|Re: Embeddable and Extensible Languages email@example.com (Thant Tessman) (2005-01-14)|
|Re: Embeddable and Extensible Languages firstname.lastname@example.org (Tom Verbeure) (2005-01-15)|
|Re: Embeddable and Extensible Languages email@example.com (PlayDough) (2005-01-15)|
|[9 later articles]|
|From:||Jean-Marc Bourguet <firstname.lastname@example.org>|
|Date:||14 Jan 2005 00:40:43 -0500|
"PlayDough" <email@example.com> writes:
> I'm working on a project that would embed a language into our
> simulation system for FPGA and ASIC design. This language would be
> used to control a testbench through the PLI/FLI provided by the
> simulator. Preferrably, it would be C (or C like) since our end
> users are most familiar with C. Also, we would like the ability to
> have multiple source files or packages that would allow our tools
> team to develop support tools.
> I've looked at Lua, Python, Pike, Ici, Eic, Ch, Cint, S-Lang, Small,
> elastiC, Simkin, and even some small, homegrown projects.
Considering your target domain, I'd consider TCL as it is more or less
a de-facto standard extension langage used by EDA applications and so
there is a good chance that your users are already familiar with it.
> So far, I've narrowed it down to Lua and Python. I like the Lua
> syntax, but the support base isn't as big as Python. But with
> Python, I fear that the syntax could be problem for the customers of
> our project. Both have the problem of not being capable of running
> multiple contexts (outside of the interpreter).
I'm not sure what you want but multiple TCL interpreters can be run in
the same executable.
Another language you didn't name but which seems to have a signigicant
user base is Ruby.
Return to the
Search the comp.compilers archives again.