[PD-dev] [PD] more about float limitation
IOhannes m zmoelnig
zmoelnig at iem.at
Wed Feb 4 12:03:11 CET 2015
-----BEGIN PGP SIGNED MESSAGE-----
On 2015-02-04 10:57, katja wrote:
> What would a legacy Pd build do with fat-precision binaries? Could
> we consider single precision the default and not rename the setup
> function compiled for single precision so it will still work with
> legacy Pd? If the extensions are not modified, a user can't see
> whether an external is fat-precision or not.
just a word with my debian maintainer hat on:
if Pd-vanilla supported double-precision builds, i would like to make
these available for Debian and derivatives as well.
if i made single- and double-precision builds co-installable (which
iÄm not sure yet), it would be as "pd" and "pd64", with pd64 using
different default configuration (~/.pd64settings) and search paths
and install all (packaged) externals that can be build for double
precision into /usr/lib/pd64/extra/, rather than having phat builds.
i don't think we should spend too much time/energy on designing and
supporting foolproof phat builds at all (as this is probably
impossible without the help from the OS).
and the extensions in Pd are already a big mess; any other environment
i know that supports loading of binary plugins, uses the OS's default
extensions: .so, .dylib, .dll; using non-standard extensions is often
*very* inconvenient...so please do not add another one.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
-----END PGP SIGNATURE-----
More information about the Pd-dev