Probably the -Ofast (GCC optimizer setting).
Recomendations are: for 'production code' -O2 (no more is considered safe!)
(as stated on GCC's site)

Nice explanation but ... don't know how many here, are understanding ASM ?!?
(suppose probably less than 10% of all members)

Since certain devices require it, to use BCD formatted UBytes, this two #Define(s) might come in handy, to solve communication problems, with such devices. #Define setBCD(v) converts from: base 16 to: base 10 (v = Decimal/Hex) #Define getBCD(v) converts from: base 10 to: base 16 (v =...

Dinosaur wrote:By the way, what made you say that

SD2405 seems to be "discontinued".

The web-site pointed to by my search engine (DDG).
Maybe, just related to their own product ?
Btw: that's where I've got the datasheet from ...

So my problem is not converting 20 to hex, but putting 20 hex to represent 20 decimal. OK, now I hopefully understand, what you seemingly need. Try the below code: ' toBCD_Mac.bas -- (c) 2020-07-02, MrSwiss ' ' compile: -s console ' #Define toBCD(v) ( CUByte( (v) \ 10 Shl 4 + (v) Mod 10 ) ) Dim As ...

More on BCD encoding is found in: Section: Tips & Tricks Titled: Union as 'own' data-type URL: https://www.freebasic.net/forum/viewtopic.php?f=7&t=27450 This just to give an idea of, how to deal with it ... (it just does one UByte at the time) You might have to extend it for your specific ne...

@Dinosaur, seems to me, that you've misunderstood what's written in the Docs, of the device. The encoding isn't, as you assumed in HEX, but in BCD (binary coded decimal). 5.2 Real Time Clock Registers [00h to 06h] These RTC (Realtimeclock) registers are stored as binary-coded decimal BCD format. Sec...

Nothing new under the sun:
M$ is still (always did it) using its userbase, as beta testers ...

Btw: those that haven't taken control of their OS themselfs by now,
by wresting it forcefully back from M$, can only be pityed.

Which clashes with other header definitions (the Windows headers, no less). Nope, nothing to do with headers (the TRUE/FALSE issue) it is FBC related. It's a change in FBC itself: OK, up to and including version: 1.03.0 From version: 1.04.0 (introduction of Boolean type into FBC) it must be removed...

srvaldez wrote:I don't know what's going on, no binaries, maybe this will work

Maybe just your virus-scanner interfering ...
(try with it switched OFF, for the test)

I'd suggest to use FBC 64 bit, whenever you are on a 64 bit operating system. The advantage is: the 32 bit emulator (WoW on WIN) isn't needed, at all. Typically: consumes more RAM and possibly, slows down execution speed. From my point of view, the 32 bit version, is only good for legacy 32 bit OS's...

I don't know LUA. LUA is a script interpreter, made by the same people that did IUP. Because of that, they integrate very well with each other (both by: PUC-RIO). Is parsing B1 to a value from the table something that LUA simply knows how to do, or is that something I would have to code? Yes, you'l...

[edit]as requested by Moderator: @badidea, infringing on copyright is against forum rules and therefore, discouraged. See: Forum/Beginners/Welcome to the forum, by counting_pine especially this section: In addition, we expect you to follow all the rules set out by our host, phatcode.net, including: ...

Sorry, don't understand the question (the library name itself, is the same for both versions).

ld: skipping incompatible /usr/lib/x86_64-linux-gnu/liballeg.so when searching for -lalleg ld: cannot find -lalleg First message: liballeg.so is found but, the bitness of it is wrong for the used compiler. Second message: simply states, "the right library" was not found (other bitness). S...