[PD] x_list for pd 0.37

[Claude Heiland-Allen]

volker böhm wrote:
> hello,
> quite a retro-question, but maybe someone can help:
> currently i'm working with PDa on a gumstix computer.
> PDa is based on pd 0.37.4 and it doesn't contain the list objects.
> since i do a lot of list processing, it would be nice to have those  
> on the gumstix, too.
> so, i took the source (x_list.c) from a recent version, cross  
> compiled it for the gumstix and installed the object in /usr/lib/pd/ 
> externs.
> this is working fine.
> only drawback is, that everytime i run pd, i have to create a  
> [x_list] object before i can use any of the list objects, like [list  
> append], [list trim] etc. so i have to somehow load the object into  
> memory. not a big issue, but can be annoying.

maybe:

1. rename the x_list_setup() function in the source code to list_setup()
2. recompile
3. copy the compiled file to list.foo (where foo is the appropriate 
extension for gumstix pda)

untested as i don't have a pda :)

then what should happen is that the list.foo is loaded automatically 
when you try and create a [list ...] object, so no more problems as all 
the [list foo] objects have that weird [list] redirector.

the classical solution would be to do:

pd -lib x_list

which would load x_list.foo and run x_list_setup() when pd starts

> in newer versions of pd this is done automatically.

in newer pd it's built into the pd binary, so no hope of fiddling with 
it to upgrade it without recompiling the whole of pd

> (i guess you call this an "interal" as opposed to "external"?)

yes, internal vs external - imo as much as possible should be externally 
loaded with pd core being super minimal - but one can dream of potatoes..

> how could i apply the same auto-load mechanism in this situation?
> 
> thanks for your comments,
> volker.


Claude
-- 
http://claudiusmaximus.goto10.org