BxbAsm

[jcfuller]

Steve,
  I found the problem.
 It was line endings. When I cut and pasted test, test2 from README.TXT they were saved with linux line endings LF, but the Sub1 and ucase were used as is and they had CRLF. When save with just LF they converted just fine.

James

[jcfuller]

Steve,
  In your asm output I believe you need to replace the ret in your Main proc to:

Code: [Select]

invoke exit,0

I added a proto in bxb.inc

Code: [Select]

exit proto c :DWORD

The ret caused a gpf on Linux. The invoke exit,0 appears to work fine on windows?

Conrary to what I though there is no _getch() on Linux. I looked in the ubx code and found how it was done,
and wrote a library that I linked to the demos and it worked fine.

I see you have a couple console routines in bxblib. I do believe that is the way to go.
Put all your routines in the library and I can help out by converting them to linux compatable code.

Go ahead and add your console routines back in and I'll see what I can do with them on Linux.


James

[SteveA]

It was line endings.
...but the Sub1 and ucase were used as is and they had CRLF.
When save with just LF they converted just fine.

This is good to know.
I wonder how I could fix that ?

In your asm output I believe you need to replace the ret in your Main proc to:

You are right, it should be "exit, 0"
It was originally "ExitProcess", which is a win32 function.
I was playing around with it and never finished it.
In old dos programs you could use "ret".

[SteveA]

What do you want to replace "_getch" with ?

[jcfuller]

What do you want to replace "_getch" with ?

Nothing. It's working fine now that I added a Linux substitute and link it in during jwasm compiling / linking of the asm source.

James

[SteveA]

Nothing. It's working fine now that I added a Linux substitute and link it in during jwasm compiling / linking of the asm source.

Okay.

About the console mode functions:
if I understand correctly, you want me to reactivate them...?

For the most part, I didn't delete them, I just commented them out.
That's what all the comment warnings were about, yesterday.
So, you want me to uncomment them...?

[jcfuller]

 I tried to uncomment just CLS because I wanted to test code I had added but I got a gpf on translation from bas -> asm

Code: [Select]

REM  test.bas version 1
CLS
PRINT "hello world!"

END


I figured I must have missed something??

On another front:

  In order to compile test 5 from BXBASIC.txt I needed to compile BxbLib.c.
Was there a reason for _stdcall? I removed it and used proto c when adding the Float2Str2 proto to bxb.inc.
Compiled and worked fine. On linux the conversion routine is gcvt.

James

[SteveA]

In order to compile test 5 from BXBASIC.txt I needed to compile BxbLib.c.
Was there a reason for _stdcall?

No, that's a windows thing.
They should be normal C calls.

I removed it and used proto c when adding the Float2Str2 proto to bxb.inc.
Compiled and worked fine. On linux the conversion routine is gcvt.

Right.

[jcfuller]

Steve,
  I found my error. I missed uncommenting  in Input.c

James

[SteveA]

Bxblib.inc, in /../Include, needs to be changed:

Here is how it reads:

Code: [Select]

testlib      proto stdcall
value2strng  proto stdcall :REAL8, :SBYTE
FloatToStr2  proto stdcall :REAL8, :PTR DWORD
ClearScreen  proto stdcall
locate       proto stdcall :DWORD, :DWORD
StrToFloat   proto stdcall :PTR DWORD, : PTR QWORD

remove all "stdcall".

[SteveA]

When uncommenting, check these, in this order:

1)  Input.c, --> get_byte()

2)  Bxbasm.c --> parser()

3)  prototype.h  --> any/all

4)  the functions themselves, in whatever filename.c
     prototype.h lists file name.

[jcfuller]

Steve,
  I would like to suggest a different approach for os dependent items.
Instead of outputing asm to be compiled use a precompiled library and link to it.
Case in point cls.
I created an object file with this code

Code: [Select]

#include <stdio.h>
#include <curses.h>
// clear console screen linux
char    ESC [2]={27,0};  // Escape
void cls(void);
void cls(void)
{
printf("%s%s%s%s",ESC,"[2J",ESC,"[H");
}
compiled with gcc -c cls.c

I then added it to a library with ar:

ar cr libbxbasm.a cls.o

I then linked this library when compiling test1.asm with this script:

Code: [Select]

~/jwasm/jwasm -elf -zcw -Fo=$1.o $1.asm
gcc -s -nostartfiles -o $1 $1.o /home/james/bxbasmx/bxblib/BxbLib.o -L/home/james/bxbasmx/bxblib -lbxbasm


Your console routines seem to be in spread out in more than one file. Your Do_color is in AVars.c while Do_locate is in AFunc.
Can these be moved to individual files, compiled, then added to a static library?
James

[SteveA]

  I would like to suggest a different approach for os dependent items.
Instead of outputing asm to be compiled use a precompiled library and link to it.

I think that is a great idea.

Your console routines seem to be in spread out in more than one file.
Your Do_color is in AVars.c while Do_locate is in AFunc.
Can these be moved to individual files, compiled, then added to a static library?

Yes,
I previously wasn't too concerned with where they ended up.
Okay, I'll gather up all the win32/console functions and put them in a seperate file.
Would you suggest a seperate file or would you prefer a seperate LIB ?
Like: console.c or console.lib ?

[jcfuller]

Steve,
  To keep it as granular as possible put each func in a file by itself and compile them separately. Combine the obj files to create a library. That will also will help me on the Linux side to see just what needs to be supplied.

James

[SteveA]

Hey james,
were you able to get any of the deleted functions working ?

Do the normal C library functions seem to be working okay ?