Stringbuilders typically do the first default, and the second if you set a capacity. Or they avoid both to simply not wrap a single block allocation, but a linked list of say <n>MB blocks that you can then write to a socket one by one. That is basically what an array does. In fact, there is rarely ...

Afaik most UEFI systems come with "secure boot" enabled that doesn't allow them to boot unsigned files. This to kill such external bootdisks as virus source. (Note: I don't say I agree with that, but that is the justification). In most systems you can turn this off in the UEFI firmware, an...

From the CPU's point of view either is equally efficient. The only reason I can think of that might favor little endian is that when reading a byte stream you can build a number while reading the bytes, stopping any time you want. It indeed requires very little CPU support, many older RISC types (l...

The problem boils down to either - marcov's StringBuilder class (several reallocations, risk to fail a HeapRealloc for large sizes) - or finding a way to know beforehand which size you need, at least approximately (requires coder to think ) Stringbuilders typically do the first default, and the sec...

This is very normal and even so common it could be considered a cross language problem. It is simply string being allocated pretty close to its (current) size, which with the next concatenation is already to small, so a reallocation and copy follows. Typical cases is generating webpages where line a...

FBC does not generated binary code. AS and LD do. And AS and LD are target (Linux,Windows,OS X etc) specific.

So you need to find (cross) binutils for the "UEFI" target, and adapt the runtime library for it.

albert wrote:Since the majority of computers on the planet , use AMD or Intel processors..

The vast majority is using network. So network order should be default :=)

dodicat wrote:"Only one endian", reminds me of a song from the sixties, but I cannot place it, I'll be trying to remember what it was all day now.
Thank you!

Maybe also a Swift's Gulliver's Travels reference? The term come from it. (and Red Dwarf did the same later with red and blue hats)

vi vi vi ... the number of the ... j/k. IIRC, "Using a free/libre vi clone isn't a sin but rather a penance." Also, "Emacs is hard on the hand, but vi is hard on the brain!" (GNU Emacs used to support vi emulation, too. VILE is actually a heavily-modified MicroEmacs.) Emacs is a...

(vi(m)/ctags) I assume you mean that regex isn't as good as a full language parser. You're right, of course, and double-checking shows Pascal support as very weak (funcs/procs only, although support is much much better for some other languages). I also want to popup only relevant identifiers on a . ...

Note that bios INT emulation alone won't cut it. Too many programs use port60-something ($66/$67?) for lowlevel kbd, and many programs do Direct Screen Writes (DSW). And then there is COM and LPT via ports for those who need it. IOW you'd need to get such peripherals (kbd,mouse,com,lpt) in the suita...

DOS is a low level OS I rather say minimalistic than lowlevel. And working through a firmware (BIOS), rather than managing the chips themselves is also not exactly lowlevel. The other OS in the same category (abstraction is done more by firmware than OS) are the older versions of Classic MacOS (say...

I think the core problem is that modern hardware is not that simple anymore.

I also worked with the FPC go32v2 textmode IDE for a while (1998-2003/4), which contrary to older stuff was fully lfn aware etc LFNs were never intended for raw MS-DOS 7, only under the GUI (Win9x) itself. MS-Dos7 was only a rescue system for win9x. So for real apps, it was never meant to run witho...