Related articles |
---|
Need advices for creating a proprietary language mike@heliovisionsproductions.fr (Mike) (1998-03-03) |
Re: Need advices for creating a proprietary language laheadle@cs.uchicago.edu (Lyn A Headley) (1998-03-06) |
Re: Need advices for creating a proprietary language sandy.harris@sympatico.ca (1998-03-06) |
Re: Need advices for creating a proprietary language joachim.durchholz@munich.netsurf.de (Joachim Durchholz) (1998-03-07) |
Re: Need advices for creating a proprietary language mc@hack.org (MC) (1998-03-07) |
Re: Need advices for creating a proprietary language markh@usai.asiainfo.com (Mark Harrison) (1998-03-07) |
Re: Need advices for creating a proprietary language nixon@softlab.se (Leif Nixon) (1998-03-12) |
Re: Need advices for creating a proprietary language tucny@km1.fjfi.cvut.cz (Ondrej Tucny) (1998-03-12) |
[3 later articles] |
From: | Lyn A Headley <laheadle@cs.uchicago.edu> |
Newsgroups: | comp.compilers |
Date: | 6 Mar 1998 16:47:37 -0500 |
Organization: | University of Chicago -- Academic Computing Services |
References: | 98-03-012 |
Keywords: | interpreter, design, comment |
Writing a compiler is very hard. If you have never studied the
issues, it would take you a long time before you could even _begin_
coding. Do you *have* to write your own language? Why not use an
existing one, like Python or Lua?
--
Lyn Headley
[Or tcl or rexx, for that matter. -John]
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.