Hans-Christoph Steiner wrote: > An easy way to avoid this is to have pdlua look for a setup function in > the .lua it is trying to open.
If it's easy, submit a patch. pdlua just runs scripts, it doesn't inspect them. > If there is no setup function, then it > wouldn't load that file. You can't see what's in a file without loading it. You can't see which class(es) a Lua script registers without running it. Example: the name of the class could be stored in the file in rot13 encoding and decoded at runtime, before it is registered with Pd. > That's really the key technique for loading pd > binaries. Lua scripts are not binaries. Not all Lua scripts are related to Pd. Not all binaries with name_setup() symbols exported are related to Pd. > The differing file extensions aren't really necessary. *all* file naming is arbitrary. Henceforth I'll name my patches in unary by order of creation date, incrementing the letter once my filesystem complains of file names being too long. Claude -- http://claudiusmaximus.goto10.org a.pd aa.pd aaa.pd aaaa.pd aaaaa.pd aaaaaa.pd aaaaaaa.pd aaaaaaaa.pd aaaaaaaaa.pd aaaaaaaaaa.pd aaaaaaaaaaa.pd aaaaaaaaaaaa.pd aaaaaaaaaaaaa.pd aaaaaaaaaaaaaa.pd aaaaaaaaaaaaaaa.pd aaaaaaaaaaaaaaaa.pd aaaaaaaaaaaaaaaaa.pd aaaaaaaaaaaaaaaaaa.pd aaaaaaaaaaaaaaaaaaa.pd aaaaaaaaaaaaaaaaaaaa.pd aaaaaaaaaaaaaaaaaaaaa.pd aaaaaaaaaaaaaaaaaaaaaa.pd aaaaaaaaaaaaaaaaaaaaaaa.pd aaaaaaaaaaaaaaaaaaaaaaaa.pd aaaaaaaaaaaaaaaaaaaaaaaaa.pd aaaaaaaaaaaaaaaaaaaaaaaaaa.pd aaaaaaaaaaaaaaaaaaaaaaaaaaa.pd aaaaaaaaaaaaaaaaaaaaaaaaaaaa.pd _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
