Command line or graphics or both?

/wiki/KeyPgInput
It might depend on the platform or possibly whether its command line or graphics. I can’t check currently..

There probably aren’t many people running FBIDE under Linux.
Does top indicate that the memory is being consumed by any other process?

Your example (with small fixes so it compiles) should, unless I’m mistaken, write 8 bytes of data (the size of a ulongint) to the start of the file. Is that what you’re seeing? You should be about to write an exact number of bytes in Binary mode with something like: Put #f, , *cast(ubyte ptr, p&...

Bear in mind that FBIDE has not seen any development for a long, long time, so anything you report is very unlikely to ever be fixed..
If you can verify that FBIDE itself is hogging the memory, then you should be able to Kill the process to free up the memory without logging out.

How are you running FBIDE through Linux? Is this through Wine, or some kind of native build? Perhaps the programs are not finishing properly. This might happen if you had Sleep at the end, but the program wasn’t showing in a console. If you run 'ps aux' in a terminal, you might see lots of copies of...

EDIT: I was thinking PNG compression is loseless but on the forum the normalized rgb 2D sphere has a ellipse inside but not if I run it on the monitor at home. May be the result of a fast png decompresser from firefox I will compare it with an other browser. Do you see the ellipse also ? Joshy EDIT...

fatman2021 wrote:You do realize that C has a perfectly good switch statement you can use? Why don't you use it? What is with all the spaghetti code?

fatman2021, please explain, what is your comment in reference to?
Who is it directed at?
Is it a response to a prior post?
How was the code you gave generated?

The other problem with over-documentation is that any changes to documented functions will potentially cause breakages for people who have come to rely on those functions. So it imposes more rigidity on the internal structure of the code, or risks breaking trust with developers, or requires them to ...

What I find slightly worrying is that Gcc produces a different result. Not in terms of timings but the array looks different... I'd call it a bug unless there is a more convincing explanation. If the code causes undefined behaviour , then different results can both be valid. I believe the results o...

Wow, just seen these - looks amazing. They should make for some very powerful macros..

Of the top of my head: ImageInfo should be dialect agnostic, although the headers it’s likely to see differ for different dialects. Version differences may refer to the byref parameters? They may have once been Integer but changed to Long, or overloaded, or something. I can’t really remember. Rem: t...

What if the '-lang fb' lexer precluded the very possibility of suffixes - particularly '$' - by including those symbols within the variable name? e.g. dim a$b$c as integer . Then in order to support legacy functions, it's just a matter of making sure both forms (e.g. mid and mid$ ) are registered a...

Under fbc's hood, the lexer expects identifiers to possibly have suffixes so it reads suffixes. But out of the 800+ places in the parser where a decision should be made about suffixes, only about 5 places are handled, often resulting in an error. My personal preference is that '-lang fb' be suffix ...

#define uses simple text replacement, which can have some weird effects because they don't respect operator precedence. const as ubyte bit1 = 1, bit2 = 2, bit3 = 4 const ComboBits = bit1+bit2+bit3 ' = 7 #define ComboBitsDefine bit1+bit2+bit3 print ComboBits*3 ' = 21 print ComboBitsDefine*3 ' = 15? I...