On Feb 11, 4:01 pm, The Editor <[email protected]>
> Here's essentially what I'll be doing. Let's say you have a string
> like: term field=value 'two' three="3" and you pass it through
> BOLTargs. It comes back like this:
>
> [''][0] => term
> [''][1] => two
> [field] => value
> [three] => 3
>
> Now it will come back just like this, which should make it easier for
> plugin developers. Simple change, but will break some existing
> plugins, obviously.
>
> [1] => term
> [2] => two
> [field] => value
> [three] => 3
Dan -
just a question about Boltargs argument parsing:
Will the change prevent use of numeric parameter keys? Maybe they are
already not allowed, in which case there is no loss. But if they are
allowed, one could get into trouble.
~Hans
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
