Video

If you look at it, the humble 6502 was the first RISC CPU. It had competition (6800, Z80, 6809, 8008/8080), but its minimized register count and minimized instruction set made it very simple to implement efficiently, and it could do everything that any other 8-bit CPU could do, and often just as quickly.

As mathematician I see Design Patterns as tricks language.

Why we can't execute ADD, SUB instructions in one clock cycle

45:21 Assuming sz can get very big, the argument to malloc can overflow and create a smaller allocation than expected. There's calloc for this purpose. Thought this was common knowledge.

16:30 Unfortunately this is also wrong, if it compiles, then only under C23. auto buffer = (char[42]){}; 1) the compound literal has an empty initializer list, which is not allowed according to ISO C (until C23 it was available as a gcc feature) 2) auto buffer : default type to int results in at least a warning (-Wall or -pedantic). 3) auto buffer : if the default type would be int (with warning) the type does not match, because the compound literal (char array of size 42) gives the address of the first element (char *) This would be a conversion from char* to int.

18:30 Unfortunately, this is not correct. The idea is to check whether the passed address belongs to an array that has AT LEAST (and not exactly) this many elements. void foo(char p[static 5]); char array[4]; foo(array); In this example, you would receive a compile warning. Both under clang and under gcc. The whole thing has its limits, of course. And of course the function cannot check whether a null pointer was passed if it was not already known as a constant value at compile time. foo(NULL) leads to a warning because a constant value was passed here. In the following example, the compiler has no way of determining at compile time whether NULL was passed. int x = 1; char const * p = "Hello"; if(x) p = NULL; foo(p); // No warning, even if p should be NULL The whole thing is not intended for this, but for cases in which a "real" array (as the address of the first element) is passed - and not a pointer. void accept(char const str[static 4]); char const a[] = "Hi"; char const * p = "Hi"; accept(a); // Warning with clang and gcc accept(p); // Warning with gcc (not with clang) Clang and gcc also do different things here to determine whether the limits of the array have been observed. For example, clang no longer warns at all if a pointer is passed. gcc tries - as far as it is possible at compile time. Unfortunately, the way it is presented in the video is not correct.

Long life to C

Thank You so much Filipp Gelman. This talk is really insightful.

Herb has great talks, but does anything he talks about happen?

Great talk!

1:22:34 I was unsure if the double cast was needed, but now I know.

ranges/view were one of the main things why i tried making our codebase ready for C++20. Even just the small things like splitting strings. And then we saw that while you could split strings there was no way of concatenating them back together in a similar style - ok, so we have to create our own compatible functionalities for that (the committee "forgot" about that and it was later added to C++23). Still not too bad - so lets test it... wait, why is everything broken? oooohhhh views are caching... and the code would need extensive reworking due to changes to enum, bool, volatile etc.... Yup, and back to C++17.

22:38 - "Do you think cheap is expensive?" - i sure hope nobody does.

Every time he says, "It's like in C++", I say, "Oh no"; "Oh no, they will make C look like that".

Something about static rules of the system that will always be there... The emulator would always be limited in outputs for exploits, at least then. He was asked to put in signal limitations and how factors effect this but he didnt like that idea and said it would be tedious and it is already in. "get a scrub to do it..someone who can burn time.""i will have to burn through physical chips to do it and even then i would be better at working on ai or exploits."

Best programming language that human kind invented.

I don't know if I love or hate the fact that the only people using C nowadays are Python devs

1:15:00 When functions are pure, then I'd say you extend them via pre- and post-composition with other functions. And I guess with generic arguments; (as said) with functions as arguments; and maybe by application of Functors ... fns in Lists, fns in Exception blocks, fns with Logging, Optional fns, a fn in an Either, fns in Futures, ... and maybe by replacement by an Interface(?)

A brilliant talk, very well delivered, thanks Roger!

when will be a risc v laptop be a reality?

The new features are neat if they will help reduce issues without requiring modifications of the existing code. But things like that non-NULL check are wack, if you start introducing those things you might as well recompile your code in C++ with use of references if needed. Not sure why they decided to make non-NULL argument descripton so complicated. It makes literally NULL sense.

Thank you a lot!

Thank you Mike!

Compound literals, don't they also exist in Java for example?

few people get it C is infinite in scope you can do anything you want with it and in any shape you want the only limit is yourself

15:42 that int (*pk)[ sz ] [ sz ] has the *pk in parenthesis because the array operator [] has higher precedence IF the parenthesis where not to be used you will have double array full of pointers to int which is a totally and completely differnt thing from a pointer variable , more so it will invalidate the malloc call , further reasoning *pk is a pointer to int therefore Encapsulates information about the data object aka int which is a 4bytes (32bits) this encapsulation/metadata if you want to call it such is what allows the pointer arithmetic to be performed it makes the pointer aware of the data object therefore when you add/sub 1 from it it will Move the instruction pointer registers exactly 4bytes using a LEA instruction it is extremely fast

Long live C.... the grandfather of all programming languages!

Always nice to see Herb! Why is the license of cppfront still NC? This will prevent it from being included in GNU/Linux-distributions once it gets ready unless you make all contributors sign a CSA and transfer all copyright to you.

And this, kids, is why you should buy a decent mike before recording videos

I do not get it, is it a stand up ?😄

Really useful, 3x

How long did it take for you guys to fully understand the language, along with its data structures and object-oriented programming concepts??

Let me teach you an expression: "We are just drilling a hole" This expression is used in the oil and gas industry, when all the crew panic, i just reset them to calm down, it gives insurance to your teammates that you are in control. Very powerful.

This is some fantastic work, thank's James!

my rule of thumb is. If a macro changes the C syntax, you shouldn't use it

this was such a good refresher on computer architecture.

Weird people of C++ community somehow flowed into the world of C and bring this mess. Long Live C17!

Wonderful reply for the hardware and then software issue. He doesn't cooked up any story , but instead provided a brave honest reply that most of the industry is not able to solve!

I first learned C in 1984, shortly after working a long time in assembler. I could not believe that there was a high-level language that was so sloppy, did not check anything much, did not give any warnings, just let your mistakes causes crashes and even bring down the whole machine in those day. Today I love C. It's minimal, the least "high-levelness" required to get one off assembler. It's small, one can can write a C compiler in reasonable time. It's best in class for performance. Today I also love Rust. Finally a high level language that banished UB and checks almost all silly mistakes I might make. While maintaining the performance of C and avoiding the monstrous complexity and ugliness of C++. And it interoperates with C very well. So I end up loving both C and Rust for polar opposite reasons. Rust will not replace C for me, they will coexist very well. I'm sure that is true in the wider world as well.

The plugboard is just a fixed substitution. You could try to match your message allowing for constant letter replacements, and it would still match regardless of the plugboard. This is a MUCH easier problem than needing to actually OBTAIN the plain text.

The fourth rotor never turned at all. It just added an extra level of fixed obfuscation.

The Poles cracked the commercial Enigma, which didn't have a plugboard.

15:56 - wait; the ring setting not only moved the turnover notch; it also shifted the whole alphabet against the rotor wiring. So yes, that last factor of 26 should be in there.

You've reversed left and right...

Basically the perfect Internet of Garbage processor ;-)

MIPS but with extra suck factor. 68k with orthogonal instruction set and lots of internal tricks and optimizations to make it go fast, would be Genius

The problem will most modern programming languages that have a large "market share" is that they're not driven by engineering or science anymore, but by mere competition. C++ gas grown into this monster only in an attempt to keep its market share, or even grow it. (Call that user base if you prefer.) Any newer language that would introduce some new paradigms or even just some new sugar coating would become an inspiration for the next iteration of C++. Just to prevent developers from moving away. That's just plain marketing. And marketing does infect everything it touches.