ch in the
original message.
Jonathan's explanation (below) seems to explain why that would be the case.
Thanks!
> Date: Sun, 27 Feb 2011 15:43:53 -0800 (PST)
> From: Jonathan Wilkes
> Subject: Re: [PD] unexpected behaviour in [route]
>
> In your quote of Miller's he
Hi,
I took the liberty to expand the OP's patch hopefully clearing some
doubts (warning fairly wide window).
Lorenzo
Mathieu Bouchard wrote:
On Sun, 27 Feb 2011, Jonathan Wilkes wrote:
"Route checks the first element of a message against each of its
arguments, [...] The part before the com
On Sun, 27 Feb 2011, rene beekman wrote:
I'm preparing some patches for courses that I teach and I noticed
behaviour in [route] that I found unexpected or at least inconsistent.
Attached is a patch that demonstrates the problem.
In short: when mixing types of arguments for [route], the object w
On Sun, 27 Feb 2011, Jonathan Wilkes wrote:
"Route checks the first element of a message against each of its
arguments, [...] The part before the comma is wrong-- that's not how
[route] works. The reality is: 1) If the first arg is a symbol atom,
then [route] is put in "selector" mode and che
ot;).
So what you quoted is the answer, as long as the questioner magically realizes
to
ignore everything before the comma.
* The parenthesis should be inside the period.
-Jonathan
--- On Sun, 2/27/11, Pedro Lopes wrote:
From: Pedro Lopes
Subject: Re: [PD] unexpected behaviour in [rout
The first paragraph of route-help states:
"which maybe numbers or symbols (but not a mixture of the two unless the
datatypes are defined explicitly)"
Its the answer.
See the help patch.
On Sun, Feb 27, 2011 at 10:40 PM, Jack wrote:
> This is not a bug.
> Just do something like this to avoid an
This is not a bug.
Just do something like this to avoid any problem :
[route number number number ...]/[route word word word ...]
++
Jack
Le dimanche 27 février 2011 à 22:46 +0200, rene beekman a écrit :
> I'm preparing some patches for courses that I teach and I noticed
> behaviour in [route]
I'm preparing some patches for courses that I teach and I noticed behaviour
in [route] that I found unexpected or at least inconsistent.
Attached is a patch that demonstrates the problem.
In short: when mixing types of arguments for [route], the object will fail
to properly route a float if the f
