2009-01-15 11:07:22 UTC
years, and making a little money at it. Recently a friend of mine asked
what it would take to resurrect one of them, a program that was
originally written for the Apple Macintosh in interpreted Microsoft
BASIC then converted it to the compiler when that came out in about '86.
I told him that three months would probably be required - Visual BASIC
not.NET being pretty similar.
Now, looking back at some of my other old programs, I am thinking that
with a nice frontend, they might have some commercial value.
Lately, for the last eight years or so, I have been writing in
PowerBASIC, first for DOS then the Console Compiler. From past
experience, conversions are not as difficult as they first appear to be,
so the question is, how should I proceed?
Microsoft left me hanging when it dropped Mac BASIC many years ago and,
as I understand it, they left a lot of VB6/VS6 developers hanging when
it went to .NET, so I am not eager to go there, even though I already
own copies of and have written some small apps using both of them. The
most obvious route would be to invest in PowerBASIC for Windows, but my
intuition tells me not to get more involved with Zale's and his
snickering lieutenant's arrogance and paranoia - I'm too old to put up
with their bullshit. In that regard, I just read the thread in the
comp.lang.basic.powerbasic newsgroup "Banned from the PowerBASIC forum,"
and it is much like my own experience with these people.
So, my question is, coming from PBCC, where should I turn for a frontend
and backend BASIC compiler? I am going to look at FreeBASIC more
closely, mainly because the PureBASIC company seems to be a little
difficult to reach, (even though I read and write German fairly well).
Realistically, I suppose VB.NET bloatware is the best choice and I have
a little time to get up to speed with it, as opposed to learning C#.
I would be grateful for any help with this.