|Re: How Do I Write My Own Scripting Interpreter? firstname.lastname@example.org (Warwick Molloy) (2001-07-23)|
|Re: How Do I Write My Own Scripting Interpreter? email@example.com (Alexander Baranovsky) (2001-07-27)|
|From:||"Warwick Molloy" <firstname.lastname@example.org>|
|Date:||23 Jul 2001 23:24:36 -0400|
|Posted-Date:||23 Jul 2001 23:24:36 EDT|
In article <WUr67.5334$MA.email@example.com>, "Mike"
> I have written a new object oriented scripting language specification.
> - How do I write my own interpreter for it?
That might depend on the tools available for your platform. For
instance you might try lex/yacc on a UNIX(like) system or some other
parser generator. I just saw an announcement for CoCo/R on this news
group. You might try that :-)
Another thought, if you need an OO scripting language, have you looked
at Python? (www.python.org) You might also try prototyping your
parser in Python. Python makes many things easy and is available on
many platforms... but then you might also try Perl etc. Whatever gets
> - Is it possible to publish the specification with a public GNU license,
> and get other hobbyists to write the interpreters for it?
Yup. Of course. You need some kind of host for it. Why not have a
look at www.sourceforge.net? You could create a project there...
This way, you can begin a community of users for your language.
> - If I can publish it, where would you recommend I post it? The >
international ACM organization? ANSI? ECMA?
Whoa there... publish or standardise? Standardisation is probably
only worth chasing once you've built up a community of users or at
least some case studies. I recommend you implement it first before
worrying about this too much...
[Similar questions have come up several times in recent months, and
people have suggested lots and lots of freely available scripting
languages including TCL, Python, Lua, and even forth. Does the world
really need yet another? -John]
Return to the
Search the comp.compilers archives again.