🚀 go-pugleaf

In article <CzD1HH.CHs@world.std.com>, ralex@world.std.com 
(Aleksey Y Romanov) writes:
|> Hi,
|> 
|> IMHO:
|> 
|> I am wondering why BASIC married with shared libs is out of consideration
|> as developer level interface ?

Which BASIC?  Line numbers for every line?  Or just for
goto-destinations?  How about subroutines with local variables?  In
which case, why go with BASIC?  It just becomes a mostly-dynamically
typed, possibly garbage collected C-like language.  It might have done
a decade ago, but not today.  Features like higher-order functions,
exceptions, continuations, safety, garbage collection, symbolic
manipulation, modules, object orientation, etc., etc., etc. are 
what go into a powerful modern language.

|> For example, application developer can 
|> put user hooks in appropriate places of his code.

Hooks are one of the most buggy methods for making the environment
extensible.

|> The procedural language has very substantial advantage - it is the most
|> natural way for human beings to describe its activities.

Splutter.  Gasp.  If you want to think so, I shan't try to dissuade 
you.

--
David Richter (drichter@rice.edu)     
"People who use functional languages swear by them."--kanze@us-es.sel.de
"People who use procedural languages swear at them."--nickb@harlequin.co.uk
(require 'standard-disclaimer)