Hi Paul,
I downloaded FireFly for FreeBasic, FreeBasic 32 bits and FreeBasic 64 bits.
I installed FreeBasic 32 bits in a folder called FreeBasic32 and FreeBasic 64 bits in a folder called FreeBasic64.
When I decide to change which compiler to use (32 bits or 64 bits), I update the path to the compiler in Tools -> Environment Options -> FreeBASIC Windows.
Is there a more convenient way to switch from 32 bits compiler to 64 compiler (or vice versa) for a project ?
Thanks for this FreeBasic version of FireFly; I feel more confident for the future with this new version of FireFly.
Regards,
Jean-Pierre
Hi Jean-Pierre,
You are correct. Currently you need to change the compiler location.
Soon I will add multiple fields where you can enter the 32 and 64 bit versions separately. This will make it much easier to create projects using both compilers.
Hi Paul,
Thanks for the FireFly for FreeBasic update FB_372_1.rar.
Switching from 32 bits to 64 bits (and vice-versa) is now very easy and works perfectly.
Thanks a lot.
Jean-Pierre
Paul,
I have not revisited FreeBasic coding in a while and my memory gets worse every day.
How do/would you handle Integers being 64bit in a 64bit app, when writing code that needs to be compiled for both 32/64.
If I remember my first forray correctly this was a MAJOR issue when porting old code to 64bit.
James
Hi James, I am not an expert in this area by any stretch of the imagination but it is my understanding that it is the INTEGER and UINTEGER data types in FB are the only data types that change size depending on 32 or 64 platforms. If I need a pure 64 bit only data type that is always 64 bits no matter what platform, then I would use the LONGINT and ULONGINT data types.
I am still scratching my head why would dkl changed those.
They are both 32 bit in 64bit apps created with all other 64 bit compilers I've used.
The only actual data types changed to 64 bit are pointers.
James