02-01-2005, 08:38 PM
Just joined the group having seen the link in the Google All Basic User Group.
Although I must admit I offer a number of freeware programs on my site in different Basics, along with the code in some cases, I have to congratulate you on your generosity in distributing this software freely. This is especially in view of all the hard work you must have put into producing the software. However I would like to make a few suggestions if I may.
For the benefit of âsimple souls â like me, you should include say an INTRO.TXT file pointing out it is a compiler only to create an EXE file. A variety of Editors can be used to create or modify a suitable .BAS file such as Notepad, Qbasic, Quickbasic. You can also use the old GWbasic providing as with the Qbasic, you save it as an ASCII file. But you will need to use Notepad to delete the end file mark with GWbasic or it produces an ASM file instead of an EXE. I know not what to do with an ASM file.
I managed to create an EXE file ok this way by just dragging a BAS file onto FBC.EXE with either the DOS or Windows versions, except the DOS version did not like the use of SCREEN. Both versions compiled ok irrespective of whether line numbers were included or not under Windows XP. However I failed to make any sense of the DOS version while in the DOS Command prompt. I was baffled which parameter to use, and only succeeded in creating a few files with strange extensions.
My final suggestion is you might consider renaming say the Windows version as fbcWin.exe and the directory as FreeBASICWin to avoid confusion when experimenting with each version
Gordon
http://sionet.mysite.wanadoo-members.co.uk
Although I must admit I offer a number of freeware programs on my site in different Basics, along with the code in some cases, I have to congratulate you on your generosity in distributing this software freely. This is especially in view of all the hard work you must have put into producing the software. However I would like to make a few suggestions if I may.
For the benefit of âsimple souls â like me, you should include say an INTRO.TXT file pointing out it is a compiler only to create an EXE file. A variety of Editors can be used to create or modify a suitable .BAS file such as Notepad, Qbasic, Quickbasic. You can also use the old GWbasic providing as with the Qbasic, you save it as an ASCII file. But you will need to use Notepad to delete the end file mark with GWbasic or it produces an ASM file instead of an EXE. I know not what to do with an ASM file.
I managed to create an EXE file ok this way by just dragging a BAS file onto FBC.EXE with either the DOS or Windows versions, except the DOS version did not like the use of SCREEN. Both versions compiled ok irrespective of whether line numbers were included or not under Windows XP. However I failed to make any sense of the DOS version while in the DOS Command prompt. I was baffled which parameter to use, and only succeeded in creating a few files with strange extensions.
My final suggestion is you might consider renaming say the Windows version as fbcWin.exe and the directory as FreeBASICWin to avoid confusion when experimenting with each version
Gordon
http://sionet.mysite.wanadoo-members.co.uk
