Brady Montz <bradym_at_cs.arizona.edu> writes:
> This discussion on extension languages is quickly going to descend into
> chaos. I see the following desires:
[...]
> I suspect there is wide agreement with these two points:
>
> 1. Fvwm's internal configuration language could be changed for the better.
> 2. If we add a new language, it should be done as a module. Most likely
people
> would want this module to be as tightly coupled to fvwm as possible for
> speed, using whichever dlopen, mmap, and threading facilities available
on
> the various architectures.
So far we agree...
> So, my proposal:
>
> Lets table the discussion on tcl/perl/python/java/icon/scheme/... and focus
on
> improving the internal language and the module interface(s).
Here we disagree. I would prefer to abandon the current configuration
language as a basis for the future development, adopt an existing
configuration language, and then add fvwm functionality/API to this
new language.
I we for some reason want to be backward compatible, we will
automatically limit ourselves to a small number of languages, but we
will keep the current user group happy.
> Both are
> necessary before we dive into grafting on an interpreter, and it's quite
> possible that if done right, they will obviate the desire for such a
grafting.
I would much prefer to use an existing configuration language if at
all possible. Inventing a new language usually means the product will
be delayed quite a bit longer than necessary. And why not take that
complication out of the project?
> (I argue that if we add an interpreter, we will have to change the internal
> language for two reasons: it's likely we will want to refer to services
> provided by modules written in language X in the .fvwm2rc, and we might wish
> to unload some of the bloat in the internal language to language X.)
I don't understand this, sorry.
/tonny
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Mon May 04 1998 - 02:20:23 BST