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...

I would probably recommend just doing :

Well, the immediate backend is now generally GCC, which produces the bad asm.. It might be worth saying, a relatively unobtrusive workaround that allows you to keep the SS name is to #define SS as something else. If you have more of them, you can stash them away in an #include somewhere. Just bear i...

I'm not an expert, but it seems to be a pretty fundamental problem in the masm intel syntax. It's easily shown with a simple program in GCC: // compile with gcc -masm intel int ss(){ } /tmp/ccOC4unv.s: Assembler messages: /tmp/ccOC4unv.s: Error: .size expression for ss does not evaluate to a constan...

Sorry, I was trying something with the .htaccess. Logins should work again now.

I occasionally search for (recent) mentions of FPC and Lazarus to comment on. I just did, and I only get results from 2005. Seems the search is working, but just got its database restored to the very beginnings ;-) Ah, I started a rebuild, but apparently if I close the page the rebuild stops. Perha...

Bit of a kludge, but you can enable highlighting on a forum page with the hilit= URL parameter.

e.g. viewtopic.php?f=17&t=28726&hilit=search

I'll try recreating the search index. See if that fixes it.
Otherwise, I guess you're probably stuck with your usual search engine of choice..