Re: Perl embedding: trial balloon
"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> wrote:
>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes:
Hrvoje> To rephrase: the C code I've written today is not
Hrvoje> guaranteed to be safe, and neither will John's code he
Hrvoje> writes tomorrow be guaranteed to be safe. But if he
Hrvoje> writes it well, the resulting Perl-Emacs combinations
Hrvoje> (what a horror) *will* be safe, and that's what counts.
[cut]
My impression is that John is looking for maximum Perl capability
for
the implementation effort (quite rightly by itself, of course), is
willing to trade off rare crashes for immediate power (his reaction
was "it works well for me"), and doesn't think that the implicit
`(require 'perl-stuff)' scenario is show-stoppingly important (his
initial reaction was "it's the Lisp programmer's problem"). That is
all I have to go on, so I know this may be an inaccurate
characterization of what he really thinks. But that's my impression.
John?
It is (or mostly was) a big task. I have trouble explaining to people
that yes, I have been working on it for several months, and no, it
doesn't do simple things like autoload Perl files yet, because my work
so far has been mostly on the core cross-language support.
My standards are the following: if anyone can crash a Perl-enabled
XEmacs using documented interfaces, then I can crash either a
Perl-disabled one or Perl using a similar trick.
I invite you to help me try to get Perlmacs to dump core... it feels
like I'm not making progress any more, it's been so long. :-)