[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Wed, 29 Jan 1997 12:37:30 -0500 (EST)
> >> So, as far as the project goes, I'm now looking at implementing a
> Why invent yet another language? If I were going to do this, either building
> Tcl, Python, Perl, seems like the approach I would use. Designing a language
> that only can be used by Lynx browsers seems less than optimal. Lynx
A good point and well taken.
Designing a language that can be used only by lynx is indeed less than
optimal -- indeed, it is academic. Which is most of the problem. My idea
my thesis advisor. The comprimise was to implement some toy language of
my own creation to demonstrate that implementing HTML-based interpreted
languages is doable, and *then* worry about doing something useful.
The next question is: Why bother? Aside from getting an MS, the above
would not seem to add much to the functionality of lynx. Hopefully, I
can direct this project so that the point becomes the construction of the
mechanisms allowing any yacc-based interpreted language to be "plugged in"
to lynx. Once the groundwork has been laid with my toy language, anyone
else who had a "real" language compiled in yacc could implement it with
minimal [giggle] effort.
Athough it's probably obvious, let me state for the record that a
"BarryScript"  enabled lynx will probably be of interest to five or six
people, tops, and would not be part of the general distribution package.
Thanks for the comments!
> Larry W. Virden INET: address@hidden
Florida State University
 My advisor's idea, not mine. Trust me.
; To UNSUBSCRIBE: Send a mail message to address@hidden
; with "unsubscribe lynx-dev" (without the
; quotation marks) on a line by itself.