>>>> "John" == John Tobey
<jtobey(a)channel1.com> writes:
John> I don't know any of the details of Mule, text properties,
John> intervals, etc., but Perl is quite flexible.
Text properties, intervals, etc are not part of XEmacs, which uses
extents as the implementation for these things. But Perl's
flexibility will be able to handle that. No problem.
But using "flexibility" and "Mule" in the same sentence scares me.
Mule is not flexible; we are not yet at a stage where we can have
efficiency in multi-lingual code without extreme discipline.
"Discipline" is not a word I associate with Perl[1], and still less with
Perl programmers.
That said, it's probably possible to use Perl as a scripting language
as long as Emchars and bufbytes are carefully kept opaque to the Perl
interpreter. Which will, of course drive Perl programmers up the
Wall. And further increase opposition to Mule, I suspect.
Oh, and don't disable that Ebola-detection code yet. A Perl
interpreter will introduce a whole new meaning to the word.
> In this case what you really want is XEmacs as a loadable
> module into perl!
John> uh-oh! You read my mind... ;-)
This is a MUCH better idea. Please consider using the external widget
interface instead.
Footnotes:
[1] Please read the Perl man page; that's my source for the statement.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
__________________________________________________________________________
__________________________________________________________________________
What are those two straight lines for? "Free software rules."