X-Git-Url: http://git.vpit.fr/?a=blobdiff_plain;f=Changes;h=c37d46a752e90d3054d02fa93032cbf164c6f768;hb=ace906d7e76ed647adbd1ab1243ac9bdbde9b1d5;hp=bd75adf2be5f4f0788ffd06b1063d526b063834c;hpb=f40399f9f0863eb53831591d8336b16752ffd816;p=perl%2Fmodules%2FVariable-Magic.git diff --git a/Changes b/Changes index bd75adf..c37d46a 100644 --- a/Changes +++ b/Changes @@ -1,5 +1,39 @@ Revision history for Variable-Magic +0.40 2010-01-06 23:20 UTC + + Fix : Possible memory miswrites when passing data arguments to cast(). + + Fix : Minor C portability tweaks. + +0.39 2009-12-01 00:05 UTC + + Add : You can use a function name as a callback by passing a string + reference to wizard() instead of a code reference. + + Fix : Compatiblity with perl 5.11.1 and 5.11.2. + + Fix : Scalars stored into the data slot no longer leak. + + Fix : Thread destruction should not segfault anymore. + + Opt : As a result of removing the deprecated features, less memory is + used for both threaded (a pointer table is used instead of a + hash) and non-threaded (no global structure is needed anymore) + perls. + + Rem : As advertised in the precendent version, all the signature + related features were removed. This includes the 'sig' option + to wizard(), the getsig() and gensig() functions, and the SIG_* + constants. + +0.38 2009-10-04 16:10 UTC + + Dep : All the signature-related features are DEPRECATED and will be + removed in december 2009. This includes the 'sig' option to + wizard(), the getsig() and gensig() functions, and the SIG_* + constants. + Afaik those features were never used in real life, and they make + the XS code slow and brittle. If you want your wizards to be + globally available, you'll have to handle that yourself by + storing them in a hash. + + Doc : More examples in a new COOKBOOK section. + + Fix : Compatiblity with the 5.11.0 release. The new compatibility + constant VMG_COMPAT_ARRAY_PUSH_NOLEN_VOID was added to cover + this. + + Fix : Work around Kwalitee test misfailures. + 0.37 2009-08-25 15:25 UTC + Add : The new constant VMG_FORKSAFE can be tested to know whether the module will behave nicely when fork()ing. It's currently always