Re: [PD] objects with no alphanumerical names, how to build them?

[Alexandre Torres Porres]

2016-04-05 16:03 GMT-03:00 cyrille henry :

> experience told me that if you are looking for trouble, you will find them
> at some point.
>

I hear you, it's just that I found that zexy library with such files
compiled and all, so I naively thought that there was an easy way out of
all these troubles.

I remember I had asked about that before, not on this thread only, but it
was never cleared to me, so I had to figure out by myself now how zexy
works in windows: it does use those weird names that require hexloader, so
it can't run on vanilla on windows. That's nice to learn.

Anyway, seems that loading these objects as a library is the only clean and
safe solution for trouble.

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

Re: [PD] objects with no alphanumerical names, how to build them?

[Jonathan Wilkes via Pd-list]

I'd like to make a Request for Peer Pressure:
Externals should only use alphanumeric characters and the underscore character.
Exceptions are: classes that should have long ago shipped with Vanilla, classes 
to gain compatibility with Max/MSP, 
domain-specific operators for a monolithic external library (i.e., one where 
you're probably going to load the entire 
library rather than individual classes from it), and legacy pd-extended bunk.
So learning about hexloader is good, maintaining zexy/cyclone is good, 
documenting problem characters on 
various OSes is good, shipping an external with a creator ":)" is bad.
-Jonathan


 

On Tuesday, April 5, 2016 2:37 PM, Alexandre Torres Porres 
 wrote:
 

 2016-04-05 12:26 GMT-03:00 Roman Haefeli :

On Windows, for instance, you can't have ? < > | : * \ / " in filenames.

I just confirmed you can't have those characters in a .dll file
So, besides these characters in Windows, what are other forbiden ones in other 
operational systems we run pd on?
I have Mac Os and it seems only colon (:) is prohibited (as in windows), or dot 
(.) at the beginning of a file.
How about Linux?
cheers
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list


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

Re: [PD] objects with no alphanumerical names, how to build them?

[Roman Haefeli]

On Die, 2016-04-05 at 15:32 -0300, Alexandre Torres Porres wrote:
> 2016-04-05 12:26 GMT-03:00 Roman Haefeli :
> On Windows, for instance, you can't have ? < > | : * \ / " in
> filenames.
> 
> 
> I just confirmed you can't have those characters in a .dll file

Just to be clear, it's not about the dll file or the dll fileformat. The
restricting factor is the file system (and probably the operating
system). 

> So, besides these characters in Windows, what are other forbiden ones
> in other operational systems we run pd on?

As I said, it depends rather on the file system than on the operating
system. Ext4, for instance, allows almost anything except / and \0
('null'). And the file names '.' '..' are restricted, too. '..pd_linux'
would theoretically work, but it would be a hidden file. I guess most
distros wouldn't allow to distribute a file with such a name. 

> I have Mac Os and it seems only colon (:) is prohibited (as in
> windows), or dot (.) at the beginning of a file.

Also here, the hfs+ file system has that restriction, not necessarily OS
X (though OS X and hfs+ are likely congruent). 

> How about Linux?

I guess most modern file systems have very few restrictions. However,
fat32 has certainly not less restrictions than ntfs (if not more) and it
can be mounted on Linux. And it is still widely used, on USB sticks or
whatsoever. It's not totally unreasonable to assume that someone runs Pd
from a fat32 formatted USB stick, thus it probably makes sense not to
assume a modern file system. I haven't tried, but I wouldn't be
surprised if a Debian system even works from a fat32 formatted USB
stick, simply because they restrict themselves to sane file names.

Some more details might be found here:
https://kb.acronis.com/content/39790

Roman






signature.asc
Description: This is a digitally signed message part
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] objects with no alphanumerical names, how to build them?

[cyrille henry]

the problem did not came only from OS, but also from the filesystem.

dot at the beginning of the file usually mean that the file is hidden (but 
exist).

on a ext4 partition, only / is not possible in your list.

i don't know about fat : since it's the only filesystem that allow to be read / 
write by the 3 major OS, it's important to test.

i also don't know about what happen on a DVDROM.

experience told me that if you are looking for trouble, you will find them at 
some point.

cheers
c



Le 05/04/2016 20:32, Alexandre Torres Porres a écrit :

2016-04-05 12:26 GMT-03:00 Roman Haefeli >:

On Windows, for instance, you can't have *? < > | : * \ / "* in filenames.


I just confirmed you can't have those characters in a .dll file

So, besides these characters in Windows, what are other forbiden ones in other 
operational systems we run pd on?

I have Mac Os and it seems only colon (*:*)**is prohibited (as in windows), or 
dot (.) at the beginning of a file.

How about Linux?

cheers


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



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

Re: [PD] objects with no alphanumerical names, how to build them?

[Roman Haefeli]

On Die, 2016-04-05 at 13:25 -0300, Alexandre Torres Porres wrote:
> 2016-04-05 12:26 GMT-03:00 Roman Haefeli :
> (Then there was the issue with object name aliases, so that
> you could load [s2l] only after having created [symbol2list],
> but this
> is another story).
> 
> 
> Roman, I've been asking about that too. I had an object like
> [equals~], and I wanted to have [==~] as an alias - but I can only do
> it after I first load [equals~].
> 
> 
> How does it work? An alias is only possible if you load the externals
> as a library? Not as a single object binary? Seems so, but i'm just
> confirming

Please someone correct me, but I think it's because the alias name is
only registered after the dll file has been loaded and the dll can only
be loaded by its filename. Pd doesn't know about a '==~' class until the
'equals~.dll' has been loaded that registers the '==~' class. 

Roman 



signature.asc
Description: This is a digitally signed message part
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] objects with no alphanumerical names, how to build them?

[Alexandre Torres Porres]

2016-04-05 12:26 GMT-03:00 Roman Haefeli :

> On Windows, for instance, you can't have *? < > | : * \ / "* in filenames.


I just confirmed you can't have those characters in a .dll file

So, besides these characters in Windows, what are other forbiden ones in
other operational systems we run pd on?

I have Mac Os and it seems only colon (*:*) is prohibited (as in windows),
or dot (.) at the beginning of a file.

How about Linux?

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

Re: [PD] objects with no alphanumerical names, how to build them?

[IOhannes m zmölnig]

On 04/05/2016 05:35 PM, Ivica Ico Bukvic wrote:
> Another thought could be having hexloader be folded into core pd...

well, a trimmed down hexloader *is* included in Pd-vanilla.

however, it only handles the case for ordinary non-alpha characters and
is lacking an escape mechanism for characters prohibited by the filesystem.

gfmadsr
IOhannes



signature.asc
Description: OpenPGP digital signature
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] objects with no alphanumerical names, how to build them?

[Alexandre Torres Porres]

2016-04-05 12:26 GMT-03:00 Roman Haefeli :

> (Then there was the issue with object name aliases, so that
> you could load [s2l] only after having created [symbol2list], but this
> is another story).
>

Roman, I've been asking about that too. I had an object like [equals~], and
I wanted to have [==~] as an alias - but I can only do it after I first
load [equals~].

How does it work? An alias is only possible if you load the externals as a
library? Not as a single object binary? Seems so, but i'm just confirming

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

Re: [PD] objects with no alphanumerical names, how to build them?

[Alexandre Torres Porres]

2016-04-05 12:11 GMT-03:00 Martin Peach :

> You're lucky that OSX accepts filenames like ==~.pd_darwin. Will it also
> accept *~.pd_darwin? Or <~.pd_darwin?
>

Yeah Martin, I can name the .pd_darwin objects to almost whatever, I've
been testing here and the only problem so far is a file containing ":" or
starting with a "." - but even something like ¿~.pd_darwin is fine :)

What OS are you on? And what is the deal there?

And, like I've been saying, I downloaded
*zexy-v0-0extended-(Darwin-i386-32)(Darwin-PowerPC-32)(Darwin-x86_64-32)-externals.tar*

it has compiled objects as <~.pd_darwin but also 0x3c0x7e.pd_darwin

not sure how that is for another OS, can you tell me what happens in yours?

Anyway, I got my cues from the code in zexy to compile a ==~ object and I'm
pretty sure it will work for other things like <~ and whatever here on Mac
Os, but I haven't tried another yet (will do soon).

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

Re: [PD] objects with no alphanumerical names, how to build them?

[Jonathan Wilkes via Pd-list]

Let's wait to see if we ever get a bug report about that.  AFAICT Pd-l2ork 
loads what needs to be loaded-- "susceptible to" isn't a good reason to awaken 
the makefile monster.

-Jonathan 

On Tuesday, April 5, 2016 11:38 AM, Ivica Ico Bukvic  wrote:
 

  Another thought could be having hexloader be folded into core pd... It is 
currently autoloaded in pd-l2ork but that approach is still susceptible to 
overrides to the default config. Perhaps we should fold it into pd-l2ork? An 
alternative is having aliases...
 
 On 4/5/2016 10:43 AM, Alexandre Torres Porres wrote:
  
 
 
 2016-04-05 5:08 GMT-03:00 Roman Haefeli :
 
 If you're simply interested in knowing how things work technically, fine.
 
  I'd love to know, for sure, that's why I'm asking :)    
Now that we have a chance to get rid of all hexloader related kludges,
 now you come and bring it up again.
 
  You see, I don't really get what you mean by "hexloader" or its related 
kludges. All I know is some [hexloader] object that is in my pd extended 
0.42-5, and all I know is that I need to use it in order to load the [==~] 
object from zexy. What you're talking about, somehow, relates to that?  
  Anyway, seems so to me... and if so, the thing is that what I'm asking and 
doing has nothing to do with "hexloader"... (I never even mentioned about 
"hexloader", btw) ... and I read about the "hex loader" discussion as 
suggested, and found stuff that I didn't really think was related to my 
questions. Yeah, like I said, I don't really know much and I'd like to know, so 
I might be missing something, and someone can help me  with it...  
  But the thing is, all I asked was how to compile an object like [==~] and 
make it load without being part of a library. I found on deken a zexy version 
that seemed to do that (specifically: 
zexy-v0-0extended-(Darwin-i386-32)(Darwin-PowerPC-32)(Darwin-x86_64-32)-externals.tar).
 And it didn't need a [hexloader] object too, by the way. 
  I didn't get an answer, but me and my colleague were checking the source code 
from zexy and found some cues. We tried it... and it works! 
  Now I have an object that is compiled as [==~], it's not part of a library, 
and it loads and works on pd vanilla 0.46-7 64 bits, pd vanilla 0.46-7 32 bits 
and also Pd-Extended 0.42-5 (without the need of the [hexloader] object by the 
way). All you need is the ==~.pd_darwin object in a search path. 
  
  Speaking and thinking as a user, I think it is easy and great to have a 
working and compiled object that just loads and works, so that is what I 'm 
after. 
  But anyway, yeah, I wanna know what are the dangers and all... 
  cheers 
  
 
  
 ___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list
 
 
 
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list


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

Re: [PD] objects with no alphanumerical names, how to build them?

[Alexandre Torres Porres]

2016-04-05 12:35 GMT-03:00 Ivica Ico Bukvic :

> Another thought could be having hexloader be folded into core pd...
>

sounds reasonable
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] objects with no alphanumerical names, how to build them?

[cyrille henry]

Le 05/04/2016 17:26, Roman Haefeli a écrit :
...

I maybe was over-dramatizing the situation,


i don't think you are over dramatizing.
I've developed a fear of using externals in pd since the hexloader/zexy story.

10 years of vanilla only patching IS over-dramatizing. ;-)

cheers
c

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

Re: [PD] objects with no alphanumerical names, how to build them?

[Alexandre Torres Porres]

2016-04-05 12:26 GMT-03:00 Roman Haefeli :

> it's not possible to have >~.dll


I don't have windows, so please explain me better. Does window forbid a
file to be named >~.dll or is there a problem with an existing  >~.dll file
being uploaded into Pd?

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

Re: [PD] objects with no alphanumerical names, how to build them?

[Ivica Ico Bukvic]

Another thought could be having hexloader be folded into core pd... It 
is currently autoloaded in pd-l2ork but that approach is still 
susceptible to overrides to the default config. Perhaps we should fold 
it into pd-l2ork? An alternative is having aliases...


On 4/5/2016 10:43 AM, Alexandre Torres Porres wrote:



2016-04-05 5:08 GMT-03:00 Roman Haefeli >:


 If you're simply interested in knowing how things work
technically, fine.


I'd love to know, for sure, that's why I'm asking :)

Now that we have a chance to get rid of all hexloader related kludges,
now you come and bring it up again.


You see, I don't really get what you mean by "hexloader" or its 
related kludges. All I know is some [hexloader] object that is in my 
pd extended 0.42-5, and all I know is that I need to use it in order 
to load the [==~] object from zexy. What you're talking about, 
somehow, relates to that?


Anyway, seems so to me... and if so, the thing is that what I'm asking 
and doing has nothing to do with "hexloader"... (I never even 
mentioned about "hexloader", btw) ... and I read about the "hex 
loader" discussion as suggested, and found stuff that I didn't really 
think was related to my questions. Yeah, like I said, I don't really 
know much and I'd like to know, so I might be missing something, and 
someone can help me with it...


But the thing is, all I asked was how to compile an object like [==~] 
and make it load without being part of a library. I found on deken a 
zexy version that seemed to do that (specifically: 
/zexy-v0-0extended-(Darwin-/i386-32)(Darwin-PowerPC-32)(Darwin-x86_64-32)-externals./tar/). 
And it didn't need a [hexloader] object too, by the way.


I didn't get an answer, but me and my colleague were checking the 
source code from zexy and found some cues. We tried it... and it works!


Now I have an object that is compiled as [==~], it's not part of a 
library, and it loads and works on pd vanilla 0.46-7 64 bits, pd 
vanilla 0.46-7 32 bits and also Pd-Extended 0.42-5 (*_without_* the 
need of the [hexloader] object by the way). All you need is the 
==~.pd_darwin object in a search path.



Speaking and thinking as a user, I think it is easy and great to have 
a working and compiled object that just loads and works, so that is 
what I 'm after.


But anyway, yeah, I wanna know what are the dangers and all...

cheers




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


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

Re: [PD] objects with no alphanumerical names, how to build them?

[Roman Haefeli]

Ok. You were lucky to have chosen '==' as an object name, then.

The insanity begins, when the object names use characters that are
forbidden by some file systems. On Windows, for instance, you can't
have ? < > | : * \ " in filenames. This means, if you want to be able to
load such an object, you need some mechanism to substitute those
characters by something that is allowed.

This is where hexloader comes into play. It was necessary because
Pd-extended decided to split libraries into single-object-files, so that
each object has its own dll|pd_darwin|pd_linux file. However, it's not
possible to have >~.dll. The problem got worked-around by substituting
the forbidden characters by their hexadecimal representation.  I don't
know the exact details, but hexloader enabled Pd to search not only for
the name you entered into the object box, but also for its hex counter
part. This means you could create an object [>~] and Pd would load
0x3e0x7e.dll, if it was available.

All this caused some degree of confusion, since hexloader wasn't loaded
per default in Pd-extended. This means, after [import zexy] you were
able to create [symbol2list], but not [>~]. You had to [import
hexloader], too, to be able to use [>~]. This created troubles for quite
many users. (Then there was the issue with object name aliases, so that
you could load [s2l] only after having created [symbol2list], but this
is another story).

All this was never an issue with the canonical zexy library, because
everything is packed in zexy.dll|pd_darwin|pd_linux. Once you load zexy,
all its classes simply worked. 

I maybe was over-dramatizing the situation, since your example with [==]
seems to work fine. However, since Pd-extended has reached its end of
life, we should take the chance to learn from its mistakes and I
consider the forceful splitting of libraries a mistake and the proposed
solution with hexloader a kludge. It might would make things a bit more
straight forward, if hexloader was part of Pd, but that's not likely to
happen (I remember Miller having expressed hesitation). And the whole
hexloader thing is currently not necessary as long as external authors
put their classes with 'weird' names into multi-object libraries with
'sane' names or use only 'sane' names for their single-object
externals.  

I hope I could make things a bit more clear and my explanations stick to
the facts.

Roman


On Tue, 2016-04-05 at 11:43 -0300, Alexandre Torres Porres wrote:
> 
> 
> 2016-04-05 5:08 GMT-03:00 Roman Haefeli :
>  If you're simply interested in knowing how things work
> technically, fine.
> 
> 
> I'd love to know, for sure, that's why I'm asking :)
>  
> Now that we have a chance to get rid of all hexloader related
> kludges,
> now you come and bring it up again.
> 
> 
> You see, I don't really get what you mean by "hexloader" or its
> related kludges. All I know is some [hexloader] object that is in my
> pd extended 0.42-5, and all I know is that I need to use it in order
> to load the [==~] object from zexy. What you're talking about,
> somehow, relates to that? 
> 
> 
> Anyway, seems so to me... and if so, the thing is that what I'm asking
> and doing has nothing to do with "hexloader"... (I never even
> mentioned about "hexloader", btw) ... and I read about the "hex
> loader" discussion as suggested, and found stuff that I didn't really
> think was related to my questions. Yeah, like I said, I don't really
> know much and I'd like to know, so I might be missing something, and
> someone can help me with it...
> 
> 
> But the thing is, all I asked was how to compile an object like [==~]
> and make it load without being part of a library. I found on deken a
> zexy version that seemed to do that
> (specifically: 
> zexy-v0-0extended-(Darwin-i386-32)(Darwin-PowerPC-32)(Darwin-x86_64-32)-externals.tar).
>  And it didn't need a [hexloader] object too, by the way.
> 
> 
> I didn't get an answer, but me and my colleague were checking the
> source code from zexy and found some cues. We tried it... and it
> works!
> 
> 
> Now I have an object that is compiled as [==~], it's not part of a
> library, and it loads and works on pd vanilla 0.46-7 64 bits, pd
> vanilla 0.46-7 32 bits and also Pd-Extended 0.42-5 (without the need
> of the [hexloader] object by the way). All you need is the
> ==~.pd_darwin object in a search path.
> 
> 
> 
> 
> Speaking and thinking as a user, I think it is easy and great to have
> a working and compiled object that just loads and works, so that is
> what I 'm after.
> 
> 
> But anyway, yeah, I wanna know what are the dangers and all...
> 
> 
> cheers
> 
> 
> 
> 



signature.asc
Description: This is a digitally signed message part
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] objects with no alphanumerical names, how to build them?

[Jonathan Wilkes via Pd-list]

Here's some Pd Fan Fiction:

Relational sigop author: Hey I got relational sigops.  You want them?
Pd author: Yeah thanks, I forgot about those. *copy/paste*Pd community: Yay!

Fin.
-Jonathan


On Tuesday, April 5, 2016 10:46 AM, Alexandre Torres Porres 
 wrote:
 

 

2016-04-05 5:08 GMT-03:00 Roman Haefeli :

 If you're simply interested in knowing how things work technically, fine.

I'd love to know, for sure, that's why I'm asking :) 
Now that we have a chance to get rid of all hexloader related kludges,
now you come and bring it up again.

You see, I don't really get what you mean by "hexloader" or its related 
kludges. All I know is some [hexloader] object that is in my pd extended 
0.42-5, and all I know is that I need to use it in order to load the [==~] 
object from zexy. What you're talking about, somehow, relates to that? 
Anyway, seems so to me... and if so, the thing is that what I'm asking and 
doing has nothing to do with "hexloader"... (I never even mentioned about 
"hexloader", btw) ... and I read about the "hex loader" discussion as 
suggested, and found stuff that I didn't really think was related to my 
questions. Yeah, like I said, I don't really know much and I'd like to know, so 
I might be missing something, and someone can help me with it...
But the thing is, all I asked was how to compile an object like [==~] and make 
it load without being part of a library. I found on deken a zexy version that 
seemed to do that (specifically: 
zexy-v0-0extended-(Darwin-i386-32)(Darwin-PowerPC-32)(Darwin-x86_64-32)-externals.tar).
 And it didn't need a [hexloader] object too, by the way.
I didn't get an answer, but me and my colleague were checking the source code 
from zexy and found some cues. We tried it... and it works!
Now I have an object that is compiled as [==~], it's not part of a library, and 
it loads and works on pd vanilla 0.46-7 64 bits, pd vanilla 0.46-7 32 bits and 
also Pd-Extended 0.42-5 (without the need of the [hexloader] object by the 
way). All you need is the ==~.pd_darwin object in a search path.

Speaking and thinking as a user, I think it is easy and great to have a working 
and compiled object that just loads and works, so that is what I 'm after.
But anyway, yeah, I wanna know what are the dangers and all...
cheers


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


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

Re: [PD] objects with no alphanumerical names, how to build them?

[Martin Peach]

On Tue, Apr 5, 2016 at 10:43 AM, Alexandre Torres Porres 
wrote:

>
> Now I have an object that is compiled as [==~], it's not part of a
> library, and it loads and works on pd vanilla 0.46-7 64 bits, pd vanilla 
> 0.46-7
> 32 bits and also Pd-Extended 0.42-5 (*without* the need of the
> [hexloader] object by the way). All you need is the ==~.pd_darwin object
> in a search path.
>
>
> Speaking and thinking as a user, I think it is easy and great to have a
> working and compiled object that just loads and works, so that is what I 'm
> after.
>
> But anyway, yeah, I wanna know what are the dangers and all...
>
>
You're lucky that OSX accepts filenames like ==~.pd_darwin. Will it also
accept *~.pd_darwin? Or <~.pd_darwin?
Usually objects with weird names (names that are illegal as file names)
need to be set up in a library first, so that their names can be registered
without Pd having to search the filesystem for them.

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

Re: [PD] objects with no alphanumerical names, how to build them?

[Roman Haefeli]

On Mon, 2016-04-04 at 18:42 -0300, Alexandre Torres Porres wrote:
> howdy, I know I kinda asked about this before on the list, but now I'm
> really committed to understanding and building objects with "weird
> character" names, like [==~].

Speaking as user, please don't. Don't find out about it, don't create
such externals, don't distribute them. The world was fine before
Pd-extended split up perfectly working libraries into
single-object-per-file libraries that required stuff like hexloader
exactly because of the very issue you seem to show interest in. Although
it technically worked, hexloader was not loaded per default and this
meant that some objects of a library simply worked, while others didn't
until hexloader got loaded and it confused the hell out of people. 

Now that we have a chance to get rid of all hexloader related kludges,
now you come and bring it up again. If you're simply interested in
knowing how things work technically, fine. If you plan to work on such
externals, puulleeaaazeee reconsider for the sake of the sanity of
this community.

Thanks,
Roman




signature.asc
Description: This is a digitally signed message part
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] objects with no alphanumerical names, how to build them?

[Alexandre Torres Porres]

I also asked something in my first email and I hope I can confirm it


I tried making a second name - or an "alias" - for [equals~] (using C.2.9
class_addcreator C.2.9 in
http://pdstatic.iem.at/externals-HOWTO/pd-externals-HOWTOse8.html )

But it didn't seem to work. I can get [==~] to instantiate as an alias, but
only after I first instantiate it as "[equals~]".

So, what's the deal, when does this aliasing work? Only if you load it as a
library?


2016-04-05 1:19 GMT-03:00 Alexandre Torres Porres :

> Well, I also found this zexy git https://git.iem.at/pd/zexy/
>
> not sure how it compiles to objects like ==~ - coz i couldn't compile. But
> my colleague, Flavio, checked it out, and seems to have realized about the
> trick to compile an object as "==~". We did it and I compiled it for Mac Os
> and it is working.
>
> By the code from the git above as a model, we changed the original code
> from:
>
>
>
>
>
>
>
> *void equals_tilde_setup(void){ equals_class =
> class_new(gensym("equals~"),(t_newmethod)equals_new, 0,sizeof(t_equals), 0,
> A_GIMME, 0);sic_setup(equals_class, equals_dsp, SIC_FLOATTOSIGNAL);}*
>
>
> To:
>
>
>
>
>
>
>
> *void setup_0x3d0x3d0x7e(void){equals_class =
> class_new(gensym("==~"),(t_newmethod)equals_new, 0,sizeof(t_equals), 0,
> A_GIMME, 0);sic_setup(equals_class, equals_dsp, SIC_FLOATTOSIGNAL);}*
>
>
>
> *void setup(void){setup_0x3d0x3d0x7e();}*
>
>
> Then the compiled object can be named as ==~ and it loads fine here.
> Should I expect that it loads just fine in any other OS as well?
>
>
> cheers
>
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] objects with no alphanumerical names, how to build them?

[Alexandre Torres Porres]

Well, I also found this zexy git https://git.iem.at/pd/zexy/

not sure how it compiles to objects like ==~ - coz i couldn't compile. But
my colleague, Flavio, checked it out, and seems to have realized about the
trick to compile an object as "==~". We did it and I compiled it for Mac Os
and it is working.

By the code from the git above as a model, we changed the original code
from:







*void equals_tilde_setup(void){ equals_class =
class_new(gensym("equals~"),(t_newmethod)equals_new, 0,sizeof(t_equals), 0,
A_GIMME, 0);sic_setup(equals_class, equals_dsp, SIC_FLOATTOSIGNAL);}*


To:







*void setup_0x3d0x3d0x7e(void){equals_class =
class_new(gensym("==~"),(t_newmethod)equals_new, 0,sizeof(t_equals), 0,
A_GIMME, 0);sic_setup(equals_class, equals_dsp, SIC_FLOATTOSIGNAL);}*



*void setup(void){setup_0x3d0x3d0x7e();}*


Then the compiled object can be named as ==~ and it loads fine here. Should
I expect that it loads just fine in any other OS as well?


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

Re: [PD] objects with no alphanumerical names, how to build them?

[Alexandre Torres Porres]

well, I've checked the messages in the "hex loader" thread from nov 2007,
it seems to talk a lot about the code of what is now the [hexloader] object
in pd extended, but i didn't see how it related to my questions, which is
how does the latest zexy library, available now via deken and seemingly
from 2013, does  create objects with not alphanumerical names, and without
the need of the [hexloader] object.

If I miss something, I'm sorry, but I still need more clues and guidelines.

thanks

2016-04-04 19:11 GMT-03:00 Alexandre Torres Porres :

> will do, but can you confirm if:
>
> the version found via deken, as: *zexy-v0-0extended-(Darwin-*
> *i386-32)(Darwin-PowerPC-32)(Darwin-x86_64-32)-externals.tar*
>
> Is this the one available from last released extended (0.43).
>
> and if this is the source code then
> https://sourceforge.net/p/pure-data/svn/HEAD/tree/branches/pd-extended/0.43/externals/zexy/src/
>
> thanks
>
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] objects with no alphanumerical names, how to build them?

[Alexandre Torres Porres]

will do, but can you confirm if:

the version found via deken, as: *zexy-v0-0extended-(Darwin-*
*i386-32)(Darwin-PowerPC-32)(Darwin-x86_64-32)-externals.tar*

Is this the one available from last released extended (0.43).

and if this is the source code then
https://sourceforge.net/p/pure-data/svn/HEAD/tree/branches/pd-extended/0.43/externals/zexy/src/

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

Re: [PD] objects with no alphanumerical names, how to build them?

[IOhannes m zmölnig]

On 04/04/2016 11:42 PM, Alexandre Torres Porres wrote:
> Anyway, I needed to understand what are the issues and what do you have to
> do to make it happen, and then, well, I guess I can look into this zexy
> structure to better understand it.

please search the archives for "hex loader".
it has all the info and discussions.

fmards
IOhannes



signature.asc
Description: OpenPGP digital signature
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list