Hello, just to add my brain fart too, pointers are the most efficient data storing/retrieving I've ever met in PureData, but it also the most complicated to manage in a patch without crashing the whole thing... Pointers have get set methods and can store all PureData types, and it's very fast, if not the the fastes method. Meanwhile, it's dedied to graphical stuff and not very convenient for users that are not very very experimented, and maybe also for the experimented ones, otherwise there would be already many proposals for managing pointers.
best regards > Le 12 févr. 2026 à 12:46, Sam Ross <[email protected]> a écrit : > > Hi, this may just be a brain fart as I'm no dev and am not acquainted with > json/the nested structures you are talking about, but it strikes me that > [list store] could be used to make a more flexible [value] type object, by > using the fact you can send it the [send $0/foo( message to request the > list... with an abstraction based on this you could have at least have > arbitrary list-based variables that you could dynamically get & set. Just > mentioning it in case it sparks anything off for anyone, please disregard if > not! > > Cheers, Sam. > --- > [email protected] - the Pure Data mailinglist > https://lists.iem.at/hyperkitty/list/[email protected]/message/BJPXLYM6ON4VM3PRXYQLTJ3V64HTQ7JT/ > > To unsubscribe send an email to [email protected] mailing list > UNSUBSCRIBE and account-management -> https://lists.iem.at/ --- [email protected] - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/[email protected]/message/FW2D7LIMZROUNTUX36U2MW7RZ6YMU6PT/ To unsubscribe send an email to [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
