nikos tag:blogs.perl.org,2009-11-03:/users/nikos//674 2012-01-02T10:32:05Z A blog about the Perl programming language Movable Type Pro 4.38 Learning Perl, 6th Edition book review most popular of 2011 tag:blogs.perl.org,2012:/users/nikos//674.2631 2012-01-02T10:16:51Z 2012-01-02T10:32:05Z The "Learning Perl, 6th edition" book review had the distinction of being iProgrammer's most popular review of 2011, between more than 250 reviews on a vast variety of subjects with thousands of reads each, but the Perl review reached top... nikosv The "Learning Perl, 6th edition" book review had the distinction of being iProgrammer's most popular review of 2011, between more than 250 reviews on a vast variety of subjects with thousands of reads each, but the Perl review reached top spot with 10,800 reads (figure untill 29/12/2011)
The benefit is that it exposed the language to a wide audience, since the site appeals to a general programming public from C# to Javascript, therefore I do hope that it managed to attract "new blood" and/or converts !

]]> Perl's threading model,not that bad afterall tag:blogs.perl.org,2011:/users/nikos//674.2472 2011-11-21T04:38:59Z 2011-11-21T04:58:36Z I've been checking the latest developments in the new C++ standard, C++11, and noticed that it now has support for thread local storage. It adopts a "hybrid" approach; sharing by default but also using TLS slots for storing globals with... nikosv I've been checking the latest developments in the new C++ standard, C++11, and noticed that it now has support for thread local storage.

It adopts a "hybrid" approach; sharing by default but also using TLS slots for storing globals with thread scope
This reminded me that the last .NET version has an option like that
"New in .NET 4.5: ThreadLocal.Values"
as well as the "It's Not Always Nice To Share" article which concludes that it is better to share nothing by default but share explicitly

Now, I know that Perl's threading model takes TLS one step further down and that it has been heavily criticized as being "not true threading"
but all this makes me think that it is not that bad after all, but rather simplifies things and mirrors Perl's philosophy of "just getting things done"

So what's after that ? The next .NET version or C++ standard fully embracing Perl's threading model in a "back to the future" fashion ? (active since version 5.8)
Would love to see that !

]]>