> It's only when the name is used as part pf a path
> (like C:/pd/extra/<~.dll) that the problem shows up.

Ok, but I still don't get how this problem manifests itself. 

Don't the externals load in every OS? Particularly, don't the cyclone objects load on every system even when declared? Because they do on MAC OS when declared.

And why do I need to use the [hexloader] object to load [<~] and [>~] from zexy?

> I would suggest using [lt] and [gt] for 'less than' and 'greater
> than' as is done in many assembly languages.

In fact, in Max, you can load [>~] as [greaterthan~], all the nettles objects have actually other such names

[greaterthaneq~] for [>=~], [lessthan~] and [lessthaneq~] for [<~] and [<=~]

[equals~] for [==~]

[notequals~] for [!=~]

[plusequals~] for [+=~]

[rminus~] for [!-~] ([rminus] for [!-])

[rdiv~] for [!/~] ([rdiv] for [!/])

[modulo~] for [%~]

perhaps we could use this

cheers




2016-02-14 13:43 GMT-02:00 Martin Peach <chakekatzil@gmail.com>:
On Sun, Feb 14, 2016 at 10:00 AM, Alexandre Torres Porres <porres@gmail.com> wrote:
Not all operating systems like the '<' and '>' in the object names

I'm aware there's some issue of OS not liking such object names, but I don't get it.

For example, [<] and [>] are vanilla objects, don't they load in every OS?

They load because they are built-in so Pd doesn't need to go to the OS filesystem to find them. It's only when the name is used as part pf a path (like C:/pd/extra/<~.dll) that the problem shows up. I would suggest using [lt] and [gt] for 'less than' and 'greater than' as is done in many assembly languages.

Martin

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list