SX-Key IDE Enhancements

Tony Leyland

Hi,

There has been a few posts asking about how to detect the space occupied by a program.

How about having a window in the SX Key IDE that shows program use on all Pages like in this attahment ?

Thanks
Tony

Tony Leyland

There seems to be something wrong with the attachment so I'll try again...

Tony Leyland

BTW, the dotted line represents the boundary to the upper part of the page, above which represents
the area beyond the limit of the CALL instruction.

Tony

KenM

Viewing a graphical representation would be nice.

Please educate me.....is viewing the list file in essence the same thing, at least for the first and second half of each page?

Indeed, a graphical view would be nice

PJMonty

I'm just curious, asside from the "gee whiz" factor of seeing code space usage, how often has not knowing code usage been a problem? I'm not referring to "it would be nice to know when I'm working" stuff, but situations where not knowing the code space usage has caused you actual problems in trying to get a project done?

Given that the SX28 (the more commonly used chip) has a modest 2K of program space, and that most people use the SX for small projects where either ease of programming/debugging or a super fast chip are more important factors than lots of code space, I'm just curious what sort of stories are out there about the time someone got burned because they didn't know how much space was left in the chip.

Thanks, PeterM

Guenther Daubach

Hi all,

I think the more critical problem is that you try to squeeze put too many instructions in one page causing that the generated code exdeeds the page boundary.

The Assembler can nicely generate an error in such cases, when you place a nop instruction at the very beginning of each page until you put some other code in that page.

Like

org $200
nop

org $400
nop

etc.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Greetings from Germany,

G

James Newton

I never have to worry about pages... my macros just manage them automatically. And for people who don't grok macros, Gunthers method is perfectly usable. I think this is an issue that should be corrected by education or a better code template.

I would rather see other types of code profile tools such as what subroutine is sucking up all the cycles, or the ability to parse macro parameter strings.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
---
James Newton, Host of SXList.com
james@sxlist.com 1-619-652-0593 fax:1-208-279-8767
SX FAQ / Code / Tutorials / Documentation:
http://www.sxlist.com Pick faster!

KenM

PJMonty said...
I'm just curious, asside from the "gee whiz" factor of seeing code space usage, how often has not knowing code usage been a problem?

Never for me.

KenM

But I will soon 'grok' macros,

Ken

PJMonty

James,

The master of macros chimes in! You are some kind of freak, my friend. I think you're about 90% of the way towards having a mid/high level language with all the macros you've written.

Thanks, PeterM

James Newton

PJMonty said...
·I think you're about 90% of the way towards having a mid/high level language with all the macros you've written.

Getting there...

...its all in the newsletter. Next issue is comming out soon.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
---
James Newton, Host of SXList.com
james@sxlist.com 1-619-652-0593 fax:1-208-279-8767
SX FAQ / Code / Tutorials / Documentation:
http://www.sxlist.com Pick faster!

Michael Chadwick

I'm not sure of the truth of this, but I read somewhere that the language SNOBOL was done entirely with macros.