Omnimaga
Omnimaga => Completed => Our Projects => Hot Dog's TI-83+ Z80 ASM for the Absolute Beginner => Topic started by: Hot_Dog on April 24, 2010, 12:34:04 am
-
Hi, guys,
So I understand that many people wanting to learn ASM have a hard time doing so. I'm willing to attempt to teach the language in an easier way, with the idea being the lessons taking a long time (much longer than 28 days), but easy to work through. But I need a lot of people wanting to learn it, or it's not worth my time. Please consider that I won't be able to teach everything on ASM, as I've only begun using it myself, but at least it will be enough so that you can start using "Learn ASM in 28 days" or a similar language.
Let me know if you guys want to learn, and just remember, you're learning from someone who took three years before he could understand the language, so I will make sure that it's easy for the average ti-basic programmer to understand.
-
I personally am unsure really, because the learning process seemed long and I heard that coding RPGs in ASM (my favorite game genre) is a major hassle. You would have to ask Iambian how it is. However, I think ASM needs to be taught in an easier way than ASM in 28 days, which assumes the user has knowledge of another language besides BASIC and is taught without visual people/people with lower learning capacity in mind
Would it be in document form?
-
Would it be in document form?
Yes, it'd be one document for every lesson.
I personally am unsure really, because the learning process seemed long and I heard that coding RPGs in ASM (my favorite game genre) is a major hassle. You would have to ask Iambian how it is. However, I think ASM needs to be taught in an easier way than ASM in 28 days, which assumes the user has knowledge of another language besides BASIC and is taught without visual people/people with lower learning capacity in mind
My approach would be visuals, numerous examples, and perhaps labs. The thing that is almost guranteed to make the language easy is, it will take about 50 lessons to teach 1/3 of asm 28 days, covering only the important stuff (since people can download routines and stuff). Since I am not an expert on calculator hardware and still can do asm, I'm not going to teach much on hardware myself.
-
aaaah ok I see
-
Hmm, this could be helpful. I'm sure it would be great for a better ASM tutorial because I know asm in 28 days Is hard for some people.
-
I most likely would not learn Asm simply because there is still so much that i feel i can do in the languages that I know. Once i exhaust my creativity then i might transfer over to Asm :P
-
I didn't vote because I know the language, but this seems like a good idea.
Funnily enough sigma goes really slowly during the first 5-6 days, but then you basically have to do everything twice.
-
I want to learn it^^ So far, I'm upto day 10 in learn asm in 28 days, but I still don't know what the heck is going on. I kind of get the stacks and stuff, but I don't get the pointer and the whole ad and bc and hl etc. stuff... They are pretty hard, mostly because it lacks examples and visuals, and try-this-on-your-own things
-
So far, things are looking positive. I'm going to give great consideration if at least 5 people want to learn, very likely if 7, and I'd be a fool if I didn't teach at least 10 people who want to learn
-
It would be very nice to have this.
Do you think the tutorial would be available both in offline and online form, like how was ASM in 28 days before?
/me hopes this wont half S.A.D progress completly, though :(
-
Do you think the tutorial would be available both in offline and online form, like how was ASM in 28 days before?
It's going to be downloadable PDF files.
* DJ Omnimaga hopes this wont half S.A.D progress completly, though
Heaven forbid
-
ok phew x.x
-
I've attempted to tackle programming a few times, (not ASM) but I could never wrap my head around the logic of it. It's like staring at random characters and numbers, with no discernible pattern as to how they're being arranged.
I just don't think my brain is equipped for this type of logic. Maybe it's true that people who are inclined toward certain skills or reasoning will be less inclined toward others. For instance: I'm good with grammar and creative writing, but I'm absolutely terrible at math. I can force myself to learn how some particular task is done, but then I could literally forget how it was done just a few minutes later. When it comes to writing, I very easily understand the patterns because they're based in words.
-
i remember hearing about people being good at math but not good at language, or vice versa before. Some artistic people are also less good at programming, because they are more into designing than coding.
-
I think they depend on the development of your brain. I heard from somewhere that one half of the brain was for language and the other for math and stuff. I myself am good at Math and Science, but not much at language...
-
I just don't think my brain is equipped for this type of logic. Maybe it's true that people who are inclined toward certain skills or reasoning will be less inclined toward others. For instance: I'm good with grammar and creative writing, but I'm absolutely terrible at math. I can force myself to learn how some particular task is done, but then I could literally forget how it was done just a few minutes later. When it comes to writing, I very easily understand the patterns because they're based in words.
Curious.
For me, solving programming problems is very much like solving mathematical problems. I always have the same feeling while solving math problems and think in a way to code things. The kind of intelligence required must be similar, both in math and programming you are dealing a lot with numbers and variables.
About interpreting text, language and visual things, I don't have the same ease but I am ok at it.
I already learned assembly and captured the concepts with some difficulty and time. Some parts of ASM in 28 days I didn't understand at first because of C stuff there and advanced without had really learned a few things.
I long had the idea to write a ASM tutorial, without low level languages experience.
Maybe we can exchange some text and ideas. My advice right now is planning very well the tutorial.
Do the brainstorm of what topics are needed and their order (in a logical way, of course).
Then write some notes to remember to put examples, images, well commented source code examples, etc..
Finally write the topics, focusing on the first topics.
-
Strange... I don't wanna brag, but I'm good at language logic and 'mathematical' logic (I'm in a Latin+math group at school), so it's not necessarily an XOR. Then again, I have other big flaws. E.g. sometimes I just can't tell whether someone is mocking me or being serious (in real life). Very annoying and embarrassing.
As for my ASM learning curve: I basically did the tutorial once, hardly understanding half of it. Then, after a few months, I tried again, and I worked through everything up till the last few days. Next, exercise, exercise and more exercise. As soon as I mastered the basic concepts of the language, I tackled the rest of the tutorial, did some more coding, and well, here I am. :)
-
I long had the idea to write a ASM tutorial, without low level languages experience.
Maybe we can exchange some text and ideas. My advice right now is planning very well the tutorial.
Do the brainstorm of what topics are needed and their order (in a logical way, of course).
Then write some notes to remember to put examples, images, well commented source code examples, etc..
Finally write the topics, focusing on the first topics.
Dude, thanks for the advice!
-
Well, I think it could be a very attractive idea.
I tried to learn ASM with a BIG french pdf tutorial (which I didn't finished yet) traduced from an english one. It was only for 8x86 ASM and was very well written.
Thus I'am interested in your contribution.
On the other hand, on which "architecture" will you be based to write this ASM tutorial ? z80/68k/ARM ?
ARM, pleeeeeeeeeeeeeaaaaaze !
*is running away*
-
It's Z80
-
Yes, it's z80, but once you get the basic idea behind ASM in general, it doesn't take months to transfer from one form of asm to another. It's the basics that people have a hard time with.
-
I've always wanted to learn x86, but due to lack of good guides, I never actually managed. The concepts are the same, but you don't have the same degree of control, sadly enough :( (j/k, security would be a bitch)
-
Well, I think it could be a very attractive idea.
I tried to learn ASM with a BIG french pdf tutorial (which I didn't finished yet) traduced from an english one. It was only for 8x86 ASM and was very well written.
Thus I'am interested in your contribution.
On the other hand, on which "architecture" will you be based to write this ASM tutorial ? z80/68k/ARM ?
ARM, pleeeeeeeeeeeeeaaaaaze !
*is running away*
z80 actually, since pretty much all of Omnimaga are 83+/84+ users. I think we only have two 68k users and one is never active. For ARM, we have about 3 or 4 TI-Nspire coders, I think. It would be nice to see someone else write an ARM ASM tutorial written in a similar way as Hot_Dog tutorial. Hopefully, various types of tutorials can help more people. Those who find the alerady existing tutorials to be too hard can simply try other ones.
Example: this is not ASM but still related to tutorial difficulty: I couldn't understand some of the memory management commands in Axe Parser after reading the command list, and that lasted until I reread how they work in the documentation PDF. It was worded differently and put into some context, so I could understand more.
-
Well, I think it could be a very attractive idea.
I tried to learn ASM with a BIG french pdf tutorial (which I didn't finished yet) traduced from an english one. It was only for 8x86 ASM and was very well written.
Thus I'am interested in your contribution.
On the other hand, on which "architecture" will you be based to write this ASM tutorial ? z80/68k/ARM ?
ARM, pleeeeeeeeeeeeeaaaaaze !
*is running away*
z80 actually, since pretty much all of Omnimaga are 83+/84+ users. I think we only have two 68k users and one is never active. For ARM, we have about 3 or 4 TI-Nspire coders, I think. It would be nice to see someone else write an ARM ASM tutorial written in a similar way as Hot_Dog tutorial. Hopefully, various types of tutorials can help more people. Those who find the alerady existing tutorials to be too hard can simply try other ones.
Example: this is not ASM but still related to tutorial difficulty: I couldn't understand some of the memory management commands in Axe Parser after reading the command list, and that lasted until I reread how they work in the documentation PDF. It was worded differently and put into some context, so I could understand more.
Which reminds me, there may be one or two people who don't understand a topic no matter what, and that's life; but I am hoping people will let me know that they don't understand, because if several don't, I know I need to slow down
-
Yeah this is what I thought. Kinda like Axe Parser doc. I reviewed it a few times and would tell Quigibo when I didn't understand something. It's a good thing people like you, him, Calc84maniac (who wanted to write a similar tutorial back in 2006 or 2007) and Iambian (same) have people with slower learning capacitity in languages and visual people in mind when wanting to write a tutorial. The same wouldn't have happened to sgm/sigma on UTI (who wrote ASM In 28 days). I remember some stuff from him in reply to people saying they don't understand the tutorial that he felt the tutorial was explained as good as needed. Later he finally started writing a new one, but despite being slightly more explained, he said he won't bother explaining in further details if people don't get it and if someone don't understand a part of the tutorial then it's the person's problem. He did not say this like that but he pretty much implied it. It's good he wrote such tutorial, though, a great tutorial, even. I wonder if it got featured on ticalc.org because I think it deserves a feature if it isn't. It's just that some other people like you and Quigibo for example are more open-minded toward other people's differences
-
hmm i would love to learn asm if i could but imma gonna stick with basic for a long while first XD although ill gladly help read threw it and see what could be challenging/needing better wording XD
-
I've been doing assembly for a while now for a pretty decent amount of time. I think it is a great idea to have more help out there. You can never have enough examples/documentation out there to learn from. I constantly find myself learning something new every time I pick a project up again. We can always use some more great z80 projects out there. I am far from an expert on z80 so always like to see what else I can learn.
-
Alrighty then, I'll write the tutorials. This is the first lesson. I put it out this early because I would like some feedback. Please provide feedback; because this is the first time I'm doing this, my first few lessons are going to have bugs and might not even be the best they could be. As soon as I get enough feedback, I'll put tutorials in a seperate forum.
Specifically,
1. Did you understand the lesson?
2. How long did you take it to understand it? Did you only have to read it once, twice? Did you have to read it several times? Was it easy for you?
3. If you didn't understand this lesson, why?
4. Is there something you feel I'm missing that I should have explained?
5. Did you have fun?
6. Do you look forward to more lessons in the future?
-
I think the hardest part of learning asm is the shift in paradigm. In my opinion, someone with very little programming background will be able to learn the language and understand it better initially than someone who has exclusively programmed in higher level languages their whole lives. I remember the concept of flags, registers, unsigned arithmetic, bit shifting, etc. seemed so foreign to me when I was first learning. You never cover that stuff in high level. In my head I kept trying to make my code look and feel like the languages I was used to so then it would all be simple and I could just naturally pick it up. But you can't do that, its impossible. You miss all the concepts that are absolutely essential to do all the low level tasks which is the whole point.
You have to start with a very open mind. Your knowledge of how to ride a bike isn't going to help you much when you're trying to fly a helicopter. It took me about a whole summer to get the hang of it and it was almost a year before I could write a game with it.
-
I think the hardest part of learning asm is the shift in paradigm. In my opinion, someone with very little programming background will be able to learn the language and understand it better initially than someone who has exclusively programmed in higher level languages their whole lives. I remember the concept of flags, registers, unsigned arithmetic, bit shifting, etc. seemed so foreign to me when I was first learning. You never cover that stuff in high level. In my head I kept trying to make my code look and feel like the languages I was used to so then it would all be simple and I could just naturally pick it up. But you can't do that, its impossible. You miss all the concepts that are absolutely essential to do all the low level tasks which is the whole point.
You have to start with a very open mind. Your knowledge of how to ride a bike isn't going to help you much when you're trying to fly a helicopter. It took me about a whole summer to get the hang of it and it was almost a year before I could write a game with it.
Can you explain that? Are you saying I should not talk to people with the idea of Ti-Basic, assuming that they know that language? Otherwise, what do you mean?
-
I just printed out. I'll give the feedback ASAP!
-
I think the hardest part of learning asm is the shift in paradigm. In my opinion, someone with very little programming background will be able to learn the language and understand it better initially than someone who has exclusively programmed in higher level languages their whole lives. I remember the concept of flags, registers, unsigned arithmetic, bit shifting, etc. seemed so foreign to me when I was first learning. You never cover that stuff in high level. In my head I kept trying to make my code look and feel like the languages I was used to so then it would all be simple and I could just naturally pick it up. But you can't do that, its impossible. You miss all the concepts that are absolutely essential to do all the low level tasks which is the whole point.
You have to start with a very open mind. Your knowledge of how to ride a bike isn't going to help you much when you're trying to fly a helicopter. It took me about a whole summer to get the hang of it and it was almost a year before I could write a game with it.
Can you explain that? Are you saying I should not talk to people with the idea of Ti-Basic, assuming that they know that language? Otherwise, what do you mean?
Yeah that's the general suggestion I'm making. It wasn't in response to the lesson you posted, I haven't read it yet, I was just giving my personal experience.
-
I think the hardest part of learning asm is the shift in paradigm. In my opinion, someone with very little programming background will be able to learn the language and understand it better initially than someone who has exclusively programmed in higher level languages their whole lives. I remember the concept of flags, registers, unsigned arithmetic, bit shifting, etc. seemed so foreign to me when I was first learning. You never cover that stuff in high level. In my head I kept trying to make my code look and feel like the languages I was used to so then it would all be simple and I could just naturally pick it up. But you can't do that, its impossible. You miss all the concepts that are absolutely essential to do all the low level tasks which is the whole point.
You have to start with a very open mind. Your knowledge of how to ride a bike isn't going to help you much when you're trying to fly a helicopter. It took me about a whole summer to get the hang of it and it was almost a year before I could write a game with it.
Can you explain that? Are you saying I should not talk to people with the idea of Ti-Basic, assuming that they know that language? Otherwise, what do you mean?
Yeah its just a general suggestion I'm making. It wasn't in response to the lesson you posted, I haven't read it yet, I was just giving my personal experience.
Thanks for explaining! Now that I understand, I appreciate the suggestion.
-
I'll give some feedback, if I'm allowed to :P
The first lesson is a great introduction. Quick revision of binary, introduction to variables etc etc. The only thing that seemed a bit strange to me, was the introduction to sprites. IMO it's better to put that in the appropriate context. (graphics lessons)
-
I'll give some feedback, if I'm allowed to :P
The first lesson is a great introduction. Quick revision of binary, introduction to variables etc etc. The only thing that seemed a bit strange to me, was the introduction to sprites. IMO it's better to put that in the appropriate context. (graphics lessons)
Agreed. Is there another example I can use describing the importance of understand binary numbers so I can avoid the sprite example? (It wasn't an introduction to sprites as much as describing the importance of understanding binary) Like I said, I'm polling for all this feedback so I can right better lessons in the feature
-
you could always just do a small reference to sprites in lesson 1 for binary, but keep the details later.
In overall it seems quite well written and I like the different approach.
-
Maybe you could just state that 1 is 'current' and 0 is 'no current', then explain that there are no 'other' possibilities, and therefore, numbers must be composed of 0 and 1.
Also, you could introduce hexadecimal as well, and add arithmetic exercises for both.
Just suggesting. Probably better to wait for someone else to comment, since I'm biased.
-
ASM is fun I toke a class and learn MIPS asm. Working with it taught me how much overhead there is to common operations. I think every programmer at one time or another should write a call stack with frame pointer, a dynamic memory manager and some simple programs just to understand the costs of the operations you do all the time. ;)
-
I think every programmer at one time or another should write a call stack with frame pointer, a dynamic memory manager and some simple programs just to understand the costs of the operations you do all the time.
Please, don't scare away the customers I'm trying to attract! :D
-
Yeah everyone has to understand not everyone can learn the same way, else it is pretty narrow-minded IMHO.
-
I think this is an awesome idea Hot Dog! ;D
I really like the idea, as I have a mildly good grasp of the basics of Asm, but I don't consider that I know it or feel comfortable using it. I really would like a guide like this, and would read all of it. I'm downloading lesson one now. Thanks Hot Dog! ;D
-
Maybe you could just state that 1 is 'current' and 0 is 'no current', then explain that there are no 'other' possibilities, and therefore, numbers must be composed of 0 and 1.
Also, you could introduce hexadecimal as well, and add arithmetic exercises for both.
-I agree, I say you show some of the arithmetic things that you can do. Keep them brief and simple. Describe what the 1 and 0 represent and that they can correspond to graphics, but you'll touch on that later. I would say you devote a lesson discussing hexadecimal, decimal, binary conversion and perhaps the reasoning behind why you would use such things.
-
Yes, a lesson about number system is needed in an assembly tutorial.
And one thing they rarely tell is why hexadecimal is used. Decimal is used because it is the number system common people learn and know, this is somewhat obvious. Binary because that it is the number system that a computer uses, this one too. (memory and registers are just lots of bits with 0's or 1's)
But hexadecimal is used, in my opinion (and no one told me so correct me or complete me if it needs), because provide a short way to represent 8-bits with 1 digit and is easy to convert between hexadecimal and binary. And not hard either to convert to decimal.
I wish less teachers, tutorials or books say you require to learn something because you need to what is next. Knowing why are you learning something, can be important to really understand what you are learning and keep you motivated.
-
Describe what the 1 and 0 represent and that they can correspond to graphics, but you'll touch on that later. I would say you devote a lesson discussing hexadecimal, decimal, binary conversion and perhaps the reasoning behind why you would use such things.
Sounds good, will do
I wish less teachers, tutorials or books say you require to learn something because you need to what is next. Knowing why are you learning something, can be important to really understand what you are learning and keep you motivated.
I would say you devote a lesson discussing hexadecimal, decimal, binary conversion and perhaps the reasoning behind why you would use such things.
Which gets me asking: why is knowing conversion important? I know how to convert from binary to decimal to hexadecimal, and yet I've rarely done it without a calculator.
Also, assuming it is necessary, can it be done in a later lesson?
-
Which gets me asking: why is knowing conversion important? I know how to convert from binary to decimal to hexadecimal, and yet I've rarely done it without a calculator.
Also, assuming it is necessary, can it be done in a later lesson?
To convert numbers greater than 255 I always use a calculator. But is useful to convert quickly to understand code like this from mind:
and $80 ; this bit masking is seen a bit
But this is also the kind of things you memorize with use. After a while you know $8 is %1000 which means the bit 3 is set.
So, yes, conversion is not that important. But is good to know why we are "complicating" using hexadecimal and binary instead of just decimal all the time.
-
So far I haven't gotten any reviews from people who have never done ASM before. Although what the lesson teaches is important, that's not my biggest concern. My biggest concern is if the lesson is understandable or not.
-
It seems pretty understandable so far. It also seems to be a good starting place... this is from someone who died after trying anything of other asm tutorials...
-
Yeah I read it through once, and I understood. It was also very funny, and engaging. Well, I might be a bit biased about understanding them at once, because I had some knowledge about binary number :P
But I can't wait for second lesson :)
-
Thanks for all the feedback people! Here's what I'll be doing:
1. I'll add the information about 1s and 0s being signals
2. I'm adding information about how to use Windows to convert from Binary to Decimal. I forgot to do that, but I feel it's necessary. I will also mention that almost anything you can do with Decimal numbers (such as add and multiply), you can do with binary numbers
3. I will save Hexadecimal numbers for another lesson, and I will put binary/decimal/hexidecimal conversion in an appendix.
4. I will start a new forum with this lesson, and lesson 2 will appear sometime this week. Please continue helping me with feedback, so that when the lessons are in their final form, they will be good enough and easy enough to actually submit to a site such as ticlac.org.
-
Which gets me asking: why is knowing conversion important? I know how to convert from binary to decimal to hexadecimal, and yet I've rarely done it without a calculator.
I think it's very important to get how these number systems work. I also do that kind of work with a calculator now, but IMO it's necessary to understand what you're dealing with. It's like owning a fish store without knowing what fish you're actually selling.
-
Even thought I don't plan to learn ASM in the future, I may still check your guide from time to time and see if there aren't stuff that needs clarifying.
-
Even thought I don't plan to learn ASM in the future, I may still check your guide from time to time and see if there aren't stuff that needs clarifying.
Any feedback is welcome. If the tutorials in their final form are a success here, I hope to put them on Ticalc.org
-
My main reson for never learning asm was that it was a pain to set up the environments to do so. I can work with C fairly decently, and I don't think the code would give me much trouble, but the hours it takes to set up just take too long (talking from DS development here) and the command line editors have little or no documentation.
I'll probably check out the guide. Maybe I could get started now!
-
oh that reminds me Hot Dog: in the tutorial it's important to help the person get started. Guide him into how to setup an ASM environment for his needs. He can use, for example, a TASM one, Spasm, Latenite (?), etc and describe the advantages/disadvantages of them.
-
And the new ASM development tool that SirCmpwn was making, it seemed pretty cool. and the one that Eeems was making, idk if it's working or not tho.
-
oh that reminds me Hot Dog: in the tutorial it's important to help the person get started. Guide him into how to setup an ASM environment for his needs. He can use, for example, a TASM one, Spasm, Latenite (?), etc and describe the advantages/disadvantages of them.
I planned on that for a later tutorial, when the person actually starts programming...the advantage is that when the person sets up the ASM program, he knows why. Are there any disadvantages, aka any reasons I should have it in the first?
-
Yeah, I guess you are right, and the person should understand the basic idea first, but what I think is that when you actually start providing examples and snippets of codes, the readers might want to try out, but don't know how to make them, like the usual hello world program. So I think introducing the ASM environment fairly early in the tutorial is good.
-
Yeah, I guess you are right, and the person should understand the basic idea first, but what I think is that when you actually start providing examples and snippets of codes, the readers might want to try out, but don't know how to make them, like the usual hello world program. So I think introducing the ASM environment fairly early in the tutorial is good.
Good point. When programming actually starts in Tutorial 4, I'll bring up the development environments.
-
I just read the first lesson. Great job! I knew what was covered in this installment, so I can't say how good it was at teaching it, but it was very well written. I can't wait to read future issues! ;D
-
I think that you should recommend a specific IDE for beginners, mention others, but mainly focus on the recommended one to avoid confusion. Just my opinion, but I think it will make it easier to understand.
-
I would definitely like to learn and start using Asm, but the problem I encounter is that the present tutorials assume all users have Windows and provide links to only compilers, assemblers, and other utilities for Windows. I, unfortunately, have a mac.
-
You may also want to mention the few ways to code ASM on calc like OTBP assembler, but that for now such method is not really convenient. In the case where SirCmpwn (where did he go, actually???) would finish Mosaic before your tutorial, you could also mention it. But mention that to get the full potential of ASM in terms of file size and libraries, it's recommended that you use a computer IDE.
-
Will was working on wabbitcode for the mac. I have a version if you like since the RevSoft is no longer up. We will be bringing it back up this summer though with some new changes. So I'll keep you all posted.
-
The issue with Mac platform is that it has a much smaller audience than Linux and Windows when it comes to developers, as Macs are generally used for multimedia. Because of this, very few programmers bother making IDEs for Mac since they feel the demand isn't high enough. This is why it took so long before a 83+ emu comes out for Mac. I think there aren't even any 89 one for this platform. It kinda sucks Mac users are singled out, though, when it comes to calc dev. I guess the only real solution in short term is to switch to Windows or Linux x.x
-
When I mean working...I mean there where versions of it at RevSoft. It does work pretty well. It incorporated wabbitemu and spasm all into one package. But I definitely hear you on the Windows/Linux thing. However for the sake of the lessons, I would just mention these few different IDEs out there. But let them know that any text editor will work as long as you save the file with the proper extension. Focus mainly from that point on.
-
Nice I didn't knew there were versions available. For Revsoft did you ever thought about starting a temporary board elsewhere with the site until the old one is back up? It might be good if some of the files were available again and also a lot of people keep asking me if Revsoft went under in #omnimaga
-
I would definitely like to learn and start using Asm, but the problem I encounter is that the present tutorials assume all users have Windows and provide links to only compilers, assemblers, and other utilities for Windows. I, unfortunately, have a mac.
You can still use the info from the tutorials, of course, to use a dev interface for mac or for the calculator
-
spasm compiles on most platforms iirc.
-
Well, I'll check it out. Plus, I now have CrossOver (mac).
-
spasm compiles on most platforms iirc.
Actually, that's the one I'll be referring to/using in the tutorials, even though I'll list some other ones
-
spasm compiles on most platforms iirc.
Actually, that's the one I'll be referring to/using in the tutorials, even though I'll list some other ones
Please provide in-tutorial links to any sources you recommend. It makes it a lot easier.
-
spasm compiles on most platforms iirc.
Actually, that's the one I'll be referring to/using in the tutorials, even though I'll list some other ones
Please provide in-tutorial links to any sources you recommend. It makes it a lot easier.
I'll be doing that, and when I provide a .zip that has all the tutorials in it, I'll include spasm in the .zip as well
-
you may want to ask Spencer permission before redistributing Spasm, though. From what I remember, he's pretty strict on redistributing their files. I had to ask Buckeye permission to include WabbitEmu here and it was only a specific version I was allowed to put online.
-
Where can I ask him?
-
Calc84maniac regulary talk to him on AIM. Maybe he got his e-mail address.
-
IIRC, Spencer expects you to either include the Spasm source code with the release or link to the revsoft SVN location of the source. Don't quote me on it though :P
-
I think that ASM was a challenge to learn, but after looking at the source codes from other people, I understood how to do it.
-
I think I am getting a little bit how some of the memory stuff is layed out on the calc and how numbers are stored, thanks to Axe language, but last time I learned ASM, I had an hard time understanding registers and seeing all those push, pop, ld, etc in ASM code confuses me (I get confused at BASIC code when there are several If statements in a row and lot of variable storage x.x)