When you return an object from a function, does it return the address of that object?

no. it returns the object. which is copy/move constructed/assigned to at call-site.

What's call site

Ok so the object will be returned from function and it'll be copied to the call site object. Right?

And will it be shallow or deep copy?

And will it be shallow or deep copy?

depends on the object itself and the constructor/assignment operator used.

In most cases yes. But when Return Value Optimization or NRVO applies then the object is directly constructed at the call site.

What's nrvo

What's nrvo

'n' denoting the number of strings to sort.. constraint is 1 <= n <= 10^5... when i write this string s[100005]; i get segmentation fault but when i write this int n; cin»n; string s[n].... the code runs successfully. why is it so

The crash happens because you exhausted the stack memory per thread. Btw VLA is not in the C++ standard but instead provided as a compiler extension. So it should not be used in C++ code. It is possible that the compiler optimized out the allocation in the latter case because you are not using the array in anyway. Try taking the address of the array in the latter case and see if it crashes. If it doesnt crash, it is possible that the array is not allocated on the stack but on the heap. The C standard doesnt specify where the array is allocated. It just requires that the array be deallocated at the end of the scope in which it is defined. GCC allocates it on the stack using alloca function on *nix platforms. But it is possible that some other compiler doesnt.

The crash happens because you exhausted the stack memory per thread. Btw VLA is not in the C++ standard but instead provided as a compiler extension. So it should not be used in C++ code. It is possible that the compiler optimized out the allocation in the latter case because you are not using the array in anyway. Try taking the address of the array in the latter case and see if it crashes. If it doesnt crash, it is possible that the array is not allocated on the stack but on the heap. The C standard doesnt specify where the array is allocated. It just requires that the array be deallocated at the end of the scope in which it is defined. GCC allocates it on the stack using alloca function on *nix platforms. But it is possible that some other compiler doesnt.

What do you mean by Taking the address?

And also if I do compile time allocation then it is always allocated on stack right? So why will it be allocated on heap.?

The point of VLA is to specify an array size not know at compile time. So how can the allocation be done at compile time?

'n' denoting the number of strings to sort.. constraint is 1 <= n <= 10^5... when i write this string s[100005]; i get segmentation fault but when i write this int n; cin»n; string s[n].... the code runs successfully. why is it so

Unity uses C#

Unity is easier as it does A LOT of stuff for you

im creating an FPS offline game for IGI fans. should i entirely code my game in c# or should i use unity?

depends on your preference.... short answer would be to use whatever you are comfortable with, long answer would be long... but if you want to discuss it, then i will write it

then you will have to tell me your motivation behind the project

i am afraid i don't understand how it is connected

how is that connected to the game you want to create?

then buy a computer and you don't have to decide between c+= and c#

so it's not about learning to code, but it is about creating a game so you would get money?

you do not know the pain of being poor

i do

i do know the pain, i was 12 years with i3-380m with gt-310m

yeah, it's enough

i don't think we (as this c/c++ group) can help you in this matter

+ it's getting quite offtopic... but everyone had to start somewhere....

if you just want to create game, you can have a look at godot, i have heard it is not as that bad and it is opensource

Basically at the core of ALMOST every game, is some kind of game engine, which handles all or most of the stuff i mentioned Without a game engine of some kind, it is difficult to make a 3D game that is of reasonable quality, if at all

Which basically boils down to Use an existing game engine to build your game Or create your own game engine to build your game