On 2010-02-25 17:37, SourceForge.net wrote: > just like signals are. As you know, [print] shows them as a not very > helpful "(gpointer)", but if you pass a pointer to [list prepend set]-[list > trim] and into a message box: There pointers show up as "(pointer)" with > the "g" missing. Anyway don't bother trying [route (pointer)], it doesn't > work either. :)
for what it is worth, i have just created a little object [rawprint] in zexy, that should allow you to inspect messages a bit closer. it's basically a clone of [print] without all the fancy handling of special atoms. for [foo 1 bar( it will print: "foo" 1.00000 'bar' the output of [pointer] could print: "pointer" pointer[0xBFD62658] the selector is indicated with double-quotes and ordinary symbols with single-quotes. it's dedicated to all those who always wanted to see what's in a message. i don't see any usefulness in itself (apart from demystifying messages) mfgasdr IOhannes
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Pd-dev mailing list [email protected] http://lists.puredata.info/listinfo/pd-dev
