Front page | perl.perl5.porters |
Postings from March 2014
* Christian Walde <walde.christian@gmail.com> [2014-03-02 02:25]: > * Leon Timmermans <fawaka@gmail.com> [2014-03-02 02:05]: > > I'm not quite sure what you mean with "threads can crash easily if > > shared data isn't meticulously flagged". On a C >level, > > threads::shared shouldn't segfault [...] If it does segfault, that > > is a bug that needs to be addressed. > > Note: By crash i am talking about any improper program termination, > not just segfault, and also conflating data corruption into it for > brevity. Keep in mind that that warning is meant to inspire fear, not > to be technical reference material. ;) Then it has no place in the documentation. It’s fine to warn off users – just not by deliberately misleading them. (Because while your wording is arguably not necessarily inaccurate, you chose it purposefully for its likelihood of misinterpretation.) (I hate woo-woo FUD. Explain to users what goes on and they will know to stay away – no fear of the unknown necessary.) And after your response to Leon I am still unsure about what you are referring to in this item. Is it the usual “shared concurrently mutable state is hard, let’s go forking” issue? Or something specific to Perl threads? If it’s the former, it probably ought to just be omitted – that is neither news nor a reason to avoid Perl threads specifically. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>Thread Previous | Thread Next