Turbo Pascal PopolonY2k's Framework

Continuing the discussion about an issue found by rolandve when he was trying to using some CONIO.PAS functions/procedures in some European MSX like NMS 8250.
Today I started debugging the CONIO.PAS functions/procedures and I realized that this issue is result of an old code refactoring which I made several years ago.

I was used to use Constants to describe some MSX system variables and to access these system variables I used a code like :

Var regs : TRegs;
Const EXPTBL = $FCC1;

Begin
regs.IY := Mem[EXPTBL];
...(rest of code)
End;

But after the code refactoring I changed to an absolute variable assignment, used in Turbo Pascal, like below:

Var      regs : TRegs;
           EXPTBL : Byte Absolute $FCC1;

Begin
  regs.IY := Mem[EXPTBL];
  ...(rest of code)
End;

But I forgot of to change the way to access this memory area from :

    regs.IY := Mem[EXPTBL];

to

  regs.IY := EXPTBL;

So I will post in the next message, the fixes for all affected functions.

Soon, I'll commit this changed module and I'll post the new URL SVN address here.

[]'s
PopolonY2k

Yup, it compiles, doesn't crash and after modifying my code I get output.
Without a _GotoXY() to start with, WriteLn() doesn't generate output, because X,Y are set to 0 in _ClrScr(). Is there a reason X,Y in _ClrScr() are initialised at 0,0? in conio.pas?

After OpenDirectTextMode(), WriteLn() add's 2 character after each line of text (CRLF)? A note symbol and an inverse coloured C. Is this by design? If I skip the OpenDIrectTextMode() these characters are not added.

PROGRAM MSXDOS;

{$I inc\types.pas}
{$I inc\dvram.pas}
{$I inc\msxbios.pas}
{$I inc\conio.pas}

Var
	scrHandle : TOutputHandle;
Begin
	OpenDirectTextMode(scrHandle);
	_ClrScr;
	_GotoXY(1,1);
	Writeln('ABCDEFGH');
	CloseDirectTextMode(scrHandle);
END.

@AxelStone: when you say TP 3.3, you are refering to MSX TP 3.3? executing and compiling in a MSX? or crosscompiler with TP 3.3 for MSDOS with some command line compiler to generate MSX code?

You're right, this is a bug and now is fixed in the project's SVN repository. Please check the new CONIO.PAS revision at https://sourceforge.net/p/oldskooltech/code/HEAD/tree/msx/tr...

In fact OpenDirectTextMode changes the default character printing handler to a new one implemented in DVRAM .PAS (Check the Procedure DirectWrite( chChar : Char ) in DVRAM.PAS). This procedure is much faster than the original character handling procedure, which in fact uses the BDOS character/string output calls. These BDOS functions are tooooooo slow functions.
My DirectWrite original implementation was not considering the CR/LF character handling, but after your report I decided to implement this feature and now it is working with CR/LF, skipping lines when necessary, so please check the new revision for DVRAM.PAS here https://sourceforge.net/p/oldskooltech/code/HEAD/tree/msx/tr...

Just a warning, working with Write/WriteLn in direct text mode (using OpenDirectTextMode), the text won't be scrolled when it reaches the borders of the screen. This is "by design", because I don't want to put a lot of code that could cause some overhead in the DirectWrite function, that is a very fast character handling procedure.
When you can, please compare displaying a big amount of text in the screen using Write/WriteLn without activating the direct text mode (through OpenDirectTextMode procedure) and after using the same Write/WriteLn with the direct text mode working through OpenDirectTextMode.

[]'s
PopolonY2k

htdreams, in fact my library and Kari's library work perfectly in the original Turbo Pascal 3.0b from Borland too, so this compiler is another option to use these libraries.

[]'s
PopolonY2k