So whats with BJ's?

03-31-2007, 11:32 PM	#1
kingofJasons	I heard that GUI uses "nasty bj functions". So what I'm asking here is -Why are bj's bad for triggering? -What does "bj" stand for? I also heard something about changing bj's to natives, if someone could clarify that I'd be greatful. Also if there's something related to this topic that could answer my questions then please redirect me.

03-31-2007, 11:44 PM

Ammorth

Bj = Blizzard J, which is a reference to the file that has all the Bj functions listed.

Bjs are bad for triggering because they usually do nothing extra special, except change the order in which the inputs are in. This means they add an extra function call for no real reason. When doing many iterations of a Bj, you will get un-needed lag due to the use of the extra function call.

Natives are what the Bj functions call in the end. They are the "raw" functions that are built directly into the engine.

04-01-2007, 09:07 AM	#3
blu_da_noob	And thus BJ's are slow because function calls are very slow in JASS. Otherwise they wouldn't be too much of a problem.

04-01-2007, 09:50 AM	#4
ixmike88	JASS: function DestroyEffectBJ takes effect whichEffect returns nothing call DestroyEffect(whichEffect) endfunction In conclusion (along with the other posts), BJ functions own.

04-01-2007, 11:35 AM

The)TideHunter(

Quote:

Originally Posted by ixmike88

JASS:

function DestroyEffectBJ takes effect whichEffect returns nothing
    call DestroyEffect(whichEffect)
endfunction

In conclusion (along with the other posts), BJ functions own blizzard's ass in programming history, and really suck.

Fix't.

04-01-2007, 02:22 PM

Alevice

Quote:

Originally Posted by The)TideHunter(

Fix't.

Way to miss the joke, mister

04-01-2007, 02:23 PM	#7
kingofJasons	Thanks for clearing this up guys, learn something new everyday :)