How many still use qb here?

[Anonymous]

I have almost not touched Quickbasic since I started to play around with Freebasic. God, I hated to run out of string space. I was/are very good at it. I was/are also good at corrupting my code. :king:

What do you mean by corrupting your code?

*****

I think he means errors that could happen where qb wrote over the memory where your code was stored, then if you saved, your src was trashed.

At leas that happened to me numerous times.

[na_th_an]

Never happened to me, but I've been listening to that thing since I first came here. Apparently it happens when you use the IDE. It's an IDE issue, I think.

[BadMrBox]

I have almost not touched Quickbasic since I started to play around with Freebasic. God, I hated to run out of string space. I was/are very good at it. I was/are also good at corrupting my code. :king:

What do you mean by corrupting your code?

*****

I think he means errors that could happen where qb wrote over the memory where your code was stored, then if you saved, your src was trashed.

At leas that happened to me numerous times.

Yepp, that's exactly what I mean.

[Moneo]

I have almost not touched Quickbasic since I started to play around with Freebasic. God, I hated to run out of string space. I was/are very good at it. I was/are also good at corrupting my code. :king:

What do you mean by corrupting your code?

*****

I think he means errors that could happen where qb wrote over the memory where your code was stored, then if you saved, your src was trashed.

At leas that happened to me numerous times.

Yepp, that's exactly what I mean.

Well, that's one of the risks of running in interpreted mode. I always compile and then test.

One obvious way around this is to save your source code, in pure text, before running any tests. Then if something goes wrong you have your original source.

*****

[Anonymous]

yeah it's an IDE issue

One obvious solution is to use a real 32-bit compiler, lol.

sorry couldnt resist :bounce:

[BadMrBox]

FBIDE :longeye:

[zoasterboy]

I do NOT use FB. I <3 QB!!!

[Dr_Davenstein]

There is actually no reason not to use both, if you think about it. The only reason I don't play with QB anymore is because it chokes on XP. Well, that and the fact that FB can use C libraries, was created by one of us, doesn't suck... that was more than one reason, I guess. :lol:

[Ralph]

Dr_Davenstein wrote:

The only reason I don't play with QB anymore is because it chokes on XP.

I had trouble with QuickBASIC 4.5 when I got my new computer, with Windows XP, and, for a while, got very upset over that fact. Finally, I discovered that it wasn't XP, which others kept insisting allowed QuickBASIC to run fine. I discovered it was a program called Flatbed.exe, that was automatically launched for my scanner (which now doesn't run with XP and is no longer supported past Windows 2000). The fix was to take Flatbed.exe off of my automatic launch list. Miraculously, that fixed ALL my QuickBASIC 4.5 and XP problems. Now, it runs fine, thank you!

But, Dr, you know this, and should remember me and my problem and solution, from the old QBasicCafe.com

[Anonymous]

the reason isn't pure qb, it's i think when you start using ems, interrupts, whatever, that xp doesn't emulate it 100%.

the reason people use fb is because it is a 32-bit compiler. there is no conversions, no emulation that has to be done. the apps run natively, fast.

edit: oh and, it's added a crap load of features. and also it's open source, no evil m$ bs waiting to happen, distrbute FB all you want, you aren't gonna get any 'cease and desist' shit like you could with qb =)