#83 [value] and [send]/[receive] share the same name

[IOhannes m zmölnig]

[value] and [s] don't like if they are used with the
same name.

e.g. the following will output "[value]: no method for
bang"

[bang(
|
[s bla]

[value bla]

[Anonymous]

Logged In: YES
user_id=801174

To me it's normal that [r] and [value] share the same
symbol-table using exactly the same field (s_thing).

Why should it be different?

[IOhannes m zmölnig]

as reported by jonathan wilkes (#2946990 ), this also effects [catch~]/[throw~]

https://sourceforge.net/tracker/index.php?func=detail&aid=2946990&group_id=55736&atid=478070

[IOhannes m zmölnig]

and just to cover more cases:

it's perfectly allowed to use the same name for [catch~]/[throw~] and [send~]/[receive~].

[IOhannes m zmölnig]

[send]/[receive] and [send~]/[receive~] _can_ live side by side, but can also expose side-effects.

e.g. [receive~ foo] will receive data from [send~ foo] (and not care about [send foo], as long as a signal is actually connected to the [send~ foo].
if no signal is connected to [send~ foo], then [receive~ foo] will receive the values from [send foo].

see attached patch sendnames.pd

[IOhannes m zmölnig]

[send] and [receive~] (not) sharing names