>>> Last time I tried XBasic, you could not make executatbles for Linux,
>>> so you would always have to reveal your source. Also it was extremely
>>> buggy, even on its own demo files. And the manual is not up to it.
>> Every release of Linux XBasic could make binary executables.
>> But yes, XBasic is unstable on some newer Linux distributions.
>> I know some problems are caused by different behavior in some
>> new window-managers [or new releases], but probably not all.
>> These problems are being investigated, and will probably be
>> fixed soon. The problems are certainly due to changes in Linux
>> or libraries, because XBasic has been reported solid as a rock
>> on some systems.
> This is provable not true:
> This is from the XBasic docs I have, in file xb/html/advanced_2.htm :
> [snip your quote from XBasic documentation]
Thanks for pointing out that documentation error.
I assume you understand the standard of proof is never
what any person or document happens to say, but reality.
And in reality, both Windows XBasic and Linux XBasic
can make executables on normal Windows95/98/NT
and Linux systems. I know so by doing so.
For example, to compile, build and execute the "ademo.x"
sample program that comes with XBasic, do the following:
In both cases, start an xterm or DOS console window and
get into the XBasic working directory.
##### Linux #####
make -f ademo.mak
##### Windows #####
The first line compiles source program "ademo.x" into
assembly language program "ademo.s" and makefile
"ademo.mak". The second line builds executable file
"ademo" or "ademo.exe" and puts it in the run subdirectory.
The third line executes "ademo" or "ademo.exe".
I am between Linux systems at the moment, so I may
have made a minor mistake in the Linux lines. The only
two possible errors would be: "the -f is the wrong switch",
and "the executable is not put into the run subdirectory,
in which case simply entering "ademo" alone will run it.
But thanks again for pointing out the documentation error.
The error in the on-line version has been fixed, but the one
inside the downloadable ZIP file has not.