[PD-dev] [ pure-data-Bugs-1415589 ] Sending a list to [select] can leave it in an unusable state

SourceForge.net noreply at sourceforge.net
Mon Jan 30 23:22:17 CET 2006


Bugs item #1415589, was opened at 2006-01-26 13:49
Message generated for change (Comment added) made by matju
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1415589&group_id=55736

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: None
Status: Closed
Resolution: None
Priority: 2
Submitted By: Frank Barknecht (fbar)
Assigned to: Miller Puckette (millerpuckette)
Summary: Sending a list to [select] can leave it in an unusable state

Initial Comment:
A [select] object primed with a symbol argument will
reset itself into an unusable state by sending it a
list with at least two elements. 

Attached patch illustrates this behaviour using a
[select x]-object. Sending a message [symbol x( will
normally make the left outlet generate a bang. However
sending a message [list x y( will disturb the [select
x] object, so that it will not correctly react to a
second [symbol x( message, until reset by a [symbol x(
message to its rigth inlet.  


----------------------------------------------------------------------

Comment By: Mathieu Bouchard (matju)
Date: 2006-01-30 17:22

Message:
Logged In: YES 
user_id=801174

there are two different classes called [select]. I don't
really know why there are two, and why the one that gets
used when there is more than one argument doesn't create any
extra inlets.

Shouldn't extra inlets be added?

----------------------------------------------------------------------

Comment By: Frank Barknecht (fbar)
Date: 2006-01-30 04:40

Message:
Logged In: YES 
user_id=569446

I agree, lets just close it. But as [select] doesn't always
have two inlets, this distributing of lists for [select
something] may not be obvius to everyone.


----------------------------------------------------------------------

Comment By: Mathieu Bouchard (matju)
Date: 2006-01-29 23:41

Message:
Logged In: YES 
user_id=801174

It's not a bug. 
 
This behaviour is consistent with many Pd classes, in which 
a list behaves like its $2 value goes in right inlet and 
then its $1 value goes in left inlet. This could be called 
"the implicit [unpack] rule", except that it's not 
necessarily as type-crippled as the real [unpack] is. 
 
By default, each object that doesn't have a listmethod 
defined will have a default one that performs the implicit 
[unpack], if i understand correctly. 
 

----------------------------------------------------------------------

Comment By: Frank Barknecht (fbar)
Date: 2006-01-26 15:00

Message:
Logged In: YES 
user_id=569446

I down-priorized this, as it's not a real bug, the
documentation just doesn't mention what will happen if lists
are sent to [symbol x].

I'd suggest to update the documentation to explain, that
like many objects in Pd [select] distributes lists over its
inlets as well, which has to be taken into account when
looking for unusual behaviour. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1415589&group_id=55736




More information about the Pd-dev mailing list