JellyBot Source code

Tr: Bunu Darkorbite Göre YapabiIirmiyiz ??
En: Darkorbit TransIate Bot

Quote:

Originally Posted by »jD« Don't get too excited, this is old, but I thought some people might like to examine some code. I've been going through my pastebin to empty it out and found this code. Anyone can use it, its not much use these days, but it will work on all the private servers :3 Use it wisely. THE CODE, WOO HOO! [Only registered and activated users can see links. Click Here To Register...] -jD

Quote:

Originally Posted by darkunited Hehe, good release. I am amazed of the source code :) Not that I think it, but does this have something to do against the PSevers?

i think that you can read...

Quote:

Originally Posted by TheMiszczu LINQ is slower than loop, also lock using is bad idea.

LINQ is slower but more efficient. Don't hesitate, always use LINQ.

And locks are there so collections won't change during initialization, which is actually good.

Quote:

Originally Posted by darkunited Hehe, good release. I am amazed of the source code :) Not that I think it, but does this have something to do against the PSevers?

You just gave me an idea ;)

thanks a lot mein friend ^^

Thanks jD for sharing this source !
Maybe it helped me. :)

Quote:

Originally Posted by ReSp3cT.Pro i think that you can read...

I guess I can't then. Where do you see it say "I have released this to show my hate against all private servers"?

<RANT>

Quote:

Originally Posted by TheMiszczu LINQ is slower than loop,

First mistake, The JIT will compile most LINQ statements to loops and will actually optimize them to kingdom come. The first time the LINQ runs, yes, it will be slow, but after that the time difference between a LINQ call and a for loop is less than 3 ticks. Infact, a LINQ query is faster than a foreach loop in most instances.

I couldn't imagine writing functions to find the first item in a collection in a for loop. The C# Compiler will actually use functions to optimize the searching of collections when used with an enumerator (eg. LINQ).

Quote:

Originally Posted by TheMiszczu also lock using is bad idea.

ARE YOU CRAZY?!?! Try writing the same code but without locks. You will get 100000 exceptions due to the collection changing whilst it's enumerating. Locks are like the first thing any programmer should use, even if you aren't managing LINQ queries! Sure, locks aren't needed in single thread applications, but because the "paint" function is run on the GUI thread and the Receiver is run on a separate thread, you NEED locks.

</RANT>

-jD

Very Good JD Thank's! :D

pbdo bot not trusted offlinee :(

Quote:

Originally Posted by -yusuf000- pbdo bot not trusted offlinee :(

@JD
Nice one jd;)

You knew somebody converted it to vb/c# i dont remember anymore... lol and released it on this forum?



is this pbdo bot thread/forum?
I dont think so.

#reported 'spam'