0 Members and 2 Guests are viewing this topic.
push hl ;EVALUATE EXPRESSION HERE ex (sp),hl pop bcloop: push bc ;LOOP BODY HERE pop bc dec bc ld a,b or c jr nz,loop
push hl ;EVALUATE EXPRESSION HERE dec hl inc l inc h ld b,l ld c,h pop hlloop: push bc ;LOOP BODY HERE pop bc djnz loop dec c jr nz,loop
Quote from: Deep Thought on April 09, 2011, 08:31:16 pmQuote from: ztrumpet on April 09, 2011, 05:15:43 pmCan we have a feature like "Zeros()," but for any data. For instance, something like this:Command(1,12) would be the same as [010101010101010101010101]Command([56],4) would be the same as [56565656]Command(127,6) would be the same as Data(127,127,127,127,127,127)Potentially, this command could even be used for repeating sets of data. For instance:Command([010203],12) would be the same as [010203010203010203010203]Command("Text"[00],15) would be the same as "Text"[00]"Text"[00]"Text"[00]So, what do you think? Could this be a command? I think it's a good idea, to avoid situations like this. I really like that idea. What about changing Zeros( (det() to something more universal?I would suggest changing the token replacement to Block(). Feeding 1 argument would create a block of the specified size filled with zeroes. Feeding 2 arguments would create a block of the specified size filled with a specified value. Maybe you could even add a Block()r command for creating a block filled with a specified word while you're at it, although this probably isn't as necessary as a normal byte-filling block command.
Quote from: ztrumpet on April 09, 2011, 05:15:43 pmCan we have a feature like "Zeros()," but for any data. For instance, something like this:Command(1,12) would be the same as [010101010101010101010101]Command([56],4) would be the same as [56565656]Command(127,6) would be the same as Data(127,127,127,127,127,127)Potentially, this command could even be used for repeating sets of data. For instance:Command([010203],12) would be the same as [010203010203010203010203]Command("Text"[00],15) would be the same as "Text"[00]"Text"[00]"Text"[00]So, what do you think? Could this be a command? I think it's a good idea, to avoid situations like this. I really like that idea. What about changing Zeros( (det() to something more universal?
Can we have a feature like "Zeros()," but for any data. For instance, something like this:Command(1,12) would be the same as [010101010101010101010101]Command([56],4) would be the same as [56565656]Command(127,6) would be the same as Data(127,127,127,127,127,127)Potentially, this command could even be used for repeating sets of data. For instance:Command([010203],12) would be the same as [010203010203010203010203]Command("Text"[00],15) would be the same as "Text"[00]"Text"[00]"Text"[00]So, what do you think? Could this be a command? I think it's a good idea, to avoid situations like this.
Quigibo, perhaps implement B_CALL(_DelRes) somehow? It would probably have to be manually called by the user at their discretion, but it would be useful for people who want to use L2. And for that matter, B_CALL(_DelRes) should probably be a part of the interrupt setup, which it currently is not.
In other news, Frey continues kicking unprecedented levels of ass.
Wasn't Fill just changed to do exactly that?