Results
|
Choice
|
Votes
|
|
Percent
|
1 day.
|
30
|
5.1%
|
|
1 week.
|
65
|
11.1%
|
|
1 month.
|
57
|
9.8%
|
|
3 months.
|
40
|
6.9%
|
|
6 months.
|
25
|
4.3%
|
|
1 year or more.
|
38
|
6.5%
|
|
I don't program in assembly.
|
328
|
56.3%
|
|
|
Re: How long did it take you to learn to program in assembly language?
|
Chris Perkins
(Web Page)
|
1 WEEK BABY!Oh yeah I am going to trie to get TIcalc to post some of my strats on programming both asm and basic and include an appology for one of my decisions with a finished game.I am not going to state what the decision is but I will state it soon.Please dont ask me right now.
Chris Perkins
|
Reply to this comment
|
11 April 2000, 00:56 GMT
|
|
Re: How long did it take you to learn to program in assembly language?
|
Mike Dombrowski
(Web Page)
|
I read a post earlier about Pokémon...I tried to play the new Pokémon 2 on my 83+ but when I put it on, I only had about 60k left and it wasnt enough to run. I didnt have anything on my calc cept the stuff for the game. I sent a mail to help@ticalc.org but never received a response...Can someone please tell me if I can run that game on a 83+ and if so, what I need to do in order to have enough memory to do so.
Thanks,
Royal
|
Reply to this comment
|
12 April 2000, 01:12 GMT
|
|
|
|
|
|
|
|
Re: Re: Re: How long did it take you to learn to program in assembly language?
|
Paulo Marques
(Web Page)
|
Yeah, so what else is knew?
Well, so stop posting messages complaining about pokemon, and just help the poor bastard...
BTW, Laura, may I stalk you too? I mean, I don't have anything else to do, and I could be nice to you, but why bother? It's much funnier this way. (and here we go, turning this discusion into another male/female interaction thing... (ops... lack of right words there) but, then again, I don't think this discusion is going anyfurther though)
|
Reply to this comment
|
13 April 2000, 00:51 GMT
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Ops...
|
Paulo Marques
(Web Page)
|
First off, I had no idea how you are, since I live in the other side of the world. (Portugal, for those who care, and I don't lke it either) Secondly, if I've touched a nerve, so sorry, but I just meant it as a joke. Thirdly, just the fact you're a girl involved in PCs/programming/... is enough for anybody to kid aroud with you (since your a female). Fourth, actually, from your desciption, I take it you're very atractive and nice young girl, enough for me to keep pissing you off. :-)
Just a complement, anyway...
|
Reply to this comment
|
15 April 2000, 22:07 GMT
|
|
Howza.
|
Grauw
(Web Page)
|
The question is rather vague. Do you mean how long it took me to learn the mnemonics (not long, they are quite limited so it's not that hard) or do you mean how long did it take me to write my first decent program in Assembly Language? I voted with the last one, it must be about three months before I really wrote something else then "Hello world" thingies.
But that in fact is not really the end. Still, even after about 6 years of assembly programming (since about my 12th) I am learning everyday, discover new things everytime. Nowadays, it's mainly programming tricks and 'nifty' stuff like messing with the stack and speed stuff, but still, you might call it learning. I mean, I know the mnemonics very well now, but I still don't know the timings of every instruction. And three years ago, I still used mnemonics which didn't exist (like for example LD DE,(HL)). And I still don't program bug-free (although lately I see an increase in the nr. of routines which immediately work).
It's a process, of which -to my opinion- the length can't be exactly specified. Next time, rephrase the question to something like "how long did it take you to write your first decent assembly-program"... Which ofcourse again raises the question: "what's decent"... Ah, whatever. Just be a bit more specific.
Well, that's my addition to this discussion.
~Grauw
|
Reply to this comment
|
13 April 2000, 21:55 GMT
|
|
|
|
|
Re: Howza.
|
Andy Selle
(Web Page)
|
Well, when I wrote the question, I intended it to mean "how long did it take before you could write decent assembly programs?" I mean you really don't "learn" to program merely by knowing the opcodes. The idea that you have "learned" something implies that you are able to use it to an end. Much in the same way, many people claim to have learned C/C++, when in fact all they know is the syntax. You don't really learn C/C++ until you fully understand pointers, which takes longer than learning the syntax. This is a general case in that the semantics cannot be learned as easily as the syntax. This property manifests itself in compilers. It is very easy for them to catch syntax errors, but it is almost impossible for them to find the semantic errors. Thus, we have bugs. In any case, yes my question was vague, and I'll try to make it more detailed next time.
|
Reply to this comment
|
14 April 2000, 16:22 GMT
|
|
Compromise
|
Ciaran McCreesh
(Web Page)
|
OK, maybe I can sort things out here (yeah right, I'll probably start a flame war).
Different programming languages are for different things.
ASM, for example, is really the only option for programming very fast things for calculators. OK, BASIC can be fast, but it isn't as powerful. C(++) is nice but too slow for a few things.
Anyway, I generally find that Delphi is better than any C(++) for programming in Windows. It's just less messing about, all your code does something useful rather than having a load of stuff that isn't important. OK, sometimes C is definitely better but usually it isn't worth the extra time it takes to develop. The loss of performance is very slight. I've just written a WYSIWYG HTML table editor, it took me about two hours in Delphi. There are things that are easy in Delphi that would take hours in C. The resulting code is virtually the same.
Anyway, different languages are for different things.
Ciaran
|
Reply to this comment
|
14 April 2000, 19:53 GMT
|
|
1 2 3 4 5 6
You can change the number of comments per page in Account Preferences.
|