Oh dear. Think context!
To be more explicit. Think of the context in which I said what I said. Think of the purpose of that.
Just as newbies don't need to be appraised up front with the details of the inner working of the regex engine, they don't need to be appraised of the inner workings of threads. The point was simply that without having been shared, each thread will get an independent, unshared copy of the array.
Your interjection is:
- unhelpful;
to the OP;
- unwarranted;
My understanding of the internals of the iThreads is:
- perfectly sound thanks;
- irrelevant in the context of the assistance I was trying to give the OP.
You don't need to be Jeff Friedl to help people with their regex problems. And if you were him, it wouldn't be useful to go into the all the DFA/NFA blah blah details of the internals when responding.
And it seems to me that if you aren't aware of the semantic differences between the copying of non-shared arrays; and the sharing of shared arrays, you're the one lacking understanding. But, I know you almost certainly are aware of those differences, which just confirms that your interjection is ...
- therefore, politically motivated.
Not intended to help the OP, but simply to come out in support of an untenable position.
Your time might be better spent where it would be most valuable. Eg. correcting some of the unnecessary extravagances of the current implementation.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] |
In our last disagreement you would not even so much as recognize my arguments about context, just completely ignoring anything I said. And there you were taking one phrase out of its qualifying context. Here I am making an objection to a complete thought that was part of your reply to the OP; yes, not one pertinent to your main point.
Why am I doing so? Because you seem to have elected yourself defender of ithreads to the point where you attack even true and reasonable cautionary points about them with a variety of shenanigans designed more to conceal than expose truth. The truth is that ithreads are a very different beast than people coming from other languages may expect. They are slow to start and tend to cause memory bloat. Anywhere there is support for copy-on-write fork, fork and some variety of IPC is almost always a better choice.
If that's politics, so be it. Don't bother responding, I'm not going to read it.
| [reply] |
| [reply] |