This Isn't BASIC
This Isn't BASIC
This isn't BASIC.
I've been struggling for hours trying to accomplish some fairly simple tasks with FreeBASIC, porting working code already written in another "dialect" of BASIC. The BASIC language is supposed to be easy. FreeBASIC isn't. It's become an arcane bastardization of BASIC. There is nothing easy about it. I feel like I'm programming in C all over again. Try this, try that, search the documentation high and low -- nothing seems to work. Too much trial and error, too much work. I'd be better off converting my project to C because at least C is (sort of) standardized. My current project isn't going to be ported to FreeBASIC. It's going to remain in its current BASIC "dialect" where at least it works and I don't have to devote an entire evening trying to accomplish something with no success.
I've been struggling for hours trying to accomplish some fairly simple tasks with FreeBASIC, porting working code already written in another "dialect" of BASIC. The BASIC language is supposed to be easy. FreeBASIC isn't. It's become an arcane bastardization of BASIC. There is nothing easy about it. I feel like I'm programming in C all over again. Try this, try that, search the documentation high and low -- nothing seems to work. Too much trial and error, too much work. I'd be better off converting my project to C because at least C is (sort of) standardized. My current project isn't going to be ported to FreeBASIC. It's going to remain in its current BASIC "dialect" where at least it works and I don't have to devote an entire evening trying to accomplish something with no success.
You are certainly entitled to your opinion, but I can't recall any times you posted in recent memory asking for guidance on any issues. You have two choices at this point: ask questions about the problems you are having, or abandon FreeBASIC. If you would like to ask a question, please do. If you are abandoning FreeBASIC, then good luck with your project.
-Vince
-Vince
After about five hours I finally hit upon the breakthrough that got my code working. It wasn't easy but it works, so I recant my previous post and will press on with FreeBASIC. Sorry for any ruffled feathers, but after five hours one can get a little hot under the collar.
Thanks to those who answered my questions in another section of the board.
Moderators: feel free to delete this thread.
Thanks to those who answered my questions in another section of the board.
Moderators: feel free to delete this thread.
-
- Posts: 5494
- Joined: Sep 12, 2005 20:06
- Location: California
Thanks for the kind offers of help. I think I'm good for now. I'm trying to work things out as best I can and am saving my questions for when I really need them.
I think I see some room for improvement in the documentation, though. I have contributed to the documentation wiki in the past (when anyone could edit it) and I would be happy to do so again. I would like to see the alphabetical keyword list expanded.
Porting is a pain, yes, but in most regards FreeBASIC is closer to the way real BASIC ought to be. Before discovering FreeBASIC I had started writing a BASIC to Perl and a BASIC to Pascal converter so I know a thing or two about it.
I think I see some room for improvement in the documentation, though. I have contributed to the documentation wiki in the past (when anyone could edit it) and I would be happy to do so again. I would like to see the alphabetical keyword list expanded.
Porting is a pain, yes, but in most regards FreeBASIC is closer to the way real BASIC ought to be. Before discovering FreeBASIC I had started writing a BASIC to Perl and a BASIC to Pascal converter so I know a thing or two about it.
-
Heh...
FreeBasic is in some aspects is near to C language becose user must many
things do manualy which you dont in many other basic dialects.
But on this way user learn deeply how things really works.
FreeBasic is in some aspects is near to C language becose user must many
things do manualy which you dont in many other basic dialects.
But on this way user learn deeply how things really works.
Re: -
This is true. I'm finding this out by interfacing with a C library which contains structures and pointers to structures and pointers within structures and strings which have to be zstrings and pointers to structures which have pointers to strings which have to be zstrings. Whew! I understand some of this is necessary either to maintain some semblance to QB or to make the language powerful in a C sort of way, but it does present a learning curve.aston wrote:Heh...
FreeBasic is in some aspects is near to C language becose user must many
things do manualy which you dont in many other basic dialects.
But on this way user learn deeply how things really works.
Re: -
It didn't for me. One of the things that really impressed me initially was how easy and intuitive the syntax was. Most of the problems I had were with the early header files.chris319 wrote: ...but it does present a learning curve.
In Australia the common language is either Strine or Horse-trail-yen.
See; http://en.wikipedia.org/wiki/Afferbeck_Lauder
See; http://en.wikipedia.org/wiki/Afferbeck_Lauder
You learn something new every day.Richard wrote:In Australia the common language is either Strine or Horse-trail-yen.
See; http://en.wikipedia.org/wiki/Afferbeck_Lauder