On Fri, 14 Mar 2008, Albert Graef wrote:
In Pd/Q this is done differently; there's only one main script which
defines all the Q objects in a patch (which are in fact just Q
functions), but this script can be reloaded dynamically through a
special "q" receiver. This operation is a bit on the he
On Mar 13, 2008, at 3:07 PM, [EMAIL PROTECTED] wrote:
> Hans-Christoph Steiner ha scritto:
>> Hey,
>>
>> Now that we have a number of loaders, I'd like to figure out a
>> standard way of naming the libraries so that they are easy to
>> organize and load. Currently, there are these arrangments:
>
Frank Barknecht wrote:
> This point however is a bit tricky with loaders, see the difference
> between the loader functionality in pdlua and the "luax" objectclass.
Yeah, that's because for the Lua external each object class is
associated with its own Lua source. In Pd/Q this is done differently;
Hallo,
Albert Graef hat gesagt: // Albert Graef wrote:
> Claude Heiland-Allen wrote:
> > Yes, a simple one: there is a function typedef (for the loader hook
> > functionality) and a function to add a hook to the list. I forget the
> > exact names, they're in m_pd.h if you have a new enough Pd.
>
Claude Heiland-Allen wrote:
> Yes, a simple one: there is a function typedef (for the loader hook
> functionality) and a function to add a hook to the list. I forget the
> exact names, they're in m_pd.h if you have a new enough Pd.
You mean this? (From your Lua external.)
/* defined in pd/src/s_
Albert Graef wrote:
> Frank Barknecht wrote:
>> May I throw in another one: As loaders are a bit different than
>> externals,
>
> Uhm, did I miss anything? In which way is a "loader" different from an
> external?
A loader-external adds a hook into Pd's loader (the bit that searches
for files to
Frank Barknecht wrote:
> May I throw in another one: As loaders are a bit different than
> externals,
Uhm, did I miss anything? In which way is a "loader" different from an
external? In that it loads another interpreter? Is there a special new
API for this kind of things? I just want to know as I'
what exactly *is* the lua loader? is it a wrapper? or a library? I was
confused in the beginning bcause I thought the "thing" was named pdlua,
but the "thing" was loaded with lib- lua (so I thought it *is* a
library, but named like lua, the language itself? hmm..)
marius.
Frank Barknecht wrote:
Hallo,
Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
> Any perferred name? I don't think I have a strong preference of any
> name, but I do think there should be a simple, standard naming scheme.
May I throw in another one: As loaders are a bit different than
externals, m
Hans-Christoph Steiner ha scritto:
> Hey,
>
> Now that we have a number of loaders, I'd like to figure out a
> standard way of naming the libraries so that they are easy to
> organize and load. Currently, there are these arrangments:
>
> pdXXX
> -
> pdlua.pd_linux
> pdtcl.pd_linux
> pdhask
So I agree this is good:
-lib lua
[import lua]
Then it seems that it would be nice if the projects were either:
pdlua
pdtcl
pdhaskell
or:
luapd
tclpd
haskellpd
How about the first one?
.hc
On Mar 13, 2008, at 2:39 PM, Claude Heiland-Allen wrote:
> Hans-Christoph Steiner wrote:
>> XXX
>>
Hans-Christoph Steiner wrote:
> XXX
> ---
> lua.pd_linux
^^ this is what I use. The project as a whole is called 'pdlua' but the
external for Pd is called 'lua', like '-lib lua' and [lua].
> tcl.pd_linux
> haskell.pd_linux
^^ this is probably what I will use if I ever resume work on my Haskell
Hey,
Now that we have a number of loaders, I'd like to figure out a
standard way of naming the libraries so that they are easy to
organize and load. Currently, there are these arrangments:
pdXXX
-
pdlua.pd_linux
pdtcl.pd_linux
pdhaskell.pd_linux
[import pdtcl]
XXXpd
-
luapd.pd_lin
13 matches
Mail list logo
