[OpenSource Project] C++ CoCore

Can I have a question? How is your Queue implementation differing from the std::queue in the STL?

Quote:

Originally Posted by KraHen Can I have a question? How is your Queue implementation differing from the std::queue in the STL?

The main reason I made my own class would be because I'm offering a multithreaded core.

Quote:

Originally Posted by ImmuneOne The main reason I made my own class would be because I'm offering a multithreaded core.

My bad, lol. I didn`t realize STL containers weren`t thread-safe ones :) Ty :p

EDIT: Sticking to the server core plan.

NOTE: This project is not abandoned. I had some busy weeks at school and since I got 2 weeks off of school, I can get back to work on CoCore.

Quote:

Originally Posted by KraHen My bad, lol. I didn`t realize STL containers weren`t thread-safe ones :) Ty :p

Most people will argue otherwise but I think you should avoid STL, and create your own wrappers whenever possible >_>

Edit:
I don't see a use for an IDispoable in C++.

Quote:

Originally Posted by InfamousNoone Most people will argue otherwise but I think you should avoid STL, and create your own wrappers whenever possible >_>

I find STL pretty handy if you wrap classes around them for your needs, but I don't see why you'd totally avoid them.

Quote:

Originally Posted by InfamousNoone Edit: I don't see a use for an IDispoable in C++.

It's not IDisposable as in the .NET's IDisposable, same naming but different function. It is just a thread-safe referenced smart pointer which destroys objects after they're done with(from what I know).

Quote:

Originally Posted by Nullable I find STL pretty handy if you wrap classes around them for your needs, but I don't see why you'd totally avoid them. It's not IDisposable as in the .NET's IDisposable, same naming but different function. It is just a thread-safe referenced smart pointer which destroys objects after they're done with(from what I know).

Exactly as this 'unknown' guy above me says:p

Quote:

Originally Posted by Nullable I find STL pretty handy if you wrap classes around them for your needs, but I don't see why you'd totally avoid them. It's not IDisposable as in the .NET's IDisposable, same naming but different function. It is just a thread-safe referenced smart pointer which destroys objects after they're done with(from what I know).

Ah ok, that makes a little more sense. The reason I avoid STL is because half the time when you recode the shit yourself it's 1000x faster.

Ok -- I'm exaggerating a bit, but if you really want my test results, I'll go dig up my old FlexibleArray<T> class (which implements all the functionality of a vector<t> and a list<t>) and I'll show you the comparison between the speed. Bricks will be shat.

It is true that half.. well most of the STL classes are slow but if you test against something like map<key, value>, the results of searching/inserting/removing are pretty close to the R-B trees time complexity ( O(log N) ); so it's not that bad in some cases after all.

Quote:

Originally Posted by Nullable It is true that half.. well most of the STL classes are slow but if you test against something like map<key, value>, the results of searching/inserting/removing are pretty close to the R-B trees time complexity ( O(log N) ); so it's not that bad in some cases after all.

Well, once I first picked up on this; I stayed as far a way from STL as I possibly could. Any chance of you guys actually committing to the revision? I wouldn't mind pitching in a bit of help if you can specify what needs to be done.

Also, I assume you want this to be cross-platform (because your using boost instead of Windows Library functions), correct?

Quote:

Originally Posted by InfamousNoone Well, once I first picked up on this; I stayed as far a way from STL as I possibly could. Any chance of you guys actually committing to the revision? I wouldn't mind pitching in a bit of help if you can specify what needs to be done. Also, I assume you want this to be cross-platform (because your using boost instead of Windows Library functions), correct?

The first revision is near to be done, I'm just finishing some network wrappers.
But if you want to see it before the first revision is committed you can send me a PM. Oh and yes this is going to be cross-platform.

Quote:

Originally Posted by ImmuneOne The first revision is near to be done, I'm just finishing some network wrappers. But if you want to see it before the first revision is committed you can send me a PM. Oh and yes this is going to be cross-platform.

Ah, ok. No problem. I'll check back now and again then and wait for the first rev'.

Oh yes. I want this. I'll help as much as I can.

Little update; I have been offline and not working on the project lately, my laptop has been at repair service for awhile now and the project's files are on it. The thing is I'm struggling with the repair service to take the costs under my warranty. I guess it doesn't count if you have < 10 dead pixels and a burn-in which covers half of the screen:S