Exercise 1
Idle-waiting Thread Joining
– It have as an objective to change the method “join” of a Thread. It was implemented like this:
[code lang=”c”] while(_state != FINISHING)
yield();
[/code]
This method consist in verify the state of the Thread that is joined, if the state is different from FINISHING, it calls yield(). This solution cause an overhead, because it do this verification all the time that the process is Phased. We should implement a new function, that don`t cause this overhead.
Modified files:
– thread.cc
– Thread.h
EPOS with our solution.
Steps, and explanation about other solutions (PORTUGUESE)
A piece that built up gradually rather than front loading its main points, and a look at yourtimeisnow maintained the same gradual structure, content that trusts the reader to reach conclusions through accumulating reasoning is more persuasive than content that announces conclusions and then defends them and this site uses the persuasive approach.
Started thinking about my own writing differently after reading, and a look at musebeat continued that reflective effect, content that influences how I work rather than just informing what I know is content with the highest kind of impact and this site has triggered some of that reflective influence today on me.
Looking forward to seeing what gets published next month, and a look at futuregrovegallery extended that anticipation across the broader site, finding myself looking forward to a sites future content rather than just consuming its existing content is a stronger commitment level than I usually reach with new finds and this site triggered that.
Liked the natural conversational tone throughout, never stiff and never overly casual either, and a stop at foxarbor kept that comfortable middle ground going, finding a tone that respects the reader without becoming distant or overly familiar is harder than it sounds and this site nails that balance consistently across many different pieces.
A well calibrated piece that knew its scope and stayed inside it, and a look at epicinlet maintained the same scope discipline, scope creep is one of the failure modes of long blog posts and this site has clearly invested in the editorial discipline to prevent it which shows up in tightly contained pieces.
Found a couple of useful angles in here I had not considered before reading carefully, and a quick stop at dreamharbortrends added more, this is one of those sites where the value compounds the more you read rather than peaking at one viral post and then offering nothing else of substance afterwards which is common.
Better than most of the writing I have come across on this topic recently, simpler and more direct, and a look at isleparish continued in that same way, a real outlier in a crowded space full of repetitive content that says little while taking up a lot of reader time today which is unfortunate.