- [Jesus Loves You] Tag for filtering - 6 Updates
- EXAMPLE - 2 Updates
- Variable declaration syntax - 16 Updates
- Virtual functions - 1 Update
| gazelle@shell.xmission.com (Kenny McCormack): Apr 09 06:45PM In article <5551c6fd-546c-434f-b4c0-0b2fb63f3e64@googlegroups.com>, >There is a powerful anti-Christ spirit at work in Apple, along the >same lines as the one at work in Starbucks. They harm people greatly, >and people embrace them with open arms unaware of the influence. Admit it. You just have a woody for Tim Cook. Latent. It's all the same with you fundies. Somewhat more seriously, that *is* the reason why a lot of funides are (or claim to be) anti-Apple. Because the CEO is gay. Seriously, I'm not making this up. -- The plural of "anecdote" is _not_ "data". |
| gazelle@shell.xmission.com (Kenny McCormack): Apr 09 06:46PM In article <eumdncA5b4tkGFfHnZ2dnUU78amdnZ2d@giganews.com>, >> Why totally shun Apple? >Rick probably shuns Apple because the CEO is gay, like me. >/Flibble Yup. -- Q: How much do dead batteries cost? A: Nothing. They are free of charge. |
| Dombo <dombo@disposable.invalid>: Apr 09 08:59PM +0200 Op 08-Apr-18 om 23:13 schreef Mr Flibble: >> Why totally shun Apple? > Rick probably shuns Apple because the CEO is gay, like me. > /Flibble Maybe you just like sausages. |
| "Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Apr 09 11:57AM -0700 On Monday, April 9, 2018 at 2:45:53 PM UTC-4, Kenny McCormack wrote: > >and people embrace them with open arms unaware of the influence. > Admit it. You just have a .. for Tim Cook. > Latent. It's all the same with you fundies. No. Our sinful flesh pulls at us in different ways. Some are drawn to homosexuality, others to adultery and fornication, others to drugs or alcohol or some other addiction. Each of us bears the weight of sin's effect in our flesh. What I seek to do that's different because I am a Christian is to pray for those people, and to bear a witness against that behavior while pointing people to Christ. Jesus gives us new spirit life, which enables us to overcome our flesh and seek and do rightly in this world. It requires a very concentrated effort to maintain focus on the spirit because the enemy here is no slouch. He knows where we're weak and he comes at us to do the maximum amount of harm (read Job 1 and Job 2 to see how, once God gave Satan permission, how hard and fully Satan attacks Job and his life. He does not stop short of the fullest attack). In any event, I pray for people like Tim Cook, same as I pray for people like you, Kenny. A day of judgment is coming and I don't want you, or Tim, or anyone to be lost, so I stay the course and keep pointing you to Jesus so you too can be saved despite the many and heinous attacks, insults, and slanders. -- Rick C. Hodgin |
| Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk>: Apr 09 08:23PM +0100 On 09/04/2018 19:59, Dombo wrote: >> Rick probably shuns Apple because the CEO is gay, like me. >> /Flibble > Maybe you just like sausages. Yes, with HP Sauce. /Flibble -- "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>: Apr 09 02:17PM -0700 On 4/9/2018 11:57 AM, Rick C. Hodgin wrote: > to homosexuality, others to adultery and fornication, others to drugs > or alcohol or some other addiction. Each of us bears the weight of > sin's effect in our flesh. Imho, ethyl alcohol is a drug. No difference. I never really understood the separation. [...] |
| legalize+jeeves@mail.xmission.com (Richard): Apr 09 04:48PM [Please do not mail me a copy of your followup] Tim Rentsch <txr@alumni.caltech.edu> spake the secret code >In most cases this means the code is crossing too many levels of >detail. Trying to cover many levels of detail is a large part of >why big functions are hard to understand. My god, yes, this! -- "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline> The Terminals Wiki <http://terminals-wiki.org> The Computer Graphics Museum <http://computergraphicsmuseum.org> Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com> |
| Jorgen Grahn <grahn+nntp@snipabacken.se>: Apr 09 09:02PM On Thu, 2018-04-05, Paavo Helde wrote: > at all when I told him this is no good. He said he cannot think up > names for smaller functions and anyway he finds it easier to follow > the program logic if it is all nicely linear in a single function. He's right, of course: if you refactor your code in such a way that you have to read it all, every time, then that's /worse/ than one long function. But chances are that author actually needs to improve his refactoring skills. Perhaps you can sit down together and reason about ways of doing it? /Jorgen -- // Jorgen Grahn <grahn@ Oo o. . . \X/ snipabacken.se> O o . |
| "Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Apr 09 10:51AM -0400 On 4/9/2018 10:45 AM, Mr Flibble wrote: > On 09/04/2018 15:38, Chris Vine wrote: > We are talking about the significance of whitespace AFTER > preprocessing/tokenization. In the case of CAlive and Visual FreePro, Jr., they are not whitespaces but are linking spaces, a completely different character that is readily tokenized out during lexing and grouping together of co-joined symbols. From that point forward, the alphanumeric form of the variable name is all that remains as a thing in the language, making it easy to handle. The only unusual thing I had to add was a unique way to render that component. But, since my editor is linked directly to my compiler, the fact that the compile-time information is already there is the benefit which made it easy. I simply render the name like normal, and then post-process and re-render the one component using the high- lighted syntax. I can teach you how to do it if you like. -- Rick C. Hodgin |
| Ben Bacarisse <ben.usenet@bsb.me.uk>: Apr 09 05:39PM +0100 >> *The* *Worst* *Idea* *EVER*. > It's famously allowed (or was, if they've changed it) in Fortran and > Algol 68, among others. There's some talking at cross purposes here. Fortran ignored spaces (except for the special columns) so you could have them pretty much anywhere, and Algol 68 allowed spaces in identifiers. However, in neither case were the spaces significant. -- Ben. |
| Manfred <noname@invalid.add>: Apr 09 06:54PM +0200 On 4/9/2018 3:52 PM, David Brown wrote: >> 02 to produce pointers to instances of CWhatever for both a >> and b? > I am sure you are not the first person to want this. I would say the first to /consider/, not to want this. But I think most > and since both currently mean the same thing ("a" is a pointer, "b" is > an object) then there is absolutely zero chance of it being changed - it > would break lots of code. It is even more than that: it is just so basic (I would say dogmatic) in C tokenization that whitespaces are not significant between different symbols: the declaration "T*x" is equivalent to "T* x" or "T *x" in the same way as "a+b" is equivalent to "a + b". This goes to the extent that even newlines are not significant. C (and, by inheritance, C++) programmers are used to this since the beginning of time, and appreciate that this allows for adapting to one's readability preferences without any impact on the meaning of the code. In my opinion it is simply undesirable. |
| gazelle@shell.xmission.com (Kenny McCormack): Apr 09 05:30PM >So, C++ syntax isn't complicated or ambiguous enough, it's necessary to >make white space significant? >I'll go along with that (since I'm never going to use C++ anyway)... Then why are you even reading, much less posting to, a C++ group? -- Donald Drumpf claims to be "the least racist person you'll ever meet". This would be true if the only other person you've ever met was David Duke. |
| gazelle@shell.xmission.com (Kenny McCormack): Apr 09 05:32PM In article <DJednduAcrqH5lbHnZ2dnUU78WHNnZ2d@giganews.com>, Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> wrote: ... >that. People are free to believe whatever nonsense they want and I >would defend their right to do so however that does not mean that I >have to respect those beliefs. Actually, we *ARE* ridiculing Ricky. For posting wildly off-topic crap in a technical newsgroup. If he did his stuff in religious groups, we'd be fine with it. I realize that he can't help it. And that's what makes it so deliciously awful to read it. -- The randomly chosen signature file that would have appeared here is more than 4 lines long. As such, it violates one or more Usenet RFCs. In order to remain in compliance with said RFCs, the actual sig can be found at the following URL: http://user.xmission.com/~gazelle/Sigs/InsaneParty |
| "Öö Tiib" <ootiib@hot.ee>: Apr 09 10:50AM -0700 On Monday, 9 April 2018 19:18:30 UTC+3, Rick C. Hodgin wrote: > https://groups.google.com/d/msg/comp.lang.c/Tq6ChAOreAg/IGz_FJ_VAAAJ > Conversion to/from UTF will be possible, but will be a layer atop > the fundamental forms. To my knowledge ASCII is encoding that has only 7-bit characters. How you convert from UTF-8? Convert that into your "ASCII of DOS video-cards of eighties" encoding: std::string name = u8"ℛ𝒾𝒸𝓀"; Also, what you wrote did not even attempt to answer my question. What you did does not conform to anything actually working now and also gives no benefits visually in your on tools. So why? |
| "Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Apr 09 01:59PM -0400 On 4/9/2018 1:50 PM, Öö Tiib wrote: > To my knowledge ASCII is encoding that has only 7-bit characters. ASCII and extended-ASCII. I grew up in the DOS days, and ASCII was all 256 characters. > How you convert from UTF-8? Convert that into your "ASCII of DOS > video-cards of eighties" encoding: > std::string name = u8"ℛ𝒾𝒸𝓀"; Each character in the "ASCII of video cards" will map to and from UTF-8 by translation tables. > Also, what you wrote did not even attempt to answer my question. > What you did does not conform to anything actually working now > and also gives no benefits visually in your on tools. So why? Nobody has to use it. It's a new feature. You can use variable names with underscores all day long. You can use camelCase, or OtherCase or whatever. The goal is to look to the future when the complete system is ready, and to give people an option to use if they want to. -- Rick C. Hodgin |
| scott@slp53.sl.home (Scott Lurndal): Apr 09 06:08PM >> To my knowledge ASCII is encoding that has only 7-bit characters. >ASCII and extended-ASCII. I grew up in the DOS days, and ASCII was >all 256 characters. "Extended ASCII (EASCII or high ASCII) character encodings are eight-bit or larger encodings that include the standard seven-bit ASCII characters, plus additional characters. The use of the term is sometimes criticized,[1][2][3] because it can be mistakenly interpreted to mean that the ASCII standard has been updated to include more than 128 characters or that the term unambiguously identifies a single encoding, neither of which is the case." |
| "Öö Tiib" <ootiib@hot.ee>: Apr 09 11:19AM -0700 On Monday, 9 April 2018 20:59:33 UTC+3, Rick C. Hodgin wrote: > The goal is to look to the future when the complete system is > ready, and to give people an option to use if they want to. Perhaps in future there are more people who are satisfied by being limited with 256 symbols of eighties. Currently it is unpopular option. Most require Unicode support. |
| "Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Apr 09 02:23PM -0400 On 4/9/2018 2:19 PM, Öö Tiib wrote: > Perhaps in future there are more people who are satisfied by > being limited with 256 symbols of eighties. Currently it is > unpopular option. Most require Unicode support. In the future I plan to implement a 32-bit system allowing for 100,000 characters per language, with the first 256 of each being available as 8-bit forms, and up to 65,536 being in 16- bit forms, and the full range in 32-bit forms per character: https://groups.google.com/d/msg/comp.lang.c/Tq6ChAOreAg/IGz_FJ_VAAAJ I think our current hodge podge systems are inadequate. We need a single, unified, extensible system. That one allows for up to ~43,000 language forms to each have 100,000 symbols. It can also be reduced to allow ~430,000 languages to each have 10,000 symbols, all with their own 8-bit and 16-bit access for the most common symbols. -- Thank you! | Indianapolis, Indiana | God is love -- 1 John 4:7-9 Rick C. Hodgin | http://www.libsf.org/ | http://tinyurl.com/yaogvqhj ------------------------------------------------------------------------- Software: LSA, LSC, Debi, RDC/CAlive, ES/1, ES/2, VJr, VFrP, Logician Hardware: Arxoda Desktop CPU, Arxita Embedded CPU, Arlina Compute FPGA |
| "Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Apr 09 02:47PM -0400 On 4/9/2018 2:08 PM, Scott Lurndal wrote: > interpreted to mean that the ASCII standard has been updated to > include more than 128 characters or that the term unambiguously > identifies a single encoding, neither of which is the case." I'll re-write it for you: I grew up in the DOS days, and "ASCII" was all 256 characters. Better? Even to this day all video cards still come with support for the 256 character set from back then. There are 8-scan line forms, 14-scan line forms, and 16-scan line forms, among others. A person can download them here if you like: http://www.libsf.org:8990/projects/LIB/repos/libsf/browse/es2/ES1/VGA They were scanned from an ATI video card in November, 2017: http://www.libsf.org:8990/projects/LIB/repos/libsf/browse/es2/ES1/VGA/VGA.CPP -- Thank you! | Indianapolis, Indiana | God is love -- 1 John 4:7-9 Rick C. Hodgin | http://www.libsf.org/ | http://tinyurl.com/yaogvqhj ------------------------------------------------------------------------- Software: LSA, LSC, Debi, RDC/CAlive, ES/1, ES/2, VJr, VFrP, Logician Hardware: Arxoda Desktop CPU, Arxita Embedded CPU, Arlina Compute FPGA |
| bartc <bc@freeuk.com>: Apr 09 07:58PM +0100 On 09/04/2018 18:30, Kenny McCormack wrote: >> make white space significant? >> I'll go along with that (since I'm never going to use C++ anyway)... > Then why are you even reading, much less posting to, a C++ group? Why, is it a prerequisite to have to use a language in order to be able to read discussion about it? I sometimes look at the Fortran group, and have even read the Awk group, and don't code in either. But I have briefly dabbled in all of them. Languages are languages. Was my comment about C++'s syntax incorrect or irrelevant? The second bit was a joke. You're the second person to bring this up; I thought you were against people attempting to police unmoderated groups. |
| scott@slp53.sl.home (Scott Lurndal): Apr 09 07:08PM >I'll re-write it for you: > I grew up in the DOS days, and "ASCII" was all 256 characters. >Better? No, wrong is still wrong. >Even to this day all video cards still come with support for the >256 character set from back then. There are 8-scan line forms, >14-scan line forms, and 16-scan line forms, among others. So what? Backwards compatability is de rigour for modern hardware, so they can still run obsolete software like windows and DOS. Doesn't make it any form of standard, nor should any new software adopt it in place of rational, well-considered and universally supported standards like Unicode and encodings such as UTF-8. |
| "Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Apr 09 03:22PM -0400 On 4/9/2018 3:08 PM, Scott Lurndal wrote: >> I grew up in the DOS days, and "ASCII" was all 256 characters. >> Better? > No, wrong is still wrong. I identified it above as "ASCII and extended-ASCII" correctly. My use of quotes indicates "that's what we all (all of the DOS-based developers I knew at that time) called ASCII." You're just nitpicking. I know ASCII is only the lower 128 chars. I know Extended-ASCII is the upper 128. I grew up in an environment where we called that ASCII because every DOS-based computer had that full set baked into it (in CGA), and by default in EGA/VGA, and to this day it remains. > any new software adopt it in place of rational, well-considered > and universally supported standards like Unicode and encodings > such as UTF-8. Why do my goals and methods affect you, Scott? If I choose to move in this way, designing a whole new system from the ground up, how are you impacted? What difference do my efforts make in your life when I'm over here, and you're over there? -- Rick C. Hodgin |
| Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk>: Apr 09 08:26PM +0100 On 09/04/2018 20:22, Rick C. Hodgin wrote: > move in this way, designing a whole new system from the ground > up, how are you impacted? What difference do my efforts make in > your life when I'm over here, and you're over there? The fractal wrongness continues unabated. https://www.google.co.uk/search?q=fractal+wrongness&source=lnms&tbm=isch&sa=X&ved=0ahUKEwiEvJb_9a3aAhUKKMAKHY8XDwMQ_AUICigB&biw=1547&bih=672&dpr=2.25 /Flibble -- "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." |
| "Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Apr 09 03:30PM -0400 On 4/9/2018 3:26 PM, Mr Flibble wrote: > https://www.google.co.uk/search?q=fractal+wrongness&source=lnms&tbm=isch&sa=X&ved=0ahUKEwiEvJb_9a3aAhUKKMAKHY8XDwMQ_AUICigB&biw=1547&bih=672&dpr=2.25 LOL! Remember this day also, Leigh. :-) -- Rick C. Hodgin |
| legalize+jeeves@mail.xmission.com (Richard): Apr 09 05:06PM [Please do not mail me a copy of your followup] Tim Rentsch <txr@alumni.caltech.edu> spake the secret code >Interesting comment. I don't think of SOLID as being the same as >having an OOP viewpoint, but it's still interesting that you got >to SOLID only after using TDD. I knew about it in theory, but for some reason it just didn't seem to come up in practice. That was because it is so easy to mix together concrete classes in C++ (and there is additional "work" in creating abstract interfaces) and there were no design or cultural forces pushing me in that direction. For instance, noone ever said in a design/code review "this should be an abstract interface because details should depend on abstractions". It came up in the Software Craftsmanship meetups and at agile conferences, but those were all after I was "test infected". >> run-time polymorphism. >The C++ community has a history of using non-standard terminology >or using established terminology in different ways [...] I guess you have to ask the question "established by whom?"; C++ has been around for such a long time that you could make the case that it used the terminology before it was "established by Java" or "established by C#". About the only other OO languages that were around when C++ was created were Smalltalk and Simula. >[...] A more recent >example is "concepts", which sounds like useful functionality, but >"concept" is an awful name for it. This term has been used in the standard for quite some time to refer to the different models that template arguments are supposed to have, e.g. InputIterator concept requires *i and ++i if i is an instance of a type that models the InputIterator concept. While we might be able to come up with a better term than concept at this point, the historical presence in the standard means that using another term would lead to more confusion than illumination. Human languages are messy. -- "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline> The Terminals Wiki <http://terminals-wiki.org> The Computer Graphics Museum <http://computergraphicsmuseum.org> Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com> |
| 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