Fr0sT.Brutal

Any crypto library should have strong PRNG

Just add "Other", profit 🙂

Looks like you have an idea for your N+1-th project. Use AI, ML and neuronets there 🙂

IIRC Help'n'doc are constantly PR-ing themselves here in "3rd party" section though they even don't have native Pascal parser.

IDK and I don't dare to go further into that cave of madness %-) there be monsters!

OTOH, some old-school C functions are another edge of insanity. itoa? strstr?? And the absolute winner - printf, fprintf, sprintf, snprintf, printf_s, fprintf_s, sprintf_s, snprintf_s, _sprintf_l, swprintf, _swprintf_l, __swprintf_l, sprintf_s, _sprintf_s_l, swprintf_s, _swprintf_s_l, _sprintf_p, _sprintf_p_l, _swprintf_p, _swprintf_p_l, vsprintf, _vsprintf_l, vswprintf, _vswprintf_l, __vswprintf_l, vsprintf_s, _vsprintf_s_l, vswprintf_s, _vswprintf_s_l, _vsprintf_p, _vsprintf_p_l, _vswprintf_p, _vswprintf_p_l, vsnprintf, _vsnprintf, _vsnprintf_l, _vsnwprintf, _vsnwprintf_l, vsnprintf_s, _vsnprintf_s, _vsnprintf_s_l, _vsnwprintf_s, _vsnwprintf_s_l, WTFPRINTF!!!

Nothing will beat IncludeTrailingPathDelimiter

Thanks, I didn't know that. It was opensourced so anyone could try to build it for newest versions

That's weird BTW - IDE seems to run compiler as standalone EXE so it should not eat memory itself. And compiler is 64-bit so it must be able to allocate as much memory as possible including swap. Just don't use them if you don't need

@Dany Marmur gentleness and diplomacy of 80 lvl! 🙂

Ok, I got your point. Full source files, fine

You have just insulted all otaku's down to the deep of the heart xD kawaii manga girls have nothing common with that synthetic model of a human xD

Very interesting. How large your project is? Regarding the subject, you could also split your bucket of units into several projects and build them one after all. Anyway, if it's possible, I'd recommend considering extracting some units into separate subprojects that will be built independently; main project would use their DCU's without rebuilding.

Trying to build latest "ICS V8.67 - Part 2" for Debian. Besides several "stream.Seek"'s that I fixed the most serious issue is that "kqueue" is used for message loop which is only available at *BSD. This topic recommends using epoll instead or some 3rd-party lib.

Why validate email at all? If you need it valid and active, send confirmation code. Otherwise let it go. "aa@bb.cc" is totally valid but as useless as "weufbowkef". I use this one frequently when a site that I found just now and unlikely will visit again requires my email for some unclear reasons.

Doing things right is always a better option. But when it's too hard, only some ugly methods could help - but one has to understand what they're doing.

This feature took them 20 years and it still has drawbacks. If they've implemented aliases from the beginning, no troubles with with would happen ever

Well, it's not the App.PM's fault, it's the misuse. You just run a continuous loop which could iterate millions times per second if there's no messages in the queue. Surely it eats up CPU time and other operations get slower. What happens if you uncomment that Sleep? BTW, each additional connect you run adds one more nested loop with App.PM=>Button.OnClick=>Connect thus the call stack grows.

You already set length to 0 on decode error. BTW, there's a catch in dynamic Result regarding performance. They have their previous state when entering a function so the array could be allocated already. When you call SetLength, and if FastMM decides the array must be reallocated (as it reserves some space after the end), it copies full contents of an old array to a new one. Which is useless anyway. OTOH, disposing the old array by setting length to 0 could also slow thing down because then allocation will happen at every call. Depending on how intensive the function call is, you might want to re-use the array without truncating its length and just return how much decoded data it contains.

IMHO Borland should've borrowed alias construction from SQL (select Foo as f, Bar as b ...) like this: with some.long.long.nested.object as foo do foo.bar := laz

IOW, optimal distribution would be not AB CD where each letter is a fragment of an image to process by a thread but ?

Of course absolutely no. Evil Russian hackers will drain all of your bitcoins in seconds just between faking US votes and drinking vodka with their bears

Ensures x64-safe typecasts in 6 units of old demos. Note: Francois' name in unit headers got damaged by Git patch generator though the commit didn't contain that change. Must be reverted manually 0001-Samples-change-unsafe-Integer-Pointer-typecasts-to-W.patch

Only Apple has the exclusive right to track you and sell this data xD

IDK, that's a mystery that evil KGB hides from public but most of restrictions were removed long ago, just requirement of wearing masks and gloves in public transport remain.