-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 14/05/13 08:47, IOhannes m zmoelnig wrote:
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.
[snip]
personally i would go for something much simpler when using comma-args:
[snip]
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.
Yes, I really like this syntax and having it as standard would be really very nice.
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.
GridFlow has this syntax already for all its C++ classes (not sure about [#expr], actually), and maybe the [args] object in GridFlow supports it too for abstractions:
[object some arguments, message to object, another message]
However, this will conflict with:
[expr],[expr~],[fexpr~] [lexpr] (expr that can change expression on the fly; pdlua example)
I think it would be best if typed creators and A_GIMME supported it (so most classes would get this bonus feature automatically), if you need the commas explicitly as arguments then perhaps A_GIMME_MORE could be defined with the current behaviour, so fixing externals that need it (a tiny minority?) would be a 5-character change.
Claude