Qbasicnews.com

Why are you trying to match the C headers?! I thought one of the whole great charms of FB was the fact that it DID NOT try to be C! :evil:

This is just a silly idea, and IMO a stupid one, but how about having FBC able to read C headers too?

Like, both C and FB headers, that would make porting libraries a breeze, infact, there would be no porting involved.

But yah, don't mak this another C wannabe language. Whats next? ; for line ends?

Are you talking about the #define support he added, or what?

Yeah, I'm not really seeing where you're coming from.

I guess he means renaming the winmm header...

C compatibilty is _good_ IMHO... but reading C headers - that would require writing a large portion of a C compiler...

Yar. Best would be a 'C' header auto-porter but that's a lot of work behind the simple aspects of such a tool.

Not only that but you'd have to take into consideration the various platforms' data type sizes and whatnot. Anyways, yes, I was talking about the renaming of win32 api headers. This is the second time headers have been renamed in the official distro to "match the C versions". NOOOOOOOOOOOOOOOOO! It may be a small issue, but that's how the big issues ALWAYS begin! Before you know it, the zealots will begin saying that the C in FBC means the C language! :evil:

Okay so I'm overreacting (slightly), but hey, this is a big deal for me...the last thing I want to see is yet another BASIC that wants to be C. There's too many of them already. FB is unique amongst BASIC compilers in two ways: first, it actually COMPILES code, rather than being yet another sh1tty interpretter, and secondly, it doesn't pretend to be C. Can it be kept this way, please?

While I have absolutely no idea what you dudes are talking about, I definately agree that freeBASIC should stay the hell away from C. It's turning out more like C with every new release, and I don't like that. I'm feeling that freeBASIC has already deviated from what it's original ethos was, and it should return to that.

Quote:I'm feeling that freeBASIC has already deviated from what it's original ethos was, and it should return to that.

What exactly was the "original ethos" of fB?

Despite any protestations from alternate language zealots, it's a C, C world out there, and there's nothing we can do about it. Why do so many X Window window managers look like MS Windows? Because they have to to succeed.

In other words, take over the world by surprise after pretending to be just like that other language...

How so is it looking like C?

Pointers? Man, when you don't have it, people complain, when you have it, the same happens, nm..

Pre-processor? Ditto.

What do you prefer, "CALL DWORD foo USING bar" as in PowerBASIC? "foo(bar)" seems much simpler to me.. "foo->bar" looks more logical, instead of "foo@bar".

You use all "additions" if you want, but calling libraries made with C in mind (SDL for example), you must use them somewhere, live with that.

If we get a h2bi (C header to FB inc file) tool (freePASCAL has a h2pas, i may try to port it), all headers will have the same name as in C, not having them named as the original now will force ppl to change their sources later, or then add "empty" inc files with say: winmm.bi: '$include: "mmsystem.bi" inside -- btw, i had to search for Mingw32 headers to find the MCI one so i could add new constants, different names make it harder to ppl that want to help doing that.. i doubt anyone will anyway.

Peace..