12-16-2004, 05:00 AM
Hi Victor, hi @ll,
regarding data types, I've seen that INTEGER and LONG is accepted for the same thing.
IMHO it would be nicer if you would stick with INTEGER and use LONG for machine (os?) dependable size.
I worked with XBasic/XBlite, and there XLONG is 32bit or 64bit, depending on the machine ( natural CPU integer ). This is very nice because some stuff on Windows act that way. (Like Window-hWnd's on Win9x and WinNT&up or a Function addresses ...)
Don't know about Linux/BCD etc. though...
Don't ask me how it's done inside the compiler, I don't know.
I'm saying this because I'm in the process of porting kernel32 include file from XBlite to fb, and where I find XLONG (so called natural long - machine dependend) I change it to long (so it could be 32bit or 64bit depending on cpu) and if you would consider to use my suggestion you could.
SLONG (fixed 32bit) will be changed to INTEGER and ULONG (fixed 32bit) to UINTEGER.
What do you guy's think?
regarding data types, I've seen that INTEGER and LONG is accepted for the same thing.
IMHO it would be nicer if you would stick with INTEGER and use LONG for machine (os?) dependable size.
I worked with XBasic/XBlite, and there XLONG is 32bit or 64bit, depending on the machine ( natural CPU integer ). This is very nice because some stuff on Windows act that way. (Like Window-hWnd's on Win9x and WinNT&up or a Function addresses ...)
Don't know about Linux/BCD etc. though...
Don't ask me how it's done inside the compiler, I don't know.
I'm saying this because I'm in the process of porting kernel32 include file from XBlite to fb, and where I find XLONG (so called natural long - machine dependend) I change it to long (so it could be 32bit or 64bit depending on cpu) and if you would consider to use my suggestion you could.
SLONG (fixed 32bit) will be changed to INTEGER and ULONG (fixed 32bit) to UINTEGER.
What do you guy's think?