- int number {89} - 2 Updates
- Microsoft Visual Studio 2022 (C++) buggy as hell - 8 Updates
- converting a 700,000+ line Fortran 77 plus 50,000+ line C++ - 3 Updates
"gdo...@gmail.com" <gdotone@gmail.com>: Nov 27 01:03PM -0800 this is not the best idea for change. int number = 86.9 could have been handled as an error by the compiler, much like int number {86.9} assignment, int number = 5; , this is a much less complex thought and the meaning is clear. string name{"Paul"}; string name = "Paul"; why the initialization is preferred syntax for c++20, good grief. feels like change for change sake. |
"gdo...@gmail.com" <gdotone@gmail.com>: Nov 27 02:43PM -0800 if ( int value{7}; value == 7) { ... } else {...} come on there can't be much use of this can there? it seems it leads more hacking of code then well thought code. like, I'm starting typing in code and oh yeah I realize a need an integer here so let me stick it in. no worries though cause it's scope is limited. hm? I guess that is in keeping with the 'c' way. I'm looking forward to a chance to use it. don't think it makes the code more readable or concise but oh well. '17 . c++20 here we come. |
Bonita Montero <Bonita.Montero@gmail.com>: Nov 27 06:11PM +0100 Am 27.11.2022 um 16:54 schrieb Mr Flibble: >>> VS2022 issues. >> I referred to you past filed bugs. > Why do you want to view those? You don't have filed any bug. |
Mr Flibble <flibble@reddwarf.jmc.corp>: Nov 27 05:32PM On Sun, 27 Nov 2022 18:11:07 +0100, Bonita Montero wrote: >>> I referred to you past filed bugs. >> Why do you want to view those? > You don't have filed any bug. You are a child if you think saying that will force me to dig up my past bug reports just to satisfy your curiosity. I don't have to prove myself to you. /Flibble |
Bonita Montero <Bonita.Montero@gmail.com>: Nov 27 07:36PM +0100 Am 27.11.2022 um 18:32 schrieb Mr Flibble: > You are a child if you think saying that will force me to dig up my past > bug reports just to satisfy your curiosity. I don't have to prove myself > to you. You're a liar. |
Mr Flibble <flibble@reddwarf.jmc.corp>: Nov 27 06:46PM On Sun, 27 Nov 2022 19:36:26 +0100, Bonita Montero wrote: >> past bug reports just to satisfy your curiosity. I don't have to prove >> myself to you. > You're a liar. You're an idiot. /Flibble |
Bonita Montero <Bonita.Montero@gmail.com>: Nov 27 08:02PM +0100 Am 27.11.2022 um 19:46 schrieb Mr Flibble: >>> myself to you. >> You're a liar. > You're an idiot. That's ok if I'm an idiot for you. But I'm not a liar ! |
Mr Flibble <flibble@reddwarf.jmc.corp>: Nov 27 08:05PM On Sun, 27 Nov 2022 20:02:42 +0100, Bonita Montero wrote: >> You're an idiot. > That's ok if I'm an idiot for you. > But I'm not a liar ! Neither am I, dear. /Flibble |
Vir Campestris <vir.campestris@invalid.invalid>: Nov 27 10:00PM On 27/11/2022 19:02, Bonita Montero wrote: >> You're an idiot. > That's ok if I'm an idiot for you. > But I'm not a liar ! I don't always agree with Bonita, but this time I do. You're telling us it's so full of bugs you can't use it, but you haven't filed any reports nor can you tell us what any of them are. Andy |
Mr Flibble <flibble@reddwarf.jmc.corp>: Nov 27 10:36PM On Sun, 27 Nov 2022 22:00:43 +0000, Vir Campestris wrote: > You're telling us it's so full of bugs you can't use it, but you haven't > filed any reports nor can you tell us what any of them are. > Andy As I have said already I don't have the time to create test cases. Do you even know what a test case is? It is the *least* amount of compilable code that reproduces the problem. It is not always easy to pare down an existing codebase into a test case for a bug report especially in the case of internal compiler errors (ICEs). Also, as with Bonita, I couldn't give one iota of a fuck as to whether you believe me or not. /Flibble |
Gary Scott <garylscott@sbcglobal.net>: Nov 27 10:38AM -0600 On 11/26/2022 8:39 PM, Lynn McGuire wrote: > not easy to write nor was it easy to maintain. The plotter/printer > interface was absolutely horrible, you essentially had to rewrite the > driver for each plotter or printer model. Its come a long way in 32 years. I've (combined with my employer) paid them about $50k to upgrade it in many areas. It started out as output only, similar to mainframe GDDM. But it now has full interactive graphics editing ability (including segments and transformations and attribute modifications for pre-drawn segments). Pretty much full CAD capability and is integrated with openGL if you choose that driver. It supports 2D and 3D but I've not had the need for 3D other than playing so I've not worked through that area of support. |
Gary Scott <garylscott@sbcglobal.net>: Nov 27 10:44AM -0600 On 11/27/2022 10:38 AM, Gary Scott wrote: > capability and is integrated with openGL if you choose that driver. It > supports 2D and 3D but I've not had the need for 3D other than playing > so I've not worked through that area of support. I'll also note that they're really nice people and will fix anything you need fixed. I've found them extremely responsive. Sometimes though a problem may be hard to reproduce so providing an example helps a lot. A problem is that it is a pretty huge code base for the size of the development/support team, but I've had numerous examples of overnight updates over the years. |
Lynn McGuire <lynnmcguire5@gmail.com>: Nov 27 01:59PM -0600 On 11/27/2022 2:40 AM, Thomas Koenig wrote: >> Writing commercial software requires a lot of code. > This is probably a few decades too late for the interface code, but > have you looked at GTK and its Fortran binding, fortran-gtk? No, that is not the problem. Thanks, Lynn |
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