[DotGNU]DGuile (was Re: About scripting: SilverScript)

[S11001001]

Peter Minten wrote:
> Hi folks,
>
> I've been doing some thinking on what would be the ideal scripting
> language for webservices. The main requirements I thought of were:
>
> * Object-Orientedness
> * Strong typing (to avoid errors)
> * Clearness of what code does (no C irregularities)
> * Code readability
> * Simplicity
> * How easy it is to call C# code

This is sort of not what you are talking about, but as I have been 
considering native programs, it seems to me that the concept of the 
scripting engine *designed* for embedding (I'm talking about GNU Guile 
here) gets more and more useful.

Programming is the most powerful customization of any program, and 
sometimes it can be more useful to use Guile code as things to rely on 
in an engine.

BTW, I came to this from thinking about a PageMaker(TM) clone, for some 
kind of AutoFormat system: you write hooks in Guile, and the main C++ 
code *relies* on this.

It seems like a big leap from scripted programs to compiled programs; 
each has its benefits and weaknesses. Embeddable scripting is a great 
way to combine both.

So I propose, for an undetermined future date, that an embeddable 
scripting engine be added to DotGNU standard libraries. SilverScript 
could very well be it, but that's not my decision. It came up because of 
the talk about calls and callbacks. It also sounds less messy than Jython.

And of course, I understand that Scheme doesn't meet your requests, but 
that is not the topic of my reply. See other posts for more useful 
replies in that topic.

And the other important point would be that the engine is designed from 
the start to be embedded, not have functionality tacked on later. Which 
is why I bring it up now.

(Tentatively named DGuile, for "DotGNU Guile", my suggestion. Guile is 
the program, not the language, IIRC)

--
Stephen Compall
DotGNU `Contributor' -- http://www.dotgnu.org

Free software is a matter of the users' freedom to run, copy,
distribute, study, change and improve the software. More precisely, it
refers to four kinds of freedom, for the users of the software:

    * The freedom to run the program, for any purpose (freedom 0).
    * The freedom to study how the program works, and adapt it to your
    needs (freedom 1). Access to the source code is a precondition
    for this.
    * The freedom to redistribute copies so you can help your neighbor
    (freedom 2).
    * The freedom to improve the program, and release your
    improvements to the public, so that the whole community
    benefits. (freedom 3). Access to the source code is a
    precondition for this.
        -- RMS, "The Free Software Definition"