Thanks Francisco, you're correct. I just tend forget to use references when passing stuff around 😊

There's no problem in using variables as copies, but be careful because there're some types that can't be copied (like unique_ptr)

I told ya

You can dm me

no

I quit

ok go

I guess it's the nice thing about unique_ptr, that it prevents you from copying it.

btw, do you use auto a lot? Or do you tend to use explicit typing instead?

btw, do you use auto a lot? Or do you tend to use explicit typing instead?

I prefer auto if there's no ambiguity or if the type is too long to type. I prefer to type auto rather than std::unique_ptr<Sprite>

use explicit types for primitive types and auto for everything else

but be careful

But if you read someone else's code, and its full of auto, it can get confusing, no?

indeed, but as I know there are some ides which show an original type

But if you read someone else's code, and its full of auto, it can get confusing, no?

Well, depends on the code, I guess

/warns

It looks like Qtcreator supports auto keyword inspection of the real type. Mm..

it's tempting indeed :)

It looks like Qtcreator supports auto keyword inspection of the real type. Mm..

Well, good luck inspectioning the type of a lambda

Anyway, if you use the auto keyword, you're forced to initialize the variable. That would help a lot when reading the code

Any books for me I'm a biginner

Any books for me I'm a biginner

Pinned message

Any books for me I'm a biginner

Someone's back from the future lol

hi

can anyone recommend me the best visual studio c++ tutorials

you make me want to kill chicken

I hate Java, Python and Visual BASIC.

P-Python?

Book says : a long constant too big to fit into an int will be taken as a long. So why we put a sufficed "l" or "L" after long constants like : 123456789L ?

I hate Java, Python and Visual BASIC.

😱😱😱😱

I hate Java, Python and Visual BASIC.

my secret alter ego

Hey!

lol .substring(0, 3)

Hey!

Hey

Hello guys... Help me how to utilize the long lifetime variable... ( option explicit)

I made a program for Android using Kotlin in like 3 days (though the program wasn't complex) but still it was my first app and it was pretty good, not the best but good enough.

What's kotlin

what should be the output guys?

No idea..

what should be the output guys?

anybody wants to give a try?

come on it's a C++ group..

What's kotlin

Kotlin is https://kotlinlang.org/

anybody wants to give a try?

ctor

unless you overloaded copy constr

Only if it's move aware

Not otherwise

what should be the output guys?

in this, the output is: ctor without any optimization. Is this a correct behaviour given that copy elision is disabled? I believed that ctor and then copy ctor will be called. But I was wrong.

Move version of constructor and assignment should be marked as noexcept if possible.

aha, this is fun :D

I want a c program for array sort and print the sort array elements in alternatively

Any one help

aha, this is fun :D

WTF

WTF

Trust whom?

In t1.ball = malloc(strlen(t1.ball) + 1);, the dereference operation of t1.ball on the right side of assignment is UB.

UB means that: compilers can do whatever on codes, and everytime you run your target code can result in different output.

Consequence: trust neither.

nighter?

nighter?

sorry for typo.

neither

233

😂

this portion has been generated by clang for x86

what does DWORD PTR mean after a NOP?

I know that it is a size directive but NOP takes no parameters, right?

It's just noping for a DWORD right?

Printf("I am human");

It's just noping for a DWORD right?

what do you mean?

Nop is just padding, right? I assume it's just repeating the instruction to fill a whole DWORD

ok, but I don't see the point of a 32 bit nop

Just to fill space

No idea why though

what about the [rax + 0x0] address?

I'm not sure, this is a different assembly dialect than I'm used to

No idea why though

Hm, maybe to match the executable format

Possibly

I'm not sure, this is a different assembly dialect than I'm used to

Hm... what assembly do you know?

x86 NASM

16 bit real mode

Hm... I can't reproduce it

Odd

I'm studying how structs are compiled from C.

how would you represent a struct in x86 ?

I'm not entirely sure