Good old 16 bit DOS?

[Anonymous]

i have to agree that ive only had real data loss from malfunction in my code from qb. granted a lot of the time i was trying to like drop massive amounts of memory in the wrong spot. but still, ive never gotten anything over even a page fault in fb. never general protection fault or specially not a blue screen :o

if you want retro stick with fb... retro isnt used cause its functional. and fb is used because it is

[Dr_Davenstein]

I've had QBasic obliterate my code once the program becomes too big. I guess some things should have been split into mod's, but I don't think it should erase your code becasue of it. It should at least give you a warning...

WARNING #666:

CODE TOO BIG.

DELETING PROGRAM, PLEASE WAIT...

PRESS ANY KEY TO CRASH SYSTEM!

:lol:

[relsoft]

What Z!re said..

How about a 6502 version so we could make some NES games in FB? -- note: i'm not been serious, really

I thought you ported FB to the z80? LOL

[Spotted Cheetah]

It did not happened ever to anybody here that (s)he just double - clicket on QB.EXE, and the machine went mad?! That was what greatly annoyed me! I never could predict when, after which click will that damn QB mess up everything! That could happen anytime. Then hit RESET, wait, type a password, look at the lioness (she is my boot picture instead of that dull sky and Windows logo), type in an another password, then find QB in the third directory of the twelweth on my drive E, and hope that now i can type in two lines of code and do not forget to save it again before hitting RESET again. With Turbo C i only had to be careful when i tried to run my program after messing with it's memory allocation routines. But this QB really can make me so upset that i would throw the compo off the window if i did not know that i can not fix it with just some glue. But if Billy was there in that time... And a hammer... A Windows bug list would fit to the purpose as well...

Call it "peaceful retro programming..."

[Dr_Davenstein]

Just think of FreeBASIC this way...

"Uber peaceful modern programming with a retro feel."

[MystikShadows]

And a standing ovation for Dr_Davenstein for the accurate view of FreeBasic :-) I couldn't have said it better myself :-).

[thegrogen]

Maybe a C64 port, down with modern CPU's!

Hehe, don't forget about the SNES.

Also, some modern console ports would be nice (PS2/PS3, XBox/Xbox2, N64, GameCube, PSP, etc.). That way, we would have TRUE cross-platform capabilities!

[Spotted Cheetah]

I think retro should be really retro at least partially. Something is retro when it
really fits to the old life so at programming when it runs for example on my old
25MHz 4.86 (Sadly it broke down...). Of course a retro MIGHT be rewritten to
function correctly on a new PC without emulator, but this "might" is important. If
it can not be set up on an usual 15 years old equipment then it can not be called
retro, rather just "old style" thing. The most silly was when such an "old style"
thing - what was not retro, so i could not experience it - refused to run correctly
on my P233 (I not want to lie, this did not happen, since i had not seen such
software yet. But it could have happened as it happened with other things looking
like requiing much less hardware than what they actually needed)! This can not be
called retro...

So QBasic messes up, FreeBasic is not suitable - i finally changed to Turbo C at
retro writing. It is easier to port working, carefully designed(!) retro C programs
to a modern OS than messing with QB - FB.

Of course FB is a good thing, but i afraid of that once it might be abandonned, and
then i will be there again with an abundance of basic codes waiting to be rewritten
in C. That's why i not use it, but as at the 16 bit side i had many basic codes, i
would happily keep on coding retro there if that QBasic not drives me mad. I simply
not want to program in two languages in 32bit since i got enough of code conversion
- annoying dull work what i think i will have to do with all my 16 bit codes if i
want to code retro later ...


(Just getting annoyed of these modern views... I hate that information technology
develops so fast that there is no time to really try out and get the best out of
anything. What most made me upset is the case of FM: a nice sound generation
technique what almost not requied CPU and memory at all: it completely dead. Now
everything has the smell of money all around IT development )

[MystikShadows]

Ok, the first reason, I assume, that v1ctor made freebasic OpenSource wasn't to abandon it, but rather to start an initiative that is made to grow. Should v1ctor EVAH decide to abandon the project for any reason whatsoever, it's open source, therefore anyone else can decide to take it over, right away.

For the same reasons, say you have an idea of your own basic and you don't want to rewrite the whole system, you can easily branch off the FreeBasic code tree and add your own functionality...that's what OpenSource is for.

In the other hand, FreeBasic is still a young project, and there's still much to be done, and the best way anyone can help out is by writing apps in Freebasic, games, apps, anything to be able to test everything out good and iron out the bugs....again that's what OpenSource is also for :-).

Have you seen the impact that freebasic has had on the QB community? I don't think any of us would let FreeBasic die or get abandonned. FreeBasic even as such a young version release has already established itself as THE replacement language for the QB coders.

What else can I say ;-).

[ShadowWolf]

why do you want retro i mean what's the point it not like you can push the envolple any more it pretty much all explored territorey at this point nothing new.

i mean 16bit realmode isn't somthing to get really excited about for the whole nastogic fealing i mean you can get that with doing 6502 coding that exicting since you can run your code though a NES consol if you have a flash card or nes emulater which give it all a big cool facter.