Search found 234 matches
- Tue Jun 09, 2020 6:29 am
- Forum: Features
- Topic: Menus file accept comment line
- Replies: 3
- Views: 8986
Menus file accept comment line
Rsrc/Menus.odc file does not accept comment lines, it's inconvenient when we customize the menu; they are menu configuration files actually. in linux ,the configuration file accepts comments : # comments here a small patch has made to accept comment line,StdMemuTool.Scan PROCEDURE Scan (VAR s: TextM...
- Tue Jun 09, 2020 6:15 am
- Forum: Features
- Topic: Shotcut improved
- Replies: 2
- Views: 8120
Re: Shotcut improved
Sorry, StdMenuTool.Item must be patched: luowy
Code: Select all
...
IF s.type = string THEN
IF s.len < 16(*8*) THEN shortcut := s.string$
ELSE Error(s, "string too long")
END
ELSE Error(s, "string expected")
END;
...
- Mon Jun 08, 2020 10:28 pm
- Forum: Features
- Topic: Shotcut improved
- Replies: 2
- Views: 8120
Shotcut improved
I have completed the fully functional shortcut keys, which can use all the keys as shotcuts. currently, some keys can't be used by shortcut: e.g "ctrl+/" "ctrl+-" "ctrl+ Insert" ... I made some improvements to this; StdDialog.Item Item* = POINTER TO EXTENSIBLE RECORD ne...
- Mon Jun 08, 2020 4:56 am
- Forum: Resolved (Bugs)
- Topic: issue-#207 Compiler TRAPs with simple CONST expression
- Replies: 11
- Views: 13472
Re: issue-#207 Compiler TRAPs with simple CONST expression
in a squence code block a1: record last item which AX loaded from ; a2: record last item which AX stroed to; a1,a2 used for elimating redundant code of moving to or from AX; detail can be found in DevCPL486.GenMov; if current code action changed AX, it should reset a1,a2; but your fix code do not pr...
- Sun Jun 07, 2020 10:41 am
- Forum: Resolved (Bugs)
- Topic: issue-#207 Compiler TRAPs with simple CONST expression
- Replies: 11
- Views: 13472
Re: issue-#207 Compiler TRAPs with simple CONST expression
my typo problem:
I checked code with
it should be as you provided;
I agree with your code!
luowy
I checked code with
Code: Select all
DevCPL486.MakeConst(c, 1, Bool);
it should be
Code: Select all
DevCPL486.MakeConst(x, 1, Bool);
I agree with your code!
luowy
- Sun Jun 07, 2020 2:49 am
- Forum: Resolved (Bugs)
- Topic: issue-#207 Compiler TRAPs with simple CONST expression
- Replies: 11
- Views: 13472
Re: issue-#207 Compiler TRAPs with simple CONST expression
let's check the decoding of this statement : CONST f = FALSE; VAR b: BOOLEAN; b := (b OR ~f) & f; (* b == FALSE *) with "DevCPL486.GenMove(c, x);" 63190037: 80 7D FF 00 CMP BYTE [EBP-1], 0 6319003B: 0F 85 00 00 00 00 JNZ 0 (63190041H) 63190041: 30 C0 XOR AL, AL 63190043: 88 45 FF MOV [...
- Sat Jun 06, 2020 12:58 pm
- Forum: Resolved (Bugs)
- Topic: issue-#207 Compiler TRAPs with simple CONST expression
- Replies: 11
- Views: 13472
Re: issue-#207 Compiler TRAPs with simple CONST expression
DevCPC486.LoadCond CODE: SELECT ALL IF y.offset >= 0 THEN DevCPL486.GenSetCC(y.offset, x) ELSIF y.offset = ccAlways THEN DevCPL486.MakeConst(x, 1, Bool) ELSIF y.offset = ccNever THEN DevCPL486.MakeConst(x, 0, Bool) ELSE HALT(100) END What do you think? ooh, it's not ok, but it will be ok if re-add ...
- Fri Nov 29, 2019 10:51 am
- Forum: Bugs
- Topic: issue-#204 SYSTEM.BIT bug
- Replies: 17
- Views: 21897
Re: issue-#204 SYSTEM.BIT bug
A2 new OberonReport has it Document
Code: Select all
12.2.1 BIT Manipulation
Function Argument Types Result Type Description
BIT(adr,n) adr: ADDRESS;n: INTEGER BOOLEAN Returns TRUE if bit n at adr is set, FALSE otherwise
- Tue Nov 26, 2019 6:09 am
- Forum: Bugs
- Topic: issue-#204 SYSTEM.BIT bug
- Replies: 17
- Views: 21897
Re: issue-#204 SYSTEM.BIT bug
According intel manual,I think we need to add this patch in DevCPB.StPar1 | bitfn: (*SYSTEM.BIT*) IF (x.class = Ntype) OR (x.class = Nproc) THEN err(126) ELSIF f IN intSet THEN IF (x.class = Nconst) THEN (*<<<*) IF (x.conval.intval > DevCPM.MaxSet) THEN n :=x.conval.intval; x.conval.intval := n MOD ...
- Sat Nov 23, 2019 12:57 pm
- Forum: Bugs
- Topic: issue-#204 SYSTEM.BIT bug
- Replies: 17
- Views: 21897
Re: SYSTEM.BIT bug
yes, your code is more elegant and correct!Josef Templ wrote:The resulting procudure would look like this
luowy