Sunday, November 27, 2022

Digest for comp.lang.c++@googlegroups.com - 25 updates in 6 topics

Gary Scott <garylscott@sbcglobal.net>: Nov 26 06:35PM -0600

On 11/26/2022 1:33 PM, Lynn McGuire wrote:
> for the users to specify their simulation.  The main window looks a lot
> like Visio.
>    https://www.winsim.com/screenshots.html
 
These would have been super easy with GINO. It was designed exactly for
this type of application. A GUI API tailored specifically for Fortran.
 
 
Lynn McGuire <lynnmcguire5@gmail.com>: Nov 26 08:39PM -0600

On 11/26/2022 6:35 PM, Gary Scott wrote:
>> USA states )California, etc) are starting to regulate cpu power
>> levels, these will probably drop as time goes on.
 
>> Lynn
 
We had a Gino CAD user interface on the Vax back in the 1980s. It was
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.
 
Lynn
Thomas Koenig <tkoenig@netcologne.de>: Nov 27 08:40AM

> like Visio.
> https://www.winsim.com/screenshots.html
 
> 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?
scott@slp53.sl.home (Scott Lurndal): Nov 27 04:33PM

>>> levels, these will probably drop as time goes on.
 
>>> Lynn
 
>We had a Gino CAD user interface on the Vax back in the 1980s.
 
I would expect that 40 years of updates would have fixed
the problems you note below.
 
http://gino.co.uk/
 
 
Mr Flibble <flibble@reddwarf.jmc.corp>: Nov 27 10:16AM

C++ templates are great for creating mixins. #cpp #gamedev #coding
 
template <typename LayoutItemType>
class size_policy_of_parent : public LayoutItemType
{
private:
typedef LayoutItemType base_type;
public:
using base_type::base_type;
public:
neogfx::size_policy size_policy() const override
{
if (base_type::has_size_policy())
{
return base_type::size_policy();
}
else if (base_type::has_parent_layout_item())
{
return base_type::parent_layout_item().size_policy();
}
return base_type::size_policy();
}
};
 
/Flibble
Bonita Montero <Bonita.Montero@gmail.com>: Nov 27 03:40PM +0100

Am 27.11.2022 um 11:16 schrieb Mr Flibble:
> }
> };
 
> /Flibble
 
You could also do a ...
 
if constexpr( requires( base_type base ) { base.xxx(); } )
...
Bonita Montero <Bonita.Montero@gmail.com>: Nov 27 03:41PM +0100

Am 27.11.2022 um 15:40 schrieb Bonita Montero:
 
> You could also do a ...
 
>     if constexpr( requires( base_type base ) { base.xxx(); } )
>         ...
 
 
if constexpr( requires( base_type base ) { { base.xxx() } ->
convertible_to<base_type::size_policy>; } )
Mr Flibble <flibble@reddwarf.jmc.corp>: Nov 27 03:16PM

On Sun, 27 Nov 2022 15:40:17 +0100, Bonita Montero wrote:
 
 
> You could also do a ...
 
> if constexpr( requires( base_type base ) { base.xxx(); } )
> ...
 
If I could have used if constexpr then I would have used if constexpr; I
cannot use if constexpr as size policy is dynamic not static.
 
/Flibble
Bonita Montero <Bonita.Montero@gmail.com>: Nov 27 04:37PM +0100

Am 27.11.2022 um 16:16 schrieb Mr Flibble:
>> ...
 
> If I could have used if constexpr then I would have used if constexpr;
> I cannot use if constexpr as size policy is dynamic not static.
 
I would dispatch that whole thing inside th LayoutItemType.
Mr Flibble <flibble@reddwarf.jmc.corp>: Nov 27 03:56PM

On Sun, 27 Nov 2022 16:37:57 +0100, Bonita Montero wrote:
 
 
>> If I could have used if constexpr then I would have used if constexpr;
>> I cannot use if constexpr as size policy is dynamic not static.
 
> I would dispatch that whole thing inside th LayoutItemType.
 
You obviously don't understand how mixins work and are asserting things
based on ignorance of the architectural design of my project.
 
/Flibble
Mr Flibble <flibble@reddwarf.jmc.corp>: Nov 26 11:29PM

On Sat, 26 Nov 2022 14:47:44 -0800, Chris M. Thomasson wrote:
 
>> VS2019 just to get a working debugger. Also experienced ICEs with
>> VS2022.
 
> I found some oddities in 17.4.1 wrt the IDE, but nothing major.
 
Well I would classify a non-working debugger and ICEs are pretty fucking
major.
 
/Flibble
Mr Flibble <flibble@reddwarf.jmc.corp>: Nov 26 11:30PM

On Sun, 27 Nov 2022 00:33:32 +0200, JiiPee wrote:
 
 
>> /Flibble
 
> can u give one example of a bug? I use it in my work but did not find
> anything major yet.
 
I don't have the time to create a test case.
 
/Flibble
"Öö Tiib" <ootiib@hot.ee>: Nov 26 06:00PM -0800

On Sunday, 27 November 2022 at 01:30:55 UTC+2, Mr Flibble wrote:
> > anything major yet.
> I don't have the time to create a test case.
 
> /Flibble
 
You are lucky to have vs 22 ... i have only vs 19 ... perhaps because my
own policy to ignore tools and technologies younger than 2 years old
with excuse of immaturity.
Bonita Montero <Bonita.Montero@gmail.com>: Nov 27 08:02AM +0100

Am 27.11.2022 um 00:30 schrieb Mr Flibble:
 
 
>> can u give one example of a bug? I use it in my work but did not find
>> anything major yet.
 
> I don't have the time to create a test case.
 
 
LOL !
JiiPee <kerrttuPoistaTama11@gmail.com>: Nov 27 10:24AM +0200

On 27/11/2022 09:02, Bonita Montero wrote:
>>> anything major yet.
 
>> I don't have the time to create a test case.
 
> LOL !
 
haha
Mr Flibble <flibble@reddwarf.jmc.corp>: Nov 27 10:14AM

On Sun, 27 Nov 2022 08:02:06 +0100, Bonita Montero wrote:
 
>>> anything major yet.
 
>> I don't have the time to create a test case.
 
> LOL !
 
What's so funny? It is not my job to fix Visual Studio, I have created
Visual Studio bug reports in the past and, yes, I did create test cases
for those bug reports.
 
/Flibble
Bonita Montero <Bonita.Montero@gmail.com>: Nov 27 01:08PM +0100

Am 27.11.2022 um 11:14 schrieb Mr Flibble:
 
> What's so funny? It is not my job to fix Visual Studio, I have created
> Visual Studio bug reports in the past and, yes, I did create test cases
> for those bug reports.
 
VC++ bug reports are public. Show me the links.
Mr Flibble <flibble@reddwarf.jmc.corp>: Nov 27 01:23PM

On Sun, 27 Nov 2022 13:08:06 +0100, Bonita Montero wrote:
 
>> Visual Studio bug reports in the past and, yes, I did create test cases
>> for those bug reports.
 
> VC++ bug reports are public. Show me the links.
 
I believe I made myself clear that I haven't created a bug report for
VS2022 issues.
 
/Flibble
Bonita Montero <Bonita.Montero@gmail.com>: Nov 27 04:38PM +0100

Am 27.11.2022 um 14:23 schrieb Mr Flibble:
 
>> VC++ bug reports are public. Show me the links.
 
> I believe I made myself clear that I haven't created a bug report for
> VS2022 issues.
 
I referred to you past filed bugs.
Mr Flibble <flibble@reddwarf.jmc.corp>: Nov 27 03:54PM

On Sun, 27 Nov 2022 16:38:49 +0100, Bonita Montero wrote:
 
 
>> I believe I made myself clear that I haven't created a bug report for
>> VS2022 issues.
 
> I referred to you past filed bugs.
 
Why do you want to view those?
 
/Flibble
Bonita Montero <Bonita.Montero@gmail.com>: Nov 27 01:29PM +0100

#if defined(_WIN32)
#include <Windows.h>
#elif defined(__unix__)
#include <unistd.h>
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)