Re: [Amsn-devel] plugin system, the way we do it q

[<gag...@ma...>]

Le 04-09-21, =E0 13:24, Fish-face a =E9crit :

> Yes, we have transparency, but really, you have to remember the=20
> contents of evPar, anyway -
Well...we will have a documentation with a list of all postevents with=20=

all the contents of epVar. It's easiest than ask people to go directly=20=

into the code and try to find the name of the variable.

>  it wouldn't make much of a difference if the inner workings did=20
> change, and how often ARE the contents going to change?
Like Arieh said, that's better to have something "permanant" who=20
does'nt depend on aMSN code.
>
> I've long been a stout defender of the no evPar front :)
>
> I originally thought that evPar was so that, if you didn't need=20
> feedback, you wouldn't have to upvar the variable.
>
> Incidentally, you don't need to upvar evPar, as you can pass it as an=20=

> argument. The thing is, $evPar(nick) is pointless to me when its=20
> contents look like they're going to permanently be "nick."
>
> Not up to me, though!
G-Rom
eMail:  gag...@ma...
MSNMessenger:  gag...@ho...
iChat & AIM:  gagnonje5000 (sur Mac.com)
Skype: germinator5000