On Wednesday 22 September 2004 16:19, Spiro Trikaliotis wrote: > I tend to disagree. IMHO, the memory layout is not that much platform > dependant, but project-dependant. I can put the char set wherever I like > it. Thus, any such system-given constant could be wrong. > > I think a macro (or even a function) which converts a memory location > into the right bits to put into the register would be much more portable > than such a constant. With this, a constant which describes where the > character sets for lower and uppercase can be found would make much more > sense. > > If I still need such a constant as you describe, I can define it myself, > can't I? mmmh well, if you consider user-defined character sets in that equatation, its getting somewhat messy indeed.... imho you are totally on your own with that kinda stuff, and the support libraries might not support it. however, if a macro could be made that takes the location of an upper- and lowercase character as an input, and which returns the proper value for vic+0x18 depending on the selected character set the whole thing would be even consistant for user-defined charsets (which is not bad ofcourse, just imho not necessary). however dont forget that you will need a second macro that returns the vic-bank (0xdd00 on a c64) then. also if this would be done, there should be constants that define the location of the system charactersets in memory. gpz ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Wed Sep 22 16:30:15 2004
This archive was generated by hypermail 2.1.8 : 2004-09-22 16:30:23 CEST