Hi list, What's the story on the following patch?
[initbang]/[closebang] for patch constructor/destuctor - ID: 1544041
I know it says the status is "open," but on the other hand this patch was added in 2006. From the related threads on pd user and dev, all I've seen are repeated hopes from various developers that these objects be included as internal objects in pd.
The only negative comment I've seen was indirectly from dmotd on 2009-03-14, quoting Miller:
"Anyhow, I'm trying to think of a better mechanism for allowing abstractions to have variable numbers of inlets/outlets, so I'm hoping initbang won't be necessary in the long run.
closebang, though, will probably be needed in some form or other."
I'd like to ask: what is the problem with [initbang] as it is, and what would a "better mechanism" look like? If a "better mechanism" is not currently in the works, could these two objects be included in pd-vanilla so that in the meantime people can make abstractions that have dynamic numbers of inlets/outlets that will work on both versions of pd? (I've never used [closebang] but I imagine the same reasoning holds for it as well.)
Similar questions about: $@ and $# expansion (argc, argv) - ID: 1543850
It looks like the discussion just stopped, and I couldn't find any threads on user or dev list. $@ would be very useful, as well as matju's suggestion about some kind of "nth argument and all the rest that follow."
-Jonathan
On Sat, 19 Jun 2010, Jonathan Wilkes wrote:
2009-03-14, quoting Miller: "Anyhow, I'm trying to think of a better mechanism for allowing abstractions to have variable numbers of inlets/outlets, so I'm hoping initbang won't be necessary in the long run."
If he were really trying, he would have found something or would have asked for advice. But no.
There's also a problem with always waiting for the best solution at the expense of finding a solution at all, NOW, or five years ago.
I'd like to ask: what is the problem with [initbang] as it is, and what would a "better mechanism" look like?
Whatever it is, it can't be supporting variable number of signals. What I thought about, is that you could have a [inlets] just like GF's [receives] that does multiple-receive. You first get the receive-symbol from the right outlet, the actual content from the left outlet. For [inlets] it would be the same, except you get an inlet-number out of the right-outlet. It's the only way you can do it without dynamic-patching. That's a cool solution, but it also doesn't support signals at all.
Thus you still need [initbang] and dynamic patching.
Are there any other reasons to use [initbang] ? I can't think of any, but I have the impression that I'm forgetting about something.
Well, actually, you can send to a toplevel iemgui's receive-symbol at loadbang-time, but you can send to an abstraction's receive-symbol at loadbang-time ONLY WHEN the receive-symbol is not computed at loadbang-time. Else the loadbang-order will not be reliable.
It took me a while to think of that one, but it makes me believe that we'd eventually hit limitations and have to do weird workarounds because of those limitations if there's no [initbang], for things not related to variable number of inlets.
If a "better mechanism" is not currently in the works, could these two objects be included in pd-vanilla so that in the meantime people can make abstractions that have dynamic numbers of inlets/outlets that will work on both versions of pd?
do you have Miller's phone number ?
(I've never used [closebang] but I imagine the same reasoning holds for it as well.)
[closebang] would be usually used for wholly different reasons. All the examples for [closebang] are unrelated to why pd needs [initbang]. The only reason why they're put together, is because they are two classes that are related to loadbang as all three send a bang at a specific special moment.
It looks like the discussion just stopped, and I couldn't find any threads on user or dev list.
What can you say more, on stuff that gets rejected without proper feedback, or ignored, for years ? At this point I would just say :
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
http://uncyclopedia.wikia.com/wiki/File:WOF-aaa.jpg
http://uncyclopedia.wikia.com/wiki/AAAAA
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
The first is included in Pd-extended, the second could be if someone
wants to refactor it so that the patch applies. I can't speak for
what's in Miller's trunk.
.hc
On Jun 19, 2010, at 6:55 PM, Jonathan Wilkes wrote:
Hi list, What's the story on the following patch?
[initbang]/[closebang] for patch constructor/destuctor - ID: 1544041
I know it says the status is "open," but on the other hand this
patch was added in 2006. From the related threads on pd user and dev, all I've seen
are repeated hopes from various developers that these objects be included as
internal objects in pd.The only negative comment I've seen was indirectly from dmotd on 2009-03-14, quoting Miller:
"Anyhow, I'm trying to think of a better mechanism for allowing
abstractions to have variable numbers of inlets/outlets, so I'm hoping initbang
won't be necessary in the long run.closebang, though, will probably be needed in some form or other."
I'd like to ask: what is the problem with [initbang] as it is, and
what would a "better mechanism" look like? If a "better mechanism" is not
currently in the works, could these two objects be included in pd-vanilla so
that in the meantime people can make abstractions that have dynamic numbers of inlets/outlets that will work on both versions of pd? (I've never
used [closebang] but I imagine the same reasoning holds for it as well.)Similar questions about: $@ and $# expansion (argc, argv) - ID: 1543850
It looks like the discussion just stopped, and I couldn't find any
threads on user or dev list. $@ would be very useful, as well as matju's suggestion about some
kind of "nth argument and all the rest that follow."-Jonathan
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
If nature has made any one thing less susceptible than all others of
exclusive property, it is the action of the thinking power called an
idea, which an individual may exclusively possess as long as he keeps
it to himself; but the moment it is divulged, it forces itself into
the possession of everyone, and the receiver cannot dispossess himself
of it. - Thomas Jefferson