Whatever the anser to your update questions,
I hope that the new create() signature is
in addition to
support for set/get_stack_size() ?
I don't have any complaint wrt the named param signature (in fact I'd
suggest possibly providing support for priority params if possible -
tho implementation of that capability is very hit-and-miss, and usually
platform specific), but set_stack_size() permits existing apps to
just add a single call up front, wo/ otherwise touching existing code,
to benefit from smaller stack size.
As for your child/grandchild conundrum, I'd say inheritance is probably
the best rule to fall back on, since its
likely the desired behavior for any other attributes (e.g., priority).
I suppose you'd need to differentiate between a parent thread that
had explicitly set/inherited an attribute vs. using the global value,
in the event the global value is modified at some point between
parent and child creation.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.