At this point why don't you just audit the language for all the crap, broken and obtuse things, gut them, and rebuild them however you like with no regards for what went before (or leave them out altogether) and call it FreeBasic 2.0.

Why? Who is this for? This doesn't affect me so whatever, but I'm gonna be honest: potentially throwing your entire current user base under the bus and changing the ABI for some potential future code or mythical people who are going to port from a different language they're currently using sounds in...

Answering someone elses question on how to achieve something similar in Freebasic and making remarks about deficiencies in a different compiler are undermining your efforts? The hard work is in doing a thing and putting it out there. What happens after that is out of your control. Expecting a reward...

It started life as a PowerBASIC static link library (sll) by Stuart McLachlan. I started to port it to FreeBASIC and hit snags with propriety methods which would be difficult to emulate in FreeBASIC. Even if we could emulate them, we may have copyright issues. Ironically, as I've recently found out...

To put it a different way: allocate(32) allocates 32 bytes, not 32 pointers. 32 bytes is either 8 or 4 pointers depending on if you're compiling 32-bit or 64-bit. So accessing anything above pointers[7 or 3] may cause problems. You can either use allocate(32 * sizeof(*pointers)) or create a FB array...

Imortis wrote: ↑Feb 01, 2024 23:57 Interesting. I would be interested in seeing the code for this.

I don't know how this works, but you can get 90% of the way there with TaskDialogIndirect. The only thing it lacks is support for changing the colours.

It's because usually your FB app doesn't opt-in to do its own scaling, so when you/fbgfx creates the 800x600 window, Windows scales it up to keep the effective 800x600 resolution. In full screen mode, the resolution really is 800x600 but Windows still scales the window hence it looks wrong despite t...

The genreated code for the case checks { { uint16* TMP$4$2; uint16* vr$3 = fb_StrToWstr( (uint8*)*(uint8**)&C$0 ); '' convert the select case string to wstr TMP$4$2 = vr$3; int32 vr$4 = fb_WstrCompare( (uint16*)TMP$4$2, (uint16*)L"a" ); '' check against case value if( (vr$4 != 0) ) got...

deltarho[1859] wrote: ↑Jan 20, 2024 11:12 I call by now and then.

You should do so more often, I could've saved you three weeks - viewtopic.php?t=32483

But what is that garbage in the rest of dimTb? That's your code not following the instructions. fbc-int/array.bi '' take care with number of dimensions; fbc may allocate '' a smaller descriptor with fewer than FB_MAXDIMENSIONS '' in dimTb() if it is known at compile time that they '' are never need...

VK_ values of 0x0 and 0xff aren't defined. All the tables and documentation go from 0x1 to 0xfe, so I guess it was a case of Garbage In, Garbage Out that just happened to be fine all this time.

It still needs a solution. It was two posts under that one. Nevertheless, I did it. Here's a diff to current master. diff --git a/src/rtlib/win32/fb_private_console.h b/src/rtlib/win32/fb_private_console.h index a511d98b6..950e1e503 100644 --- a/src/rtlib/win32/fb_private_console.h +++ b/src/rtlib/...

There's one pretty big difference between the C code formation of the message headers, which is 5 lines: "To: " TO_MAIL "\r\n" "From: " FROM_MAIL "\r\n" "Cc: " CC_MAIL "\r\n" "Subject: SMTP example message\r\n" "\r\n" /*...

Dim As String sConhost = _WinAPI_FindFile("C:\Windows\WinSxS\amd64_microsoft-onecore-console-host-core_*", "conhost.exe") In 32-bit apps you can use sysnative to access the 64-bit system32 folder without it being redirected to syswow64, like C:\Windows\Sysnative\conhost.exe It i...

You could do either of those but they'd be wrong. It's still a 64-bit value in 32-bit code. This is the evntrace.h definition for the invalid handle value, if that doesn't work in 32-bit fb, that's an FB problem. #define INVALID_PROCESSTRACE_HANDLE ((TRACEHANDLE)INVALID_HANDLE_VALUE) You can just ma...