-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hi jonathan,
great ideas!
On 2013-05-13 23:26, Jonathan Wilkes wrote:
- adding a function to make it easy to parse comma-separated
A_GIMME args to an object as named args. Thus for [someobject foo 1 2 3, bar 1 2 3 4, blah bee], there should be a function that can be used inside of someobject_new for which the author can ask for the "foo" args and retrieve "1 2 3" (maybe by returning the indices to the first and last arg of "foo"). That will match the syntax of message boxes and give external developers an easy and consistent way to do named
personally i would go for something much simpler when using comma-args: [someobject foo 1 2 3, bar 42] would translate to something like
[preinitbang] | [bar 42( | [someobject foo 1 2 3]
with [preinitbang] being executed immediately after the instantiation of [someobject], so it's guaranteed that [someobject] is not connected to anything yet (kind of the opposite of [loadbang]). [preinitbang] is only here for illustrative purposes, and shouldn't exist.
it all boils down to sending initialization messages to an object right after it was created.
the nice thing about this is, that it doesn't require *any* changes on the object's side in order to be able to use it out of the box in *most* cases.
i've been thinking about implementing this for some time now (though i never found any time to do it)...i just wanted to through it into discussion before there are several competing uses of comma-separated A_GIMME args.
fgmasdr IOhannes