Re: Unloading Perl scripts ...

[Peter Zelezny <zed@linux.com>]

On Sat, 13 Apr 2002 16:15:52 +0200
Frodo Baggins <thehobbit@altern.org> wrote:

> Running multiple interpreter is silly. First it will eat to much
> memory, second will forbid to have utility scripts. For instance, I
> have made a script which just adds rfc-like nick and channel name
> comparation. I use the function provided by this script in a lot of
> others. Obvioulsy I could make the script a perl module and have the
> script charging it, but then there will be say 10 copies of it in the
> memory...
> 
> By "perl based" I mean that the search for the handler and its
> execution will be a purely perl affair, using function defined in a
> perl module which will be loaded by the embedded interpreter on
> startup. From the point of view of the rest of xchat, nothing will
> change: it will still call some perl_inboud or perl_outbound function,
> but this will in turn call a perl sub and let it doing the
> job. Starting nerxt month I should have some free time and I could
> try to implement it if you people are interested.
> 
> 
> 
> Greetings

perl_inbound isn't even there anymore. You might want to take a look
at 1.9.x snapshots. It uses the C-plugin-interface, and acts like a proxy
between perl scripts and the C-interface. I think the most ideal solution
would show perl scripts in the PluginListGui, and allow you to Unload
plugins/scripts with the same button.

-- 
Peter Zelezny. <zed@xchat.org>
--
XChat-discuss: mailing list for XChat users
Archive:       http://mail.nl.linux.org/xchat-discuss/