On Jul 17, 2008, at 5:03 AM, IOhannes m zmoelnig wrote:
hard off wrote:
ok, sorry to have caused a fuss.
last question: hypothetically, if miller was to include >~ and <~
into vanilla, would they load properly then?yes of course.
again: the only problem with these objects is that you cannot have
files (e.g. binary files containing the code for these objects; or abstractions) that are include characters like ">" on certain
platforms.the only solution for this is to use filenames that are named differently than the actual class.
this solution can be implenmented in various ways:
- include it into Pd-vanilla (so these objects would reside in the
file "pd.lib" or "pd")
- use multi-object libraries (so these objects reside in
"zexy.l_i386")
- use aliases (so ">~" really lives in "gt~.pd")
- use a hexloader (kind of generated filenames that map to the
original classname), so ">~" resides in "0x3e0x7e.pd"
so it's rather simple, BUT:
- Pd-vanilla does not include all the fancy'n'cool objects into Pd
(esp. if they can be easily built as externals)
- multi-object libraries are deprecated in PdX
- aliases are problematic, as you have to tell Pd about these aliases
somehow (the mapping from ">~" to "gt~" is rather arbitrary)
- the hexloader has only been partially accepted into Pd-vanilla (that
is: the filename mangling part has been taken out); and the implementation of it as an external loader has only created
problems for everyone.
So the loaded classes need to be fixed to that they are canvas-local,
not global like it is currently. If that was the case, then I could
see using multi-class-single-file libraries for cases like this,
provided that they could be used like [>~] and [math/>~]. The tricky
part would be getting the "math.pd_linux" file to load automatically
when someone creates [math/>~].
.hc
mfgasdr IOhannes
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
News is what people want to keep hidden and everything else is
publicity. - Bill Moyers