not even a huge amount of data.. this like 1000 mesgs/sec lol .. i wonder if it's due to lower rate.. idk for now

No one is gonna code for you. If you have a specific problem, send the code and all the details and kind people in the chat is gonna help you.

Thanks, but I already solved the exercise

Thanks, but I already solved the exercise

I don't care

I don't care

🙊 but np

Also anyone got groups for assembly and malware analysis

What is the key difference b/w visual studio and vs code

What is the key difference b/w visual studio and vs code

Visual Studio only runs on macOS and Windows. VS Code can run on macOS, Windows as well as Linux. Not many professionally developed plugins are available for Visual Studio. VS Code comes with a wide range of professionally curated plugins and extensions to meet all kinds of editing and compiling needs.

Then why people yse VS

*use

What is the key difference b/w visual studio and vs code

One is IDE and one is editor

What is the key difference b/w visual studio and vs code

Vs code is a light weight code editor that has a large ecosystem of extension visual studio is and ide, it supports different languages by fefualt (i use it only for C++ or C#), honestly the only worth ide for C++,

Vs code is a light weight code editor that has a large ecosystem of extension visual studio is and ide, it supports different languages by fefualt (i use it only for C++ or C#), honestly the only worth ide for C++,

is your last sentence? >honestly the only one worthy IDE for C++ (is VSCODE)

Uh, sorry

Uh, sorry

wasn't that bad, np

Vs code is a light weight code editor that has a large ecosystem of extension visual studio is and ide, it supports different languages by fefualt (i use it only for C++ or C#), honestly the only worth ide for C++,

Doesn't seem lightweight at all for a code editor

Doesn't seem lightweight at all for a code editor

if you don't add any extensions...

if you don't add any extensions...

Why use a browser at all tho

Why use a browser at all tho

why use a program at all tho

Fair but if it advertises itself as lightweight, and if one is really concerned about performance, I don't think VS code would be falling into that category

But well you are right.. It's just a tool.. So nvm

foo(string const& myname) more advantage than foo(string const* myname) relating to null refererence. Can somebody explain me ? foo(string const& myname) vs foo(string const &myname) does the same thing ?

& myname And &myname both are same, space doesnt create any difference that is how the language works

foo(string const& myname) more advantage than foo(string const* myname) relating to null refererence. Can somebody explain me ? foo(string const& myname) vs foo(string const &myname) does the same thing ?

are these homework/test/exam questions?

are these homework/test/exam questions?

it does look like it

Heay, btw i havent heard any null reference, i have always used nullptr, is null reference even valid?

Heay, btw i havent heard any null reference, i have always used nullptr, is null reference even valid?

Of course no

Heay, btw i havent heard any null reference, i have always used nullptr, is null reference even valid?

no, i don't think null references even exist

foo(string const& myname) more advantage than foo(string const* myname) relating to null refererence. Can somebody explain me ? foo(string const& myname) vs foo(string const &myname) does the same thing ?

This guy is leaving in parallel universe

int* p = nullptr; int& r = *p; std::cout << r; yep null references dont exist

int* p = nullptr; int& r = *p; std::cout << r; yep null references dont exist

It's not a valid C++ code

it compiles, links, and runs, what do you mean

it compiles, links, and runs, what do you mean

It doesn't mean it's valid lol

define valid

define valid

Conforms to the C++ standard

which line does not conform to the standard?

which line does not conform to the standard?

Reading the dangling reference

It's undefined behavior

oh ok sorry int* p = nullptr; int& r = *p; r is still a null reference

It's undefined behavior

Show me the line is standard where its described

Show me the line is standard where its described

Find it yourself, smartass :)

oh ok sorry int* p = nullptr; int& r = *p; r is still a null reference

It's not a null reference, it's a dangling reference

Pointer is run-time variable, you can not have a knowledge about will it be a null or not

Find it yourself, smartass :)

Lol

Pointer is run-time variable, you can not have a knowledge about will it be a null or not

So what lol?

How does it make a C++ program valid or not?

Thats another question

Thats another question

What question have you answered then? :)

Find it yourself, smartass :)

.

.

Dude, when you're trying to read an object which lifetime has not started, it is undefined behavior Is that so hard to understand?

One example in the standard of that would be: http://eel.is/c++draft/basic.life#7

Show me the line is standard where its described

dcl.ref/5 Note: in particular, a null reference cannot exist in a well-defined program, because the only way to create such a reference would be to bind it to the “object” obtained by indirection through a null pointer, which causes undefined behavior.

dcl.ref/5 Note: in particular, a null reference cannot exist in a well-defined program, because the only way to create such a reference would be to bind it to the “object” obtained by indirection through a null pointer, which causes undefined behavior.

I thought that indirection to null is ok while you're not trying to access it

oh ok sorry int* p = nullptr; int& r = *p; r is still a null reference

So this also has undefined behavior:)

int a += b; yep this also has undefined behavior

dcl.ref/5 Note: in particular, a null reference cannot exist in a well-defined program, because the only way to create such a reference would be to bind it to the “object” obtained by indirection through a null pointer, which causes undefined behavior.

definitely undefined behaviour

int a += b; yep this also has undefined behavior

The code itself is invalid just like its author

bruh you got me there what about this int a, b; // ... a += b; undefined behavior

It's a random number generator

bool b; is also some kind of qubit

Also depending on compilers optimizations

bruh you got me there what about this int a, b; // ... a += b; undefined behavior

I'm not sure, probably it is also undefined behavior http://eel.is/c++draft/basic.indet#2

bruh you got me there what about this int a, b; // ... a += b; undefined behavior

(I thought you were trolling)

I'm not sure, probably it is also undefined behavior http://eel.is/c++draft/basic.indet#2

I was trying to talk about another type of UB other than indeterminate values, imagine a and b being initialized later on something like this int a, b; a = 2000000000; b = 1000000000; a += b;

int* answer = (int*)malloc(sizeof(int)); *answer = 42; This is also undefined behavior before C++20 :) But it behaved as expected on all the implementations because otherwise it would be a nightmare for the C and C++ compatibility In C++20 they added a wording that malloc and some other functions implicitly start a lifetime for some types of objects

I was trying to talk about another type of UB other than indeterminate values, imagine a and b being initialized later on something like this int a, b; a = 2000000000; b = 1000000000; a += b;

Well, either a program has an undefined behavior or not does depend on the runtime properties sometimes

For some inputs it does have an UB, for other - does not

classic c++ be careful with your c++ everyone, c++ tends to bite you when you least expect it

int* answer = (int*)malloc(sizeof(int)); *answer = 42; This is also undefined behavior before C++20 :) But it behaved as expected on all the implementations because otherwise it would be a nightmare for the C and C++ compatibility In C++20 they added a wording that malloc and some other functions implicitly start a lifetime for some types of objects

Isn't casting value that malloc returned bad practice ?

For some inputs it does have an UB, for other - does not

You are right. Using uninitialized variables to initialize other variables is generally Undefined Behavior. There are exceptions only for char (if it is unsigned char on the implementation), unsigned char and std::byte.

Isn't casting value that malloc returned bad practice ?

If you do not do the cast, the code is not going to compile in C++

Isn't casting value that malloc returned bad practice ?

☠

If you do not do the cast, the code is not going to compile in C++

Ah, so it only applies in C then

even in c you should cast it

even in c you should cast it

https://stackoverflow.com/questions/605845/do-i-cast-the-result-of-malloc

those points are retarded in that post

those points are retarded in that post

Care to explain?

It is unnecessary, as void * is automatically and safely promoted to any other pointer type in this case. well now have fun importing the code to a c++ project It adds clutter to the code, casts are not very easy to read (especially if the pointer type is long). what clutter, if you name ur shit with long ass names, you have other issues It makes you repeat yourself, which is generally bad. blah blah blah, sometimes repeating yourself is better It can hide an error if you forgot to include <stdlib.h>. This can cause crashes (or, worse, not cause a crash until way later in some totally different part of the code) your code won't compile congrats

What is the best way to make cpp GUI applications

What is the best way to make cpp GUI applications

C'mon be an engineer. It depends at least on platform and complexity of that app.

What is the best way to make cpp GUI applications

If you really want to go with other's opinion, use qt