C is super fast language,but hard to master.

Not really... and not really...

C is not the fastest language.... C is also the easiest language for me.

C is not the fastest language.... C is also the easiest language for me.

cjen: So what is int(*(*foo)(const void *))

That is pointers I can make that stuff in Pascal too and it gets worse in assembly.

I once meet a PhD who claims her master c in one week.

And she never free memory.

cjen It's the same thing in Pascal any older language has same exact issues, if you compare C with C# then just because C# runs on a stupid .NET framework which takes care of garbage collection it doesn't make it simpler, it makes it how should I put it... impotent.

Gc is not issue in PL level.

And the statement is no problem.

I didn't even understand what you said... what do you mean GC is not in PL level?

Ok garbage collection is not PL?

Well there are no native compilers of C#... no none not even one.

Of course not.

they were planning to do .net native, some gibrish converter (removes that layer of net) but seems like its inactive project

but you guys, are #ot

It's talking about C being hard... it's not OT

it’s comparesment and stuff, but anyways

Come on no one is talking about anything today...

Varzish tajakistan

Hello

What does that mean?

Hello means hi

lol.

Hello means hi

No it doesn't... Hi is used in friendly manner only, Hello could be used by anyone.

No it doesn't... Hi is used in friendly manner only, Hello could be used by anyone.

sir, ...

sir, ...

ma'am...

Saar

And she never free memory.

So she leaves memory leaks or never makes a program that uses over 4MB of memory?

Because both ways that's stupid

So she leaves memory leaks or never makes a program that uses over 4MB of memory?

Actually in C you don't have big leaks, worst leak you can have if you malloc memory and do not free it, C++ has the issue of memory leaks because you can create object and forget to free it.

Actually in C you don't have big leaks, worst leak you can have if you malloc memory and do not free it, C++ has the issue of memory leaks because you can create object and forget to free it.

Well no it's just that with objects you'll leak more because they're bigger

Leaks also happen in C#, I made a program to display random images from server, but when I ran the application it kept getting bigger... problem was I didn't free the "graphics" object, I did the same program in Lazarus and because I knew I had to free it, I did that and it worked fine. Other problem was C# doesn't allow me to free everything, I couldn't find what I wasn't freeing for days.

So no garbage collector isn't always good, because you can make an unmanaged application in C#, unlike Java and that could leak memory.

Simple C has almost 0 leaks if you do not malloc, you'll not have leaks.

C++ is better on that behalf

You can leak resources almost everywhere

You can leak resources almost everywhere

CAN yes

Good design is important

^^^^^

C++ has big advantages with - for example - references

references are safe

Well they can get confusing in terms of ownership if used incorrectly but yeah

Also with garbage collectors you can have cyclic references and with that you again have: leaks (kinda) the python garbage collector actually resolves cyclic references if you do not overwrite the destructor with your own del But thats also another point for good design

ewww

python

python

python

Simple C has almost 0 leaks if you do not malloc, you'll not have leaks.

How's C++ different in that regard? new always goes through malloc

eww

How's C++ different in that regard? new always goes through malloc

You can create object and not free it...

Simple C has almost 0 leaks if you do not malloc, you'll not have leaks.

if you don’t malloc what

You can create object and not free it...

In C you can create a variable and not free it

Same thing

In C you can create a variable and not free it

Variables can't be "freed".

Try doing that.

You can create object and not free it...

Only if you create it on the heap and thats the same as C

Variables can't be "freed".

if you declare them on the stack

Only if you create it on the heap and thats the same as C

You have to create objects in C++, you don't have to use heap in C

Variables can't be "freed".

What?

You have to create objects in C++, you don't have to use heap in C

tf

You have to create objects in C++, you don't have to use heap in C

Umm

Dude heap is used like all the time

if you declare them on the stack

Yes if you do something that is complex... sure.

Yes if you do something that is complex... sure.

int i;

There we go its on the stack

You're getting some fundamentally different things mixed up here

Yes if you do something that is complex... sure.

Or like anything that requires over 4MB of memory

You're getting some fundamentally different things mixed up here

Like what? Do I have to free a variable I decleared as int i = 0;?

Like what? Do I have to free a variable I decleared as int i = 0;?

No

Like what? Do I have to free a variable I decleared as int i = 0;?

It will be on the stack

That's on the stack

But lets say a dynamic array

And when I'm out of the function what happens to the stack?

Or a linked list

And when I'm out of the function what happens to the stack?

Nothing

The stack is cleared....

Its just there, probably will get overwritten

The stack is cleared....

nope

And when I'm out of the function what happens to the stack?

Gets cleared unless it's with a static lifetime

Gets cleared unless it's with a static lifetime

Not rlly you still can access it actually