>
> > I assume when you determine what | will be, i.e. which hex value
> less
> > than 0x20, you scan the string to be inserted to make sure there's
> no
> > collision?
>
>
> I don't right now. It uses 0x02. I might add, I guess. But I
> could not make it fool proof (pun intended).
As well as fools, there's handles, which by definition contain a
character less than 0x20. As long as (a) you, I, and any other plugin
writers know to not use 0x20 and (b) no one does anything foolish like
trying to pass a binary string via cb, not too many foolish things
likely to happen.
> > And: callbacks in same cases are not to a label in the same script,
> > but to a separate, named script. But your parameter processing
> could
> > be useful either in that situation too. Maybe
> >
> > you produce
> >
> > cbs(scriptname, label, arg1, arg2...)
> >
>
> I thought about this. Probably simpler just to use
> cb("[EMAIL PROTECTED]",...) ; pp just adds .
> cb("@label",...) ;; PP adds scriptname.
> cb("script",...) ;; pp adds just .
> this would break anybody that had used beta, but cleaner than two
> functions I think. I'll switch to this unless you can think of a
> reason not too.
Sounds good to me.
Attention: PowerPro's Web site has moved: http://www.ppro.org
SPONSORED LINKS
| Computer monitoring software | Power pro | Computer and internet software |
| Free computer monitoring software |
YAHOO! GROUPS LINKS
- Visit your group "power-pro" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
