Banned from the FreeAsic forum, hooray!

[jj2007]

Instead of taking FreeAsic's problems seriously, they prefer to kill the messenger...

The thread "Using a static library: linker problems" was deleted - no problem, every new user of FB will run into the same problems over and over. It's a shame, because FreeBasic is perhaps (next to PowerBasic) the last good BASIC compiler around. But the FB Forum is so crammed full of desperate users asking for help because their simple proggies won't compile with the xyz "toolchain". Many problems are caused by fanatic type checking that simply does not work in a Windows environment, others because, well, for the benefit of serving the 1% Linux fans, one has to sacrifice lots of good features.

So, Hutch, please keep up the good work with PowerBasic - the World of BASIC needs you

P.S.: The text below was supposed to be my last post

...which helps no one.

First, I have not enough time into indulging into the secrets of compiling fbc.exe, so bear with me if I can't help you with code. Quoting one friendly member whose name I want to keep out of this thread:

The warnings can be suppressed by doing things like
wc.hbrBackground = cast(HBRUSH__ PTR,(COLOR_BTNFACE+1))
and
wc.hIcon = LoadIcon(hIconLib, cptr(any ptr,239)) ' get the butterfly icon

Yes, that will suppress the warnings, but you really cannot expect such stuff from a newbie, especially not in a language that has a "B" in its name.

What the compiler could do, instead, is to check what the wc.hbrBackground member expects, and to provide the friendly Gcc compiler automagically with the necessary cast if, and only if, the naked parameter passed by the newbie can be casted to what the compiler expects. Another example: SendMessage. Numerous absurd warnings and errors. Each Message is documented, and can tell the compiler the kind of parameters that are expected. Now if the user passes a FB string where a zstring ptr is expected, cast it, for heaven's sake, but don't ask the "B" user fumble this.

IMHO that would be sufficient to make all nonsense warnings disappear.

[hutch--]

This sounds a bit unfortunate but in every programming environment you seem to have this "push" to turn them into mediocre chyte.

There has been an ongoing battle in PB to reduce the language down to its lowest common denominator, turn it into a toothless terror but fortunately the author Bob Zale, who was a member of this forum until he passed away, built enough capacity into his last 2 compilers to be able to bypass the mediocre. The new owner, Adam Drake keeps the 2 compilers maintained so they are up to date.

There is a need for a proper 64 bit basic compiler, not just a rewrapped C compiler, but it would need to be a native code compiler written for 64 bit Windows, not a hotch potch of left over GNU binaries. Something that has long differentiates Windows from Unix distributions is persistence. The code you wrote in 32 bit 25 years ago still runs on current 64 bit Windows.

I will keep working to extend PowerBASIC as time allows as I see it as a decent 32 bit tool that needs to keep its status as a native code binary compiler, not be misrepresented in the way it has been.

[HSE]

Banned from the FreeAsic forum, hooray!

Sorry to know that JJ ... because You will have more time for strange things in assembly 

Joke apart, for everybody who have beginning to make interesting things in Basic, is sad to know that Basic options decrease.

[daydreamer]

seem like the horror of get stuck fix typecasting alot,until you tire of it and give up your project JJ
its makes programming lot easier in masm windows programming get rid of all waste spend time finding out use right type/typecasting all the time,when everything is dword or masm64 qword

[jj2007]

seem like the horror of get stuck fix typecasting alot

Code: [Select]

mov hEdit, rv(CreateWindowEx, WS_EX_CLIENTEDGE, Chr$("RichEdit20A"), NULL, reStyle, 0, 0, 1, 1, hWnd, ID_EDIT, wcx.hInstance, NULL)
mov hEdit, rv(CreateWindowEx, WS_EX_CLIENTEDGE, Chr$("RichEdit20A"), NULL, reStyle, 0, 0, 1, 1, FP4(1.0), ID_EDIT, wcx.hInstance, NULL)
mov hEdit, rv(CreateWindowEx, WS_EX_CLIENTEDGE, Chr$("RichEdit20A"), NULL, reStyle, 0, 0, 1, hWnd, ID_EDIT, wcx.hInstance, NULL)
mov hEdit, rv(CreateWindowEx, WS_EX_CLIENTEDGE, Chr$("RichEdit20A"), NULL, reStyle, 0, 0, 1, 1, 1, hWnd, ID_EDIT, wcx.hInstance, NULL)

Code: [Select]

## line 33: argument #9 should be DWORD ##
## line 34: not enough arguments for CreateWindowExA ##
## line 35: too many arguments for CreateWindowExA ##
I'm not against some basic type checking, but I've always thought that counting the arguments is more important than checking their types

[hutch--]

 

JJ,

We could lead you astray with PowerBASIC, its connercial software written by a genuine assembler guru, Bob Zale. 

[jj2007]

We could lead you astray with PowerBASIC, its connercial software written by a genuine assembler guru, Bob Zale. 

I know a free alternative

Bob Zale was a great programmer, no doubt. I tried PowerBasic, I even bought a license years ago, but I never got used to it, being spoiled by GfaBasic. % signs for Windows constants like %WM_INITDIALOG, all uppercase etc simply didn't encourage me to go ahead. It's a matter of taste. I get easily p*ssed off by syntax I don't like, mostly C/C++ type {brackets} and useless semicolons;

[hutch--]

There is a technique where you use a macro and it works OK but I could not be bothered doing a complete include file for it.

[jack]

Instead of taking FreeAsic's problems seriously, they prefer to kill the messenger...

The thread "Using a static library: linker problems" was deleted - no problem, every new user of FB will run into the same problems over and over. It's a shame, because FreeBasic is perhaps (next to PowerBasic) the last good BASIC compiler around. But the FB Forum is so crammed full of desperate users asking for help because their simple proggies won't compile with the xyz "toolchain". Many problems are caused by fanatic type checking that simply does not work in a Windows environment, others because, well, for the benefit of serving the 1% Linux fans, one has to sacrifice lots of good features.

So, Hutch, please keep up the good work with PowerBasic - the World of BASIC needs you

P.S.: The text below was supposed to be my last post

...which helps no one.

First, I have not enough time into indulging into the secrets of compiling fbc.exe, so bear with me if I can't help you with code. Quoting one friendly member whose name I want to keep out of this thread:

The warnings can be suppressed by doing things like
wc.hbrBackground = cast(HBRUSH__ PTR,(COLOR_BTNFACE+1))
and
wc.hIcon = LoadIcon(hIconLib, cptr(any ptr,239)) ' get the butterfly icon

Yes, that will suppress the warnings, but you really cannot expect such stuff from a newbie, especially not in a language that has a "B" in its name.

What the compiler could do, instead, is to check what the wc.hbrBackground member expects, and to provide the friendly Gcc compiler automagically with the necessary cast if, and only if, the naked parameter passed by the newbie can be casted to what the compiler expects. Another example: SendMessage. Numerous absurd warnings and errors. Each Message is documented, and can tell the compiler the kind of parameters that are expected. Now if the user passes a FB string where a zstring ptr is expected, cast it, for heaven's sake, but don't ask the "B" user fumble this.

IMHO that would be sufficient to make all nonsense warnings disappear.

@jj
is this the thread that you claim was deleted? https://www.freebasic.net/forum/viewtopic.php?t=31463

[jj2007]

is this the thread that you claim was deleted? https://www.freebasic.net/forum/viewtopic.php?t=31463

Yes, that's the one. So it is back... interesting

Btw yesterday I was banned for a month, now the site tells me "You have been permanently banned from this board.". Oh well

[guga]

You were banned from fb forum ?   

Weird behavior of them, specially with a compiler that lacks support anyway. But, that´s a coincidence you open a post about FreeBasic. I´m currently trying to port that LolRemez app to masm (and RosAsm), and i ended up trying to build a Runtime Library for fb. I read that a guy was trying to do it, but unsuccessfully so far. So, i´m giving a shot to try to create a dll of fb Api. The main problem is, internally, this thing is kinda badly written, and is hard to follow and fix what is necessary, but i´m trying.

If i suced, i´ll release it here to you and Steve take a look, and see if it can be useful somehow.

[jj2007]

You were banned from fb forum ?   

I complained every now and then about the weird and absolutely useless warnings when compiling a standard Windows template. And sometimes I post MasmBasic snippets to demonstrate how FreeBASIC could look like if they took the "B" seriously. Oh well, now I am banned forever by "Paul Doe", and crying bitterly all night long

[jj2007]

Sorry to know that JJ ... because You will have more time for strange things in assembly 

I do my best

Code: [Select]

Name              #called   total time   per call
SubRE                4765      5736 ms    1204 us
OpenLink                3      5183 ms    1727 ms
AssRun                  1      3462 ms    3462 ms
FindOptions             1      3215 ms    3215 ms
FindTextP             381      3173 ms    8329 us
AssRunThread            1      2654 ms    2654 ms
FiWo                    9      2610 ms     290 ms
ReOpenFile              1      1305 ms    1304 ms
WndProc              3159       988 ms     313 us
CbTimer               333       971 ms    2917 us
SetLcBufferP           27       849 ms      31 ms
ConvertLinks            1       480 ms     479 ms
DrawPics               24       412 ms      17 ms
SetSelFromB            19       386 ms      20 ms
RestoreSel             16       380 ms      23 ms
ReSaveFile              2       339 ms     169 ms
## Hit any key. Ctrl C may cause data loss. Press 'h' to hide the console, 'r' to reset ##

[hutch--]

There is a solution to a ban message of that type, tell the to "get phuked", preferrably with a pineapple being rotated. You could leave it up to them to pick which end was recommended. 

[guga]

tell the to "get phuked", preferrably with a pineapple being rotated.