heh among the things i was trying to get to work with freebasic, but without success they were "intrinsinc" instructions... like i could even get SOME working i.e. declare function __popcnt cdecl alias "__builtin_popcount" (n as integer) as integer print __popcnt(3) but i can't g...

ok... where i do start... first i will use the old version of it as i think the .bi expect that version.... AND... the newer version does not have windows binaries... so one would need to compile that to even try... and i wont do that, so lets work with what we have... since aspell have installers f...

ok, so it seems on freebasic 1.01+ i need to have two macros calling each other for the idea to work... and to avoid having duplicates of the macros it will have another macro to create the two macros.... so it looks like this: #macro RepTill10() #macro __GenMacro(_GA,_GB) #macro __DoRepeat##_GA() p...

so what is the current state and ideals of freebasic regarding Recursive Defines? its a very useful thing to allow more advanced parsing at compile time, but seems too much effort is doing on freebasic to try to "eliminate" that without a good reason... for example: #macro UcaseChar( _N , ...

so... freebasic have variadric macros... and unlike C, freebasic supports #preprocessor definition inside preprocessor... the only thing blocking a Iterative Variadric Macro, is because freebasic blocks recursive defines... BUT! you can fool it to accept that, and call a macro, with a variable numbe...

who was the genius bright fellow, that converted a beauty .h interface into fellow garbage OOP?? genius people these days...

why "option escape" requires fblite lang? when it makes more sense to have it for fb than fblite... i.e. a way to make all strings work like C...

unless, theres a way to have that on lang fb without the option escape (and obviously without using !"..." on all strings ^^)

ok then :) well my point was that win32s programs works fine even on win10, theres no attempt to unite anything... and i was point out some factors that make win32s superior in terms of teaching good practices even to win32 programmers, and that most of the commercial programs are easily doable even...

and talking about win32s compatibility... its somewhat "harder" to write for it with modern tools, because theres no debuggers that can debug properly... so the only way to debug would be use MSVC 4? that support win32s and then it can be REMOTELY debugged to a NT 3.52 machine... and it wo...

Hi MySoft, that's a great project! I am still running a big 16-bit application that uses lots of 32-bit stuff through thunking, it runs fine in XP but I doubt it would run in a Win 3.1 plus Win32s environment. May I ask what is your motivation to do this? Even finding the hardware must be non-trivi...

@Mysoft looks really nice, what screen resolution are you using on DOSBox? 1024x768... i also made a "mouse program" to have a seamless mouse on win3.11, and the win3.11 on dosbox have winsock using Trumpet TCP, because the drivers for native MS Network or MS Lanman does not work on dosbo...

The point is that you can't do things like you normally do, and what internet recommends. This complicates things for people mostly working on newer windows. Just like any Windows code after 2000-2005 will probably call -W functions a lot. Things like that are basically behind the advise to not add...

You can't make use of timers like in still supported versions of Windows. (and for a lot more, like unicode etc). actually you can... is just freebasic method that didnt used multimedia timers for win95/98, and... using multimedia timers is possible to make a sleep on win95/98 using an event.... (s...

not to mention that the programs compiled for win32s work on windows 3.11 to windows 10 :P heh, and yeah even on DOS freebasic gfx have the problem of not working properly inside windows, because of unecessary use of the PIT interrupt, and automatic "full" update, so many of the concepts i...

yeah indeed... because the "andalso/orelse" on preprocessor is doing the same as "and/or" i.e. its not shortcicuiting the parsing... the same difference from dim as integer ptr pBad = 0 if pBad andalso *pBad = 32 then print "ok" 'this would work fine if pBad and *pBad =...