FriFlo

I have attached a little example: I want to send different combinations of two integers (in this example always starting with 1) to the match object.

I would expect the match object only to send "1 1" to its outlet, when it receives the list "1 1". However, it also sends "11" for any consecutive two-number-list, that just starts with a 1 ...

When I send "1 0" "1 1" " 1 2", the match object only received 3 consecutive 1s, therefore it should not send again at the time it gets to "1 2".

Is that a bug or did I understand something wrong with the object?

I have attached a little example: I want to send different combinations of two integers (in this example always starting with 1) to the match object.
I would expect the match object only to send "1 1" to its outlet, when it receives the list "1 1". However, it also sends "11" for any consecutive two-number-list, that just starts with a 1 ...
I wouldn't expect that:
When I send "1 0" "1 1" " 1 2", the match object only received 3 consecutive 1s, therefore it should not send again at the time it gets to "1 2".
Is that a bug or did I understand something wrong with the object?

problem-with-match-object-or-bug

I don't think it's a bug. However, perhaps the way match works is not the way you expect. Every number that comes in the left inlet -- whether individually or as part of a list -- gets used, in order, for the list-matching comparison.

So, if it is looking for the list "1 1" and you send in lists "0 1", "1 1", "1 2", and "1 3" in that order, it's as if match had received "1 0 1 1 1 2 1 3", and in that message it can find two matches for "1 1": at the 3rd and 4th items, and at the 4th and 5th items. So when you send in the message "1 1" it finds a match between those two, and when you next send in "1 2" it finds a match between the second 1 of the previous message and the first 1 of the current message, and it reports a successful match even though the current message (the way you're thinking of it) is not in and of itself a match.

You could try sending match a 'clear' message after every input message if you want it to behave more as you'd like.

Ah, thanks! That did the trick, although I also found another way in the mean time with an expr. I just expected the match object to behave that way ... thanks for letting me know!

problem with match object (or bug?)