[GEM-dev] using logpost(3) for version message

[IOhannes m zmoelnig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2011-09-27 21:37, Hans-Christoph Steiner wrote:
>
>> and possibly 0.41
>> this is not a big problem for PdX, where you ensure that the pd binary
>> is accompanied by "matching" externals, but it is a problem if you
>> distribute binary builds of the external.
> 
> This can easily support any Pd version with an #ifdef, I'll add that.

i'm talking about runtim compatibility, not compile time compatibility.
an #ifdef patch will most likely not going to make it before Pd-0.45

(there might be some old code in Gem that indeed uses #ifdef for these
kind of things but i want to make it fade out (unless the Pd-version
tested for has been there for a number of years)


>> - - logpost() is mainly there to post verbose information that is
>> attached
>> to an object. the Gem version is not attached to any object.
> 
> I wrote logpost() to do both.  Just set the object to NULL and it just
> posts.

i thought i did :-), but indeed this is your work.

nevertheless, verbose() offers the same functionality as logpost(NULL,)
and works with older version of pd.


sdfmt
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6CyPIACgkQkX2Xpv6ydvT1lACgnNFooWufaGY7BYDzzH+x4i5D
+F0AoJmYuqU2tP9+3admNl6iZV+fb7FK
=+iiC
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3636 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20110928/dcc23946/attachment-0001.bin>