Register.Console.Echo still functional?

[Don_Kirby]

I've been trying, unsuccessfully, to turn off the console echo. Can someone verify that this function is working correctly? Using the code below, I get an echo in Hyperterminal where I shouldn't. I have verified that the echo feature in Hyperterminal is off.

Code: Select all

Sub Main()
	Do
		Register.Console.Echo = False
		Dim x as byte
		Console.Write("Type Something ")
		x = Console.Read
		Console.WriteLine("")
		Console.WriteLine("You entered " & Chr(X))
	Loop
End Sub

-Don

[dkinzer]

I've been trying, unsuccessfully, to turn off the console echo.

The code generated for setting Register.Console.Echo is incorrect. You can work around the problem by commenting out the existing code and adding the inline C code as follows:

Code: Select all

#c
    setBits((uint8_t *)&zxd + ZX_IO_FLAGS_OFST, IOF_CONSOLE_ECHO, ZX_FALSE);
#endc
'    Register.Console.Echo = False 

The code generated for reading Register.Console.Echo in also faulty. Replacement code for it, however, is a bit more complicated. Let me know if you need it, too.

[Don_Kirby]

Is this a native mode specific problem?


-Don

[dkinzer]

Is this a native mode specific problem?

Yes. The code generated for VM mode is correct.

[dkinzer]

Is this a native mode specific problem?

Perhaps a better interim solution is this:

Code: Select all

#if Option.TargetCode = "Native"
#c 
    setBits((uint8_t *)&zxd + ZX_IO_FLAGS_OFST, IOF_CONSOLE_ECHO, ZX_FALSE); 
#endc
#else
    Register.Console.Echo = False
#endif

[mikep]

Code: Select all

#c 
    setBits((uint8_t *)&zxd + ZX_IO_FLAGS_OFST, IOF_CONSOLE_ECHO, ZX_FALSE); 
#endc

Can you explain what some of these fields like ZX_FLAGS_OFST, ZX_FLAGS2_OFST, ZX_FLAGS3_OFST etc are for.

[Don_Kirby]

Code: Select all

#if Option.TargetCode = "Native"
#c 
    setBits((uint8_t *)&zxd + ZX_IO_FLAGS_OFST, IOF_CONSOLE_ECHO, ZX_FALSE); 
#endc
#else
    Register.Console.Echo = False
#endif

This returns the following:

RunSetup.bas Error: end-of-file reached with one or more open conditionals
RunSetup.bas Error: expected C statements and #endC following #C

-Don

[mikep]

Code: Select all

#if Option.TargetCode = "Native"
#c 
    setBits((uint8_t *)&zxd + ZX_IO_FLAGS_OFST, IOF_CONSOLE_ECHO, ZX_FALSE); 
#endc
#else
    Register.Console.Echo = False
#endif

This returns the following:

RunSetup.bas Error: end-of-file reached with one or more open conditionals
RunSetup.bas Error: expected C statements and #endC following #C

I just pasted the code into my test application and it compiles fine. I get your error messages if the #endc is not on a new line i.e.

Code: Select all

#if Option.TargetCode = "Native"
#c
setBits((uint8_t *)&zxd + ZX_IO_FLAGS_OFST, IOF_CONSOLE_ECHO, ZX_FALSE);#endc
#else
    Register.Console.Echo = False
#endif

[dkinzer]

Can you explain what some of these fields [...] are for.

Only in general terms. They are bit fields of an internal data structure that control various aspects of execution.

[Don_Kirby]

Mike, try that test again using indentation and see if you get the error. I'm big on keeping my indentation neat and tidy, so I indented the code after I pasted it. Removing the indentation made the errors go away.

-Don

[dkinzer]

try that test again using indentation and see if you get the error.

Currently, the #c, #endc, #asm, and #asm directives must begin in column 1. In retrospect, I don't know why they should not be allowed to be indented given that #if, #else, etc. are.

[Don_Kirby]

... I don't know why they should not be allowed to be indented given that #if, #else, etc. are.

Perhaps the intention was to make the C and ASM code segments stand out more in the code (by not being indented).

-Don

[dkinzer]

Currently, the #c, #endc, #asm, and #asm directives must begin in column 1.

Actually, the #c and #asm are currently allowed to be indented. The compiler has now been modified to allow the #endc and #endasm to be indented, too.