??? 08/14/05 22:21 Read: times |
#99384 - command interpreter Responding to: ???'s previous message |
Basically I want to define some commands "in my assembly app" and have them run/execute whatever you want to call it.
I don't think I need the ability to "define" commands on the fly, (would make it nice to fix things to get it right, but not a requirement. Plus they would probably get wiped out on a power down.). As I'm thinking about this I'm thinking only 1 parameter after the command. Before I posted this question I'd been thinking about switching to basic-51 just because i know it has some string handling capabilities, but I want to actually try and keep it assembly language. Actually since I'm a beginner I'm not sure I could decipher the basic-51 source, especially if its in 'C'. I do have a larger project that I'm going to use this in and I guess I'm just going through the small steps first, plus trying to learn assembly along the way. |
Topic | Author | Date |
command interpreter | 01/01/70 00:00 | |
What do you mean by 'command intepreter' | 01/01/70 00:00 | |
command interpreter | 01/01/70 00:00 | |
Nope | 01/01/70 00:00 | |
my command interpreter: | 01/01/70 00:00 | |
your command interpreter | 01/01/70 00:00 | |
Re: your command interpreter | 01/01/70 00:00 | |
command interpreter | 01/01/70 00:00 | |
SBCMON | 01/01/70 00:00 | |
Re: SBCMON | 01/01/70 00:00 | |
Single-letter commands | 01/01/70 00:00 | |
You Need a debugger | 01/01/70 00:00 | |
the ultimate learning tool is an ICE (eq | 01/01/70 00:00 | |
Yes, i done it | 01/01/70 00:00 | |
commands | 01/01/70 00:00 | |
How to get the parameters![]() | 01/01/70 00:00 |