hello Roland Chastain
one thing that is suspect when a program compiled to 64-bit has problems is Integer variables, Integer is 32-bit on FB 32-bit and 64-bit on FB 64-bit
I suggest you try search and replace Integer with either Long or Integer<32>

Hello IvanisIvan when you have problems like that it helps if you compile your program with the option -exx in freeBasic you must dimension arrays, change your dim's to DIM Counta AS INTEGER DIM Countb AS INTEGER DIM Countc AS INTEGER DIM Countd AS INTEGER DIM Namea( 0 TO 60 ) AS STRING DIM Nameb( 0...

Hi crylex the easiest way to get allegro working with FB is to use the same version as the example which is allegro-5.0.10 you can get the 32-bit binaries from https://www.allegro.cc/files/ you need to get the MinGW 4.7.0 archive ideally you would want the latest version, but the example in the FB d...

I also noticed speed differences depending on the console size
but your times are indeed very slow

@fzabkar
what vesion of FB are you using and what command options if any are you using?
also, is your computer a laptop?

here's your test with timing ' # include "vbcompat.bi" Dim row as UByte Dim col as UByte Dim sRowData As String dim as double t t=timer For row = 1 To 250 For col = 0 To 39 Print Using "##"; col Mod 10; Next col Print Next row Print timer-t Sleep t=timer For row = 1 To 250 For co...

@fzabkar
the perception of slow or fast is subjective, your test does not give a performance benchmark, say in milliseconds to completion

the 32-bit tests of libcairo works ok, I suspect that the cairo bi files are not 64-bit clean

while testing libraries produced by MXE (cross environment) https://mxe.cc/ I ran into this issue again was testing libcairo and Iczer's solution did solve the undefined symbol problem but the cairo clock would crash so tried including different msvcrt libs without Iczer's solution thinking that per...

hello softfoot you can combine both the 32 and 64-bit compilers in one directory, obviously you will need to rename fbc to something like fbc32.exe and fbc64.exe [or you could just keep the 64-bit of fbc.exe] the rest merges without conflict, for example you have the directories /lib/win32 and /lib/...

hello fzabkar
the code you provided should not cause any problems, there must be more to it that you are not revealing

like jj said, do a clean install

did you succeed in installing libtinfo5 ?
if so, then a sudo ldconfig may solve your problem

thank you Richard, very interesting :-)

what about a careless npc that leaves the key in the lock?

here's a tiny expression evaluator https://github.com/codeplea/tinyexpr before you compile tinyexpr I suggest that you un-comment #define TE_POW_FROM_RIGHT when compiled as a static library with -O2 it's about 1.75 times faster than muParser tinyexpr.bi #pragma once #inclib "tinyexpr" exte...