"Cpp2 and cppfront: Year-end mini-update" by Herb Sutter

[Lynn McGuire]

"Cpp2 and cppfront: Year-end mini-update" by Herb Sutter

https://herbsutter.com/2022/12/31/cpp2-and-cppfront-year-end-mini-update/

"As we close out 2022, I thought I’d write a short update on what’s been
happening in Cpp2 and cppfront. If you don’t know what this personal
project is, please see the CppCon 2022 talk on YouTube."

"Can C++ be 10x Simpler & Safer? - Herb Sutter - CppCon 2022"
https://www.youtube.com/watch?v=ELeZAKCN4tY

Lynn

[Michael S]

1. Too many youtube videos, too little written text.
I don't watch/hear videos with technical context. Approximately at all.
So, not much I can write below.

2. Roadmap looks good. Mostly.

3. I don't believe that the roadmap can be implemented under constrains of
"100% seamless link compatibility always (no marshaling, no thunks, no
wrappers, no generated 'compatibility modules' to import/export C++
code from/to a different world)".

4. But this Sutter guy knows more than myself about languages, compilation
and linking, so there is a certain hope that he is right and I am not.

[Albert]

On 01/01/2023 18:28, Michael S wrote:
>
> I don't watch/hear videos with technical context. Approximately at all.
>

Neither do I. I rely mainly on written articles with examples which I
can compile and run on my machine. The article posted here contains an
example that is alien to me. My C++ program were always like so:

int main()
{
std::cout << "Hello World!" << std::endl;
return 0;
}

but the article gives a link that shows like so:

<https://user-images.githubusercontent.com/1801526/189241726-db92ae64-2b2f-4463-a0c3-87794062da9c.png>

I have never written progs like that so now I'll need start doing that!!!!!.

[Michael S]

I never write programs like yours and I have no intentions to start doing that.
Mine look like that:
int main()
{
printf("Hello World!\n");
return 0;
}

IMHO, it's much better.

[Lynn McGuire]

But printf is not type safe.

Lynn

[Öö Tiib]

With string constant as format string it is in practice as most
compilers warn about type mismatches.

[Lynn McGuire]

That is indirect type safety. I prefer embedding calls to sprintf and
fprintf in my own utilities such as my 16 variations of my asString
method and my scrwri and outwri methods. That way, if there is a
problem then I have a common place to show the error and fix it.

Lynn

[Chris M. Thomasson]

Reminds me of the various ways to pass variables into a GLSL shader:

https://registry.khronos.org/OpenGL-Refpages/gl4/html/glUniform.xhtml

[Öö Tiib]

OK. We still get diagnostics so it is direct enough for user. Open
source IDEs like QtCreator warn as one types. Meanwhile the
"type safe" std::cout also causes common newbie problem
that "I wanted to output some int8_t value but see � or some
other strange symbol."

[Alf P. Steinbach]

On 2 Jan 2023 20:35, Stefan Ram wrote:

> Albert <Albert....@gmail.com> writes:
>> but the article gives a link
>

> BTW: 20 years ago, Herb was still active in Usenet
> as one moderator of "comp.lang.c++.moderated".

He was on the moderator list, one of the founders I believe, and he
maintained the group's web pages: the guidelines and the list of
moderators. And he may have been actively moderating in 2002. But when I
started, in 2006, he was not an active mod any longer.

However, he /participated/, also in this group, comp.lang.c++, until at
least 2011.

And that activity includes the Guru Of The Week postings.


- Alf