- OT: A message regarding the rapid transformation of our world - 7 Updates
- macro-problems - 4 Updates
- More precision about my new inventions of scalable algorithms.. - 10 Updates
| "Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Feb 24 07:10PM -0500 OT: A message regarding the rapid transformation of our world Read this and repost. It's important. This message is to U.S. citizens, but it applies world-wide. Our nation is under serious assault. Not by the left or right, but by evil spiritual forces at work inside of people. By our society, people have sold out to sin in all its various forms, and now those evil spirits literally dwell inside the physical bodies of people, and from that place of influence they are moving against all of mankind in the capacity of the people they occupy. Leaders. Business people. Everyone of influence is under assault or being replaced in their position by someone who is compromised. This translates into a world environment where all of us who trust in the Lord Jesus Christ, who seek to do and be a part of what's true, what's right in God's sight, deferring to the guidance which God has given us in the Bible, by His Holy Spirit, through His Son, are also under assault. No one is sidelined. We are all all in whether we realize it or not. The United States in its present form will not survive. We read in Revelation about the coming great tribulation and how the entire world will go after the mark of the beast system, taking the mark and in so doing damning their eternal souls. My friends, that time is here. We are seeing the transformation and preparation for the full-on implementation of that system happening before our very eyes. We are seeing that mark of the beast system coming online and rising up before us. It will not be too much longer until everyone who trusts in Jesus Christ will be cast out of their jobs, their homes, onto the streets, unable to get employment, unable to provide for their families. They will be shunned and hated everywhere by those very people who, through sin and their love of sin, are compromised. Christians will become a band of outcasts and the whole world will rejoice for a time because of it. But to every Christian: Take heart, because the Lord of hosts has secured our victory. He will take us out of this world so we will not go through that mark of the beast system and the seven year tribulation. Stay strong, my friends. Take courage. The Lord Jesus Christ has already given us the victory. This is the enemy's moment in time to rise to power and overcome, but scripture teaches us it is a fleeting moment, and it will not endure, and Jesus has already secured their defeat in the most final way possible. Be strong no matter what comes. And if you need encouragement, please contact me. Watch my video on the spiritual nature of our lives on YouTube. And teach the people around you about this spiritual battle we are facing, and why and how we must keep our faith and trust in Jesus Christ no matter what the enemy throws at us. I am there with you in spirit, as are all the saints, across all the nations, across this entire world, are likewise. Look up, because your redemption draws near. In Christ, Rick C. Hodgin PS -- To all of you who don't believe, consider these things. Read the Bible and see for yourself if what I teach you about the correlation between worldly events and changes aligns with the Biblical teaching. Do not go another day without knowing for sure. Put God to the test. Prove Him out by examining and testing what He's written to see if He is true or not. Do not rely upon me or my guidance / thoughts. I am a man and can be wrong. But God is not a man like us, and He cannot be wrong. Jesus wants to forgive you today. Ask Him to forgive you and escape what's coming. Do this, and you will feel the change, and you will see the whole world from inside of new eyes. Peace, my friends. [Jesus Loves You] |
| Mr Flibble <flibble@i42.REMOVETHISBIT.co.uk>: Feb 25 12:52AM On 25/02/2021 00:10, Rick C. Hodgin wrote: > OT: A message regarding the rapid transformation of our world [snip - tl;dr] And Satan invented fossils, yes? /Flibble -- 😎 |
| Andy Burns <usenet@andyburns.uk>: Feb 25 08:06AM Rick C. Hodgin wrote: > someone who is compromised. > This translates into a world environment where all of us who trust in > the Lord Jesus Christ, who seek to do and be a part of what's true, libSF.c:15:12: error: 'Jesus' undeclared (first use in this function) |
| "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Feb 25 12:14AM -0800 On 2/25/2021 12:06 AM, Andy Burns wrote: >> This translates into a world environment where all of us who trust in >> the Lord Jesus Christ, who seek to do and be a part of what's true, > libSF.c:15:12: error: 'Jesus' undeclared (first use in this function) Did he finally finish his compiler? I want to install the platform, and give it go. Have some old computers around. |
| "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Feb 25 12:17AM -0800 On 2/25/2021 12:06 AM, Andy Burns wrote: >> This translates into a world environment where all of us who trust in >> the Lord Jesus Christ, who seek to do and be a part of what's true, > libSF.c:15:12: error: 'Jesus' undeclared (first use in this function) I know that you are being sarcastic... However, when he finally does finish, and I can install an iso image. I would jump up in the air: https://youtu.be/UZ2-FfXZlAU |
| "Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Feb 25 12:09PM -0500 On Thu, 25 Feb 2021 08:06:47 +0000 > > in the Lord Jesus Christ, who seek to do and be a part of what's > > true, > libSF.c:15:12: error: 'Jesus' undeclared (first use in this function) Very clever and funny! :-) You're using an outdated "compiler." Upgrade to version 2.0, which has both the physical and spiritual components. It has all the #includes and knows how to process the new spiritual abilities. -- Rick C. Hodgin |
| Mr Flibble <flibble@i42.REMOVETHISBIT.co.uk>: Feb 25 05:48PM On 25/02/2021 17:09, Rick C. Hodgin wrote: > You're using an outdated "compiler." Upgrade to version 2.0, which has > both the physical and spiritual components. It has all the #includes > and knows how to process the new spiritual abilities. And Satan invented fossils, yes? evolution.c:15:12: error: 'God' undeclared (first use in this function) /Flibble -- 😎 |
| Bonita Montero <Bonita.Montero@gmail.com>: Feb 25 07:24AM +0100 I've got a header with a macro to define new exception-subclasses: #pragma once #include <exception> #include <string> #define exc_subclass(base, deriv, default_what) \ struct deriv : public base \ { \ deriv( char const *what = default_what ) noexcept : \ m_what( what ) \ { \ } \ deriv( exception_ptr nextException, char const *what = default_what ) noexcept : \ m_nextException( nextException ), \ m_what( what ) \ { \ } \ deriv( deriv const &other ) noexcept : \ base( other ), \ m_what( other.what() ) \ { \ } \ virtual char const *what() const noexcept override \ { \ return m_what.c_str(); \ } \ std::exception_ptr next_exception() const noexcept \ { \ return m_nextException; \ } \ private: \ std::string m_what; \ std::exception_ptr m_nextException; \ }; But this doesn't accept ... exc_subclass(std::exception, deriv, "my default what") ... because of the :: in it. Is there any escape for :: ? |
| Ben Bacarisse <ben.usenet@bsb.me.uk>: Feb 25 11:11AM > But this doesn't accept ... > exc_subclass(std::exception, deriv, "my default what") > ... because of the :: in it. The macro does not care about the ::. If it does not work, it's for some other reason. -- Ben. |
| Paavo Helde <myfirstname@osa.pri.ee>: Feb 25 01:43PM +0200 25.02.2021 08:24 Bonita Montero kirjutas: > { \ > } \ > deriv( exception_ptr nextException, char const *what = default_what You are missing std:: before exception_ptr in the prev line. Colons in preprocessor macros are fine. Commas, on the other hand, might be a bit tricky sometimes. |
| Bonita Montero <Bonita.Montero@gmail.com>: Feb 25 02:54PM +0100 > You are missing std:: before exception_ptr in the prev line. Ok, that's what someone else found on Stack Overflow also. But thanks. |
| "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Feb 24 05:16PM -0800 On 2/24/2021 10:28 AM, Richard Damon wrote: > to do some 'cleanup' on the resource, but if the process isn't releasing > the resource in the required time, can you really trust that it is doing > its job right? Are you familiar with robust mutexes? They are designed to allow one to repair the shared data if a processes dies while holding the lock. |
| Bonita Montero <Bonita.Montero@gmail.com>: Feb 25 07:08AM +0100 > A lock that works with the OS to so the OS knows what locks the process > holds can kill a 'bad' process and force the release of the lock. That's impossible because that what the lock guards is in inconsistent state at this time. |
| "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Feb 24 11:39PM -0800 On 2/24/2021 10:08 PM, Bonita Montero wrote: >> holds can kill a 'bad' process and force the release of the lock. > That's impossible because that what the lock guards is in inconsistent > state at this time. Think of a "master" process, than can kill a process while its holding a process-wide mutex. This can be handled and corrected, the state can be repaired into a consistent state. Its tricky, yet can be done. Wrt Windows think of the WAIT_ABANDONDED state. POSIX has it with EOWNERDEAD. |
| "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Feb 24 11:43PM -0800 On 2/24/2021 10:08 PM, Bonita Montero wrote: >> holds can kill a 'bad' process and force the release of the lock. > That's impossible because that what the lock guards is in inconsistent > state at this time. Wrt WAIT_ABANDONED, read the docs: https://docs.microsoft.com/en-us/windows/win32/api/synchapi/nf-synchapi-waitforsingleobject _____________ WAIT_ABANDONED: The specified object is a mutex object that was not released by the thread that owned the mutex object before the owning thread terminated. Ownership of the mutex object is granted to the calling thread and the mutex state is set to nonsignaled. If the mutex was protecting persistent state information, you should check it for consistency. _____________ POSIX has, EOWNERDEAD: https://man7.org/linux/man-pages/man3/pthread_mutex_consistent.3.html |
| Bonita Montero <Bonita.Montero@gmail.com>: Feb 25 09:49AM +0100 > process-wide mutex. This can be handled and corrected, the state can be > repaired into a consistent state. Its tricky, yet can be done. Wrt > Windows think of the WAIT_ABANDONDED state. POSIX has it with EOWNERDEAD. If you have shared memory modified while holding the lock there's nothing to fix. |
| "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Feb 25 01:05AM -0800 On 2/25/2021 12:49 AM, Bonita Montero wrote: >> Windows think of the WAIT_ABANDONDED state. POSIX has it with EOWNERDEAD. > If you have shared memory modified while holding the lock there's > nothing to fix. have you ever had to encounter and deal with EOWNERDEAD, or WAIT_ABANDONDED ? |
| "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Feb 25 01:49AM -0800 On 2/24/2021 9:20 AM, Bonita Montero wrote: >> It does depend on the implementation if frequent reads can starve out >> writers. > But if this happens is a matter of the lock-behaviour. The way the user actually uses a rwmutex should be read heavy, writes, not so frequent. However, frequent sustained reads should not have the ability to starve out writers; lots of rwmutex impls allow just that. Some even have so-called reader/writer priorities. Bakery algorithms cannot suffer from these conditions... They just go in order. |
| Bonita Montero <Bonita.Montero@gmail.com>: Feb 25 11:43AM +0100 >> nothing to fix. > have you ever had to encounter and deal with EOWNERDEAD, or > WAIT_ABANDONDED ? Boy, you're stupid. If you're modifying memory while holding a lock and the lock is deleted meanwhile, WAIT_ABANDONNED or whatever doesn't help. |
| "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Feb 25 03:09AM -0800 On 2/25/2021 2:43 AM, Bonita Montero wrote: > Boy, you're stupid. If you're modifying memory while holding a lock > and the lock is deleted meanwhile, WAIT_ABANDONNED or whatever doesn't > help. You have never had to clean up after a process dies while holding a mutex? |
| "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Feb 25 03:10AM -0800 On 2/25/2021 3:09 AM, Chris M. Thomasson wrote: >> Boy, you're stupid. If you're modifying memory while holding a lock >> and the lock is deleted meanwhile, WAIT_ABANDONNED or whatever doesn't >> help. I am not referring to deleting a mutex, I am talking about a process crashing in the middle of a critical section. |
| 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