[PD] select issues

[marius schebella]

got it. but it does not explain, the following:
[select 1 2 3]
has only one input. so no need to distribute anything. then send the 
message
[4 4 4 4(
no bang on the first outlet, but on the last one, but why is still only 
the first element on the list passed?
just want to point out, that select just does not work for messages.
marius.


Frank Barknecht wrote:
> Hallo,
> Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
> 
>> Hmm, I suppose it should pass thru every thing unmodified on the  
>> right outlet.  Can anyone think of any problems or disadvantages of  
>> [select] just outputting the unmatched input intact on the right outlet?
> 
> Yes, I can!
> 
> [select] like many objects distributes incoming messages over its
> inlets, so passing lists unchanged to the right outlet may let all
> hell break loose with old patches.
> 
> Example: 
> 
>   [5 5(
>   | 
>   |
>   [select] 
>   |     |
>   |     [print MISS]
>   |
>   [print HIT]
> 
> will *always* print HIT because the second "5" in the list will first
> set the value, that [select] selects, the left "5" then will trigger a
> hit. A message "1 2" however will always pass the 1 to the MISS
> outlet, after the 2 in the list has set the select-target.
> 
> Ciao