Does anyone here program ASM?

[BlizzHaX0r]

Hey all,
I'm new here, but I was wondering if anyone programs in Assembly. I'm 13...if I can do it, I think anyone can :P

[Grizzly]

A lot of us here have college degrees is something CS related, so by virtue of that a lot of us have had at least one semester in Assembly. I don't think I've met anyone that's taken it much farther than that though. It's not something people really enjoy doing in their spare time.

But hey, kudos to you for taking the dive into the wild world of Assembly at age 13.

[cjohnson]

I found assembly to be fun/interesting :/

[Big_Mac]

well, it's a powerful language, and if you are a logical person or have excellent algorythms, you can write killer code, but for most purposes, writing in c++ or java or VB is faster, easier, and more likely to be understood by the next guy that needs to work on your code.

Remember, all your programs should be able to be understood by a fresh set of eyes, because you never know when it'll be necessary.

[slavik]

in the corporate world ...

Originally posted by Big_Mac
well, it's a powerful language, and if you are a logical person or have excellent algorythms, you can write killer code, but for most purposes, writing in c++ or java or VB is faster, easier, and more likely to be understood by the next guy that needs to work on your code.

Remember, all your programs should be able to be understood by a fresh set of eyes, because you never know when it'll be necessary.

[Adisharr]

I don't know anyone that has the time or want to do a project in assembly. I can't imagine anyone would find it fun but to each his own. Other than microcontrollers / embedded systems stuff I don't see much of a need to learn use it for anything (other than education).

Ladder Logic (I hate calling this a 'language') is the closest thing to assembly I use right now. For most machine control it's adequate but when you start doing any math other than very simple expressions is very frustrating keeping track of all the temporary variables and having to break everything up into smaller sub-expressions.

[ua549]

I stopped using assembly laguage back in the early 80's. Even then it's only use was for things requiring tight code such as operating systems and special hardware.

Ahhhhh, the good old days. NOT!

[BlizzHaX0r]

Sorry that it's taken me so long to replay guys, I've been busy with football, soccer, school, homework....etc lately.

I know that ASM isn't the easiest or most convienient to program in, it IS the most powerful language, and is faster than languages such as C++. ASM, if it floats your boat, can also be used for hacking :P, especially with maphacks and **** like that.

That's my 2 cents :P

[Remington]

C++ compilers these days generate very tight code. You'd be hard pressed to beat one for speed alone. The only reason you'd have to use asm is if you needed to do something really specific.

[Big_Mac]

Originally posted by BlizzHaX0r
Sorry that it's taken me so long to replay guys, I've been busy with football, soccer, school, homework....etc lately.

I know that ASM isn't the easiest or most convienient to program in, it IS the most powerful language, and is faster than languages such as C++. ASM, if it floats your boat, can also be used for hacking :P, especially with maphacks and **** like that.

That's my 2 cents :P

Ever heard of MLX? (aka Machine Language?) it's lower level, and as such, given a perfect programmer with plenty of time on his hands, would be faster and tighter than ASM. Sorry dude, assembly is a pretty powerful language, but it's still not the lowest level.

Originally posted by slavik
in the corporate world ...

not just the corp world. If I write crappy, poorly documented and illogical code (that still works) for a class, I lose marks. If I do the same on a group assignment, they'll boot me from the group because I'm useless. If I'm collaborating on some code for a new linux kernel with some people across the world, my code had best be intelligable and easily understood. In the corp world, it'll get you fired. Even if you're just writing a neat little program that you'll release as freeware, have good source. If someone wants to use your code, they'll be able to. And do it for yourself. Six months down the road, if you have to patch something in your own work, you won't remember anything...

here:
int I[10],J=0;
long double Something=1;
for (J=0;J<10;J++)
{
scanf("%d",I[J])
};
Something = SOME UGLY GODAWFUL EQUATION;

now, wouldn't it be nice to make
long double Something=1;
look like
long double Something=1; //Holds the next prime number larger than the sum of all I[]

AND

Something = SOME UGLY GODAWFUL EQUATION;
look like
Something = SOME UGLY GODAWFUL EQUATION; //stores the next largest prime after the sum of all I[]

now, isn't the documented code just a little safer? it may take an extra 30 seconds now, but it'll save you three hours sometime down the road when you need to figure out what the heck Something is and what an ugly equation does.

And most of all, do it out of pride. You can either write ugly code, or good code. It's ultimatly your choice, but out of pride, I'd hope you pick good code.