- Shorthand ~> pointers - 4 Updates
- simple proxy gc scheme... - 1 Update
- Running code in a different folder without redefinition errors. - 1 Update
| "Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Dec 23 02:52PM -0500 On 12/23/2018 2:17 PM, Mr Flibble wrote: >>> My assertion is based on what you said that I quoted... >> What did I say? And why did it indicate to you that I'm doing it wrong? > lern2..usenet It was a mistake for me to reply to you. I've never once seen you actually help someone. Once again you exhibit your sole desire to be mean, do harm, and hurt people. I am very sad for you, Leigh. I'm sorry your life is like this. It doesn't have to be. -- Rick C. Hodgin |
| "Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Dec 23 03:02PM -0500 On 12/23/2018 2:26 PM, Ian Collins wrote: > auto& box {w->settings->rc}; > box.left = something; > which will always be unambiguous. That general idea is what I do today. It requires me creating box, which is what the ~~ no longer requires. It also removes one more line of source code, yet at the expense of not having the lengthy reference somewhere nearby. If the reference is not common, you'll probably want it. But if it's under an umbrella like "settings" it may not be needed as it's an obvious part of the design. > Your scheme falls down as soon a you have a struct with more than one > compound member of the same type. You can include compound members: w~~rc1.left w~~rc2.left The shorthand portion takes up the common portion, leaving only the unique portion as the focus in code. It's not for everything. It's a tool for where it has uses. -- Rick C. Hodgin |
| Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk>: Dec 23 09:14PM On 23/12/2018 19:52, Rick C. Hodgin wrote: > It was a mistake for me to reply to you. I've never once seen you > actually help someone. Once again you exhibit your sole desire to > be mean, do harm, and hurt people. Oh why don't you just grow a pair you snowflake? > I am very sad for you, Leigh. I'm sorry your life is like this. > It doesn't have to be. Replying to Usenet posts be they fucktarded or not is like 0.1% of what I do/am. /Flibble -- "You won't burn in hell. But be nice anyway." – Ricky Gervais "I see Atheists are fighting and killing each other again, over who doesn't believe in any God the most. Oh, no..wait.. that never happens." – Ricky Gervais "Suppose it's all true, and you walk up to the pearly gates, and are confronted by God," Bryne asked on his show The Meaning of Life. "What will Stephen Fry say to him, her, or it?" "I'd say, bone cancer in children? What's that about?" Fry replied. "How dare you? How dare you create a world to which there is such misery that is not our fault. It's not right, it's utterly, utterly evil." "Why should I respect a capricious, mean-minded, stupid God who creates a world that is so full of injustice and pain. That's what I would say." |
| Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk>: Dec 23 09:36PM On 23/12/2018 19:52, Rick C. Hodgin wrote: > be mean, do harm, and hurt people. > I am very sad for you, Leigh. I'm sorry your life is like this. > It doesn't have to be. You are sad for me? Trying being sad for yourself. The last person I need a psychological evaluation from is a Christian who believes homosexuals should be put to death. (Leviticus 20:13) /Flibble -- "You won't burn in hell. But be nice anyway." – Ricky Gervais "I see Atheists are fighting and killing each other again, over who doesn't believe in any God the most. Oh, no..wait.. that never happens." – Ricky Gervais "Suppose it's all true, and you walk up to the pearly gates, and are confronted by God," Bryne asked on his show The Meaning of Life. "What will Stephen Fry say to him, her, or it?" "I'd say, bone cancer in children? What's that about?" Fry replied. "How dare you? How dare you create a world to which there is such misery that is not our fault. It's not right, it's utterly, utterly evil." "Why should I respect a capricious, mean-minded, stupid God who creates a world that is so full of injustice and pain. That's what I would say." |
| "Chris M. Thomasson" <invalid_chris_thomasson@invalid.invalid>: Dec 23 12:48PM -0800 On 12/17/2018 11:41 PM, Chris M. Thomasson wrote: > to keep things Kosher. > https://groups.google.com/forum/#!topic/lock-free/ryIAaCod7OQ > https://pastebin.com/raw/FpnvTqvM [...] A simple proxy with per-thread mutexes. Threads enter a protected region by taking their own lock, and leave it by releasing said lock. Very basic. When a thread wants to defer a node for deletion it pushes it onto a global lock-free stack via CAS. There is a reaper thread that flushes all of the nodes with XCHG, and keeps it on an internal list. The reaper thread loop then tries to acquire and release all of the per-thread locks. Once it has done this, it says quiescent state. It keeps nodes in a way that ensures at least two periods of this state have occurred before it actually calls delete and destroys memory. Since the reapers use a try_lock to detect a quiescent state, it can livelock in a reaper in the sense that it never gains a lock. However, Relacy should never detect the condition because of the limited iteration loop for workers wrt the test code itself. There is a work around. We can let a reaper fail for a little while before it actually ditches try_lock and just locks the per-thread quiescence lock. It would act just like an adaptive mutex, in a sense... _______________ fresh = new generation old = old generation // reaper loop fresh = gain new nodes if (quiescent) { dump = old; old = fresh; fresh = empty; dump.destroy(); // reclaim memory... } _______________ Fwiw, if interested, read some of the new responses in: https://groups.google.com/forum/#!topic/lock-free/ryIAaCod7OQ |
| Manfred <noname@add.invalid>: Dec 23 08:56PM +0100 On 12/23/2018 7:05 PM, Paul wrote: > of the .h file but that is considered bad practice. > I am looking for a way to test f() in a different folder which is good > practice (and therefore avoids an #include "TestLinker.cpp"). IDEs can provide tools for this, but in the end it resolves to proper usage of the compiler and linker. For example, you can instruct the compiler to look for header files in some folder (-I/some/folder) so that you don't need to specify the full path in the #include statement. Similarly, you can instruct the compiler where to put the object files, and instruct the linker where to pick them, and where to generate the executable. |
| You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to comp.lang.c+++unsubscribe@googlegroups.com. |
No comments:
Post a Comment