- [Jesus Loves You] A new age is dawning - 2 Updates
- How to get the next line character(s) - 5 Updates
- PolyCollection - 1 Update
| "Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Feb 18 12:31PM -0800 [Jesus Loves You] A new age is dawning There is a change in progress. The enemy spirit is ramping up his sheer hatred of Jesus Christ. Devout Christians are being attacked in increasing quarters. It is the end times. That evil spirit is operating in men and women more and more. It is growing in anger and hostility toward Christians, forcing them out of jobs, social gatherings, online publications. Only the religion of "tolerance for everything (except Christians)" is being allowed. Make no mistake about it. It's not just us. You are targeted. Your soul. Your eternal fate. You are not on the sidelines. You are a player. You are all in. You are fully invested in the outcome, whether you acknowledge it or not. The enemy is gunning for you. You only have one way out of his deceptive death clutches. It's about exactly two things: 1) Your sin, and 2) Jesus Christ. You have sin. The soul (eternal soul) who sins dies (eternal death in Hell). Jesus came to take our sin away. He will forgive your sin and give you eternal life for the asking. Do you want to be judged for your sin? Or forgiven? Jesus forgives all who come to Him asking for forgiveness. Your eternal fate is in your hands. Ask Jesus to forgive your sin and gain eternal life today. -- Rick C. Hodgin |
| "Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Feb 18 12:38PM -0800 Here's some simple commentary on why our society is changing: "And the Devil smiled" https://www.youtube.com/watch?v=WXkiGOZ64JM Unless you know Jesus Christ as Savior and Lord, the devil owns you. There are no fence sitters. No bystanders. You're either serving the Lord actively, or you are serving Satan. Literally. Whose are you? -- Rick C. Hodgin |
| Louis Krupp <lkrupp@nospam.pssw.com.invalid>: Feb 17 09:30PM -0700 >I will try if using the descriptors in separate processes the mechanism >will work correctly. Unfortunately, even if it will work it will result >an excessive work only to know how the system encodes the end of line. Here's yet another program that might help. My apologies if it matches something that's already been suggested: #include <iomanip> #include <iostream> #include <sstream> #include <string> int main() { std::ostringstream oss; oss << std::endl; const char *p = oss.str().data(); std::cout << std::setfill('0') << std::setw(2) << std::hex; while (char c = *p++) std::cout << int(c); std::cout << "\n"; return 0; } Louis |
| Paavo Helde <myfirstname@osa.pri.ee>: Feb 18 10:14AM +0200 On 18.02.2018 6:30, Louis Krupp wrote: > std::ostringstream oss; > oss << std::endl; > const char *p = oss.str().data(); This creates a dangling pointer. > std::cout << "\n"; > return 0; > } Yes, this has been proposed and it would not work even if the dangling pointer bug is fixed. The linefeed translation only appears with an "external representation" and there is nothing external in a stringstream. Cheers Paavo |
| Louis Krupp <lkrupp@nospam.pssw.com.invalid>: Feb 18 03:43AM -0700 On Sun, 18 Feb 2018 10:14:50 +0200, Paavo Helde >> oss << std::endl; >> const char *p = oss.str().data(); >This creates a dangling pointer. OK. It's off-topic, but how would you fix it? >"external representation" and there is nothing external in a stringstream. >Cheers >Paavo OK. So even if it were correct, it would be useless. Louis |
| "Öö Tiib" <ootiib@hot.ee>: Feb 18 04:04AM -0800 On Sunday, 18 February 2018 12:43:43 UTC+2, Louis Krupp wrote: > >> const char *p = oss.str().data(); > >This creates a dangling pointer. > OK. It's off-topic, but how would you fix it? By writing it simply: std::string s = oss.str(); // ... for (char c : s) { std::cout << int(c); } Avoid raw pointers then those can not dangle. |
| Christian Gollwitzer <auriocus@gmx.de>: Feb 18 01:49PM +0100 Am 18.02.18 um 13:04 schrieb Öö Tiib: > // ... > for (char c : s) { std::cout << int(c); } > Avoid raw pointers then those can not dangle. It also demonstrates nicely how modern C++ is a much cleaner language. It could even be for (char c : oss.str()) { ... } -> "give me every char from the stream" without worrying about NULL-terminators and such. Christian |
| woodbrian77@gmail.com: Feb 17 05:48PM -0800 I'm thinking about adding serialization support for this PolyCollection library: http://www.boost.org/doc/libs/1_66_0/doc/html/poly_collection.html to the C++ Middleware Writer: https://github.com/Ebenezer-group/onwards . One thing I'd like to know is how many of the applications that you have worked on, which used runtime polymorphism, could have benefited from PolyCollection? Keeping in mind that PolyCollection imposes it's own ordering of objects added to it. And is it too early/late to suggest that this library be added to the standard? Thanks in advance. Brian Ebenezer Enterprises - Enjoying programming again. http://webEbenezer.net |
| 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