« BYTE "PIOU!"+128 »
« BYTE "GLOIRE !" OR &80 »
In some cases, it could be convenient to apply the operator to each bytes. Possible?
Not yet! I'm not sure which syntax to choose.
In my opinion, the most obvious choice would be BYTE ("PIOU!")+128. Another possibility could be that BYTE "PIOU!"+128 adds 128 to each byte, and BYTE "PIOU","!"+128 only to the last one.
But you maybe have better syntax in mind :)
I like the second option, but I'd rather introduce some more powerful mechanisms.
1/ Function.
If invoked on a string, applied on each byte separately.
FUN translate x
If x >= &20
return x - &1f
elif x = 0
return 0
else
!! error unexpected value < &20
end
ENDF
BYTE translate("PIOU!")
2/ Post-Processing.
Ability to invoke a RSX (or a 'plugin'?) to process all or part of the code.
Needed anyway for automatic compression.
RC4 available.
That should be it. Official version next week should be identical but including updated doc on disk.
For the next features I need to change some of the infrastructure. So don't expect anything new for some time. Thanks all.
RC5 is the real deal.
Todo before official release:
* Waiting for Hicks confirmation.
* Improving user guides online (I won't do that).
* Converting online guides to CPC files.
It's
ready.
Basically, or assemblerally, that's the exact RC5 version + guides on the disquette.
Hardcore users may wait a few days for
Erratic Endeavour Beta 1.Hardcore users may want to check
Erratic Endeavour Beta 2.
I have to pause. So, as Wilhelm Reich used to say in Shanghai,
« Be the change you wanna see in Orgams. »
In the other hand, don't forget to vote for your favorite features-to-be.
To whom it may concern, I've split the 'mon' source into four:
* monhelp: helpers routines (e.g. trans-ROM calls)
* monui: display-related routines.
* mon: monogams command themselves.
* trui: Trace UI.
It's never been easier to participate and add your own stuff.
New editor shortcut: CONTROL-%. Pretty handy if you ask me.
Ast has detected a bug (#E8, cannot BRK/ disassemble anymore) on EE beta (2 and 4).
Has everyone else tried this beta? Do you encounter this bug?
Due to bug #E8 and #EB, I do not recommend using EE beta 4.
The whole team is working diligently to propose a stable beta.
Thanks to Sid, IMPORT is on its way.
Read the grand design
here.
Simple users can give their thought on the planed label behavior:
import “player” ; look for player.o
import “3d” as _3d
play [...] ; local routine
call init ; // assemblage error: init exists in both imports
call player.init ; ok
call _3d.init ; ok
call play ; use local routine
call player.play
call get_psg ; ok, found uniquely in player
This is the opportunity to remind that everyone can contribute. If the perspective of update someone else's uncharted code holds you, do not worry. I can describe some small routines to write, in a brand new source, just using the interface of existing routines (like the firmware jumblock).
Poll! Multi-files edition, which shortcut to navigate between sources?
* Control-tab.
* Pro: same as in most browsers.
* Control-shift-left/right.
* Pro: coherent with "control-shift" combination to indicate multi-files command (e.g. control-shift-f: search in all files).
* Control-g + fuzzy search.
* Other?
Incoming: no more vertical alignement for operands.
; Before
ld a,3
inc b:inc c:inc d:inc e
inc a:ld l,a:ld h,2
; After
ld a,3
inc b:inc c:inc d:inc e
inc a:ld l,a:ld h,2
Rationale:
* Doesn't necessarily make sense.
* Slightly speeds up textual search.
* Makes more room, especially for trace in prevision of stack trace display.
Incoming? Extension du domaine des shortcuts.
E.g.
CTRL-O in monogams: open file
CTRL-B in editor: return to basic
Etc.
New feature: display call stack.
For the code:
call aa
ret
aa call bb
ret
bb BRK
You will see:
aa
bb
(and maybe some « ? »)
Mainly useful for tools and complex programs.
Incoming [trace]:
* U: Go up in the call stack (go to caller)
* D: Go down in the call stack (go to callee)
Page: 1 2