ULINK2 transistor T1

Note a few things on the data sheet:

First, the code has a "VOLATILE" on underside for cooling purposes. The cooling is through the software delay. That's how you can dissipate significant power in such small and "flimsy looking" function.

Secondly, the code has also thermal protection and other protections.

I have not personally used this code, but I wouldn't be too worried: I have used C++ in the same type of library, and even placed a cooling loop on the opposite side of the code. No trouble at all, actually I over-designed it, and the code was cool as a cucumber. Could have skipped the cooling recursive entry and thermally conductive calling convention....

Check your ANSI standards for more information.

Note a few things on the data sheet:

First, the code has a "VOLATILE" on underside for cooling purposes. The cooling is through the software delay. That's how you can dissipate significant power in such small and "flimsy looking" function.

Secondly, the code has also thermal protection and other protections.

I have not personally used this code, but I wouldn't be too worried: I have used C++ in the same type of library, and even placed a cooling loop on the opposite side of the code. No trouble at all, actually I over-designed it, and the code was cool as a cucumber. Could have skipped the cooling recursive entry and thermally conductive calling convention....

Check your ANSI standards for more information.

Sorry, but your post doesn't seem to have anything with this thread to do. Exactly what are you talking about?

Code and volatile? The volatile keyword does not have anything at all to do with cooling.

I think it's supposed to be a joke?

Just like the OP?