- "Why < cstlib > is more complicated than you might think" - 1 Update
- cmsg cancel <nb7lv3$8ob$5@dont-email.me> - 1 Update
- pronunciation of "Bjarne Stroustrup" - 2 Updates
- "Current Proposals for C++17" - 1 Update
- Union of bitfields and larger type on ARM - 1 Update
- send email and socket programming - 1 Update
| Ian Collins <ian-news@hotmail.com>: Mar 03 10:20AM +1300 Lynn McGuire wrote: >> are written in C++. Perhaps a majority of them. Aided by the fact >> that C++ _is_ derived from C. > What do you do when your embedded program runs out of ram? Does the car crash? Most smaller embedded applications (whether C or C++) don't use dynamic allocation. -- Ian Collins |
| bleachbot <bleachbot@httrack.com>: Mar 02 10:32PM +0100 |
| "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com>: Mar 01 06:25AM +0100 On 01.03.2016 05:37, Stefan Ram wrote: > danske navn "Bjarne Stroustrup". Jeg beklager, at det er > skrevet på engelsk. Alligevel, måske nogle danske læsere er > interesseret i dette spørgsmål.) I'm Norwegian, and I pronounce it with "U" last. But I'm not sure what would be correct Danish pronunciation of the first part of the surname. I pronounce it like midway between "strøstrup" and "strøustrup". This is why we just call him Bjarne. Or sir Bjarne. In a parallel universe where he was knighted. Surnames are so confusing, e.g. my own. Cheers & hth., - Alf |
| Bertel Lund Hansen <gadekryds@lundhansen.dk>: Mar 01 10:00AM +0100 Stefan Ram skrev: > The wrong pronunciation [O] is the vowel as in the English > »off«/»default«. The correct one [U] is as in English »would«. No, it's not. It's the vowel in "pose" that is the closest one. I do not know IPA so I can't give you the symbol. Crossposted to: comp.lang.c++, dk.kultur.sprog -- Bertel - stadig med Linux |
| legalize+jeeves@mail.xmission.com (Richard): Mar 01 06:55AM [Please do not mail me a copy of your followup] Dombo <dombo@disposable.invalid> spake the secret code >their own string, container...etc classes and mechanisms. All of this >was understandable in the nineties before C++ was standardized but is >unforgivable in this day and age. That's a fair criticism. wxWidgets (and I assume Qt, but I know less about how they decide future directions) would welcome a modern version of the toolkit that used C++ more directly. However, consider that wxWidgets is constrained by the underlying GUI toolkit of the environment (Win32, Cocoa, Tcl/Tk, whatever). There isn't always a good mapping from modern C++ to these underlying systems. And jesus, no, we don't need something that isn't an evolution of what we currently have. In other words, creating an ivory tower type GUI library that feels good from a modern C++ perspective, but provides no bridge to existing GUI technologies or API is a complete waste of time. Existing defacto standards have momentum and pretending that your library is better without that momentum on your side is silly. It can't be 10% or even 50% better if you're proposing an entirely new library, it has to be 5000% better to convince people it's worth learning/switching from what they already know. >Development of WinForms has stopped well over a decade ago, [...] The key thing you're all missing when you list GUI libraries for these other languages is THEY ARE NOT PART OF THE STANDARD. Sometimes this is because there is no standard for the language, or because the standard only specifies the language and not any pile of libraries on top). C# standard doesn't specify the .NET Framework, which is a pile of libraries from Microsoft. And so-on. My point is that these other languages are doing just fine, thank you, without "standardizing" a GUI toolkit. So is C++. There is no need for a GUI toolkit in the C++ standard because we already have defacto standards that are serving the need just fine. I could understand this clamor for a GUI toolkit if there was nothing available and there was a huge screaming void, but there have been C++ GUI toolkit libraries since 1988 when InterViews was described and that was done straight on top of Xlib, which was a C API. <http://www.cs.tufts.edu/~nr/cs257/archive/mark-linton/interviews.pdf> -- "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline> The Computer Graphics Museum <http://computergraphicsmuseum.org> The Terminals Wiki <http://terminals.classiccmp.org> Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com> |
| Paavo Helde <myfirstname@osa.pri.ee>: Feb 28 12:47AM +0200 On 27.02.2016 23:40, Jerry Stuckle wrote: > bugs in it, though. > I actually think this was a big cause of the eventual failure of their > compiler. Except that it is not dead. Nowadays this is called Embarcadero C++Builder and the last release according to Wikipedia was on 31 Aug. 2015 (C++Builder 10 Seattle (23)). |
| alexo <alelvb@inwind.it>: Feb 29 02:16PM +0100 Il 14/02/2016 18:01, alexo ha scritto: > Hello group, > I've written for UNIX a little program [FLTK] that needs to send an > order through e-mail. [...] I've found the bug! PEBKAC !! cutting and pasting the payload source function I had forgot to select a part of it. The compiler told me I had left an unmatched brace so I added it leaving a mangled function that was doing nothing. And so the infinite apparent data transmission. All is well that ends well Thank you all for your help and patience. |
| 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