ZealOS/docs/Doc/CutCorners.DD.html

59 lines
4.8 KiB
HTML
Raw Normal View History

2021-07-03 05:07:57 +01:00
<!DOCTYPE HTML>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=US-ASCII">
<meta name="generator" content="ZealOS V0.11">
2021-07-03 05:07:57 +01:00
<style type="text/css">
body {background-color:#fef1f0;}
.cF0{color:#000000;background-color:#fef1f0;}
.cF1{color:#0148a4;background-color:#fef1f0;}
.cF2{color:#3b7901;background-color:#fef1f0;}
.cF3{color:#057c7e;background-color:#fef1f0;}
.cF4{color:#bb2020;background-color:#fef1f0;}
.cF5{color:#9e42ae;background-color:#fef1f0;}
.cF6{color:#b57901;background-color:#fef1f0;}
.cF7{color:#b2b6af;background-color:#fef1f0;}
.cF8{color:#555753;background-color:#fef1f0;}
.cF9{color:#678fbb;background-color:#fef1f0;}
.cFA{color:#82bc49;background-color:#fef1f0;}
.cFB{color:#0097a2;background-color:#fef1f0;}
.cFC{color:#e26a6a;background-color:#fef1f0;}
.cFD{color:#c671bc;background-color:#fef1f0;}
.cFE{color:#c7ab00;background-color:#fef1f0;}
.cFF{color:#fef1f0;background-color:#fef1f0;}
2021-07-03 05:07:57 +01:00
</style>
</head>
<body>
<pre style="font-family:monospace;font-size:12pt">
<a name="l1"></a><span class=cF5> Cut Corners
2021-07-03 05:07:57 +01:00
<a name="l2"></a></span><span class=cF0>
<a name="l3"></a>There are a few places where corners are cut in the interest of not junking-up code. This is part of the ZealOS mentality.
<a name="l4"></a>Try not to let stupid legacy compatibility issues enter and junk-up ZealOS.
<a name="l5"></a>
<a name="l6"></a>* The type-casting operator was made post-fix because it makes the compiler way cleaner.
<a name="l7"></a>
<a name="l8"></a>* ZealOS does not figure-out </span><span class=cF2>FAT32</span><span class=cF0> short name alias numbers. </span><a href="https://zeal-operating-system.github.io/ZealOS/Kernel/BlkDev/FileSysFAT.CC.html#l646"><span class=cF4>FAT32DirNew</span></a><span class=cF0>(). It can cause hard drive corruption, so it
<a name="l9"></a>might have to do it eventually. It would really take a lot of junky code for this hatefully, detestable, legacy issue.
<a name="l10"></a>&quot;Please don't make us ruin the beautiful shiny-new ZealOS with that!&quot; </span><span class=cF2>FAT32</span><span class=cF0> is also unappealing because it is in patent
<a name="l11"></a>limbo. </span><span class=cF2>FAT32</span><span class=cF0> might get removed from ZealOS. There is the </span><a href="https://zeal-operating-system.github.io/ZealOS/Doc/RedSea.DD.html#l1"><span class=cF4>RedSea</span></a><span class=cF0> 64-bit file system that works perfectly well. </span><span class=cF2>FAT32</span><span class=cF0> is
<a name="l12"></a>useful, however, because it assists in transferring between dual booted operating systems.
2021-07-03 05:07:57 +01:00
<a name="l13"></a>
<a name="l14"></a>* The </span><a href="https://zeal-operating-system.github.io/ZealOS/Compiler/OpCodes.DD.html#l1"><span class=cF4>asm opcodes</span></a><span class=cF0> names were changed to remove the ambiguity between insts with different numbers of arguments, making the </span><span class=cF4>
<a name="l15"></a></span><a href="https://zeal-operating-system.github.io/ZealOS/Compiler/Asm.CC.html#l1"><span class=cF4>assembler</span></a><span class=cF0> simpler and minimal 16-bit asm support was done, since 64-bit is what you should be using, unless you're doing a </span><span class=cF4>
<a name="l16"></a></span><a href="https://zeal-operating-system.github.io/ZealOS/System/Boot/BootDVD.CC.html#l1"><span class=cF4>boot loader</span></a><span class=cF0>.
2021-07-03 05:07:57 +01:00
<a name="l17"></a>
<a name="l18"></a>* There are no user-controlled file-sharing locks. However, the drive and file system have locks and concurrent operations
2021-07-03 05:07:57 +01:00
<a name="l19"></a>should be fine.
<a name="l20"></a>
<a name="l21"></a>* A hidden window is never refreshed. Certain tasks are never done, therefore. During refresh, the entry count limit of the
<a name="l22"></a>document buffer is, normally, checked and enforced. If you print to the command-line in a task whose window is covered, no
<a name="l23"></a>limit on buffer exists and it will alloc memory for the document buffer until the system runs out of memory and crashes.
<a name="l24"></a>
<a name="l25"></a>* Even if a local function variable is declared less than 64 bits, the compiler does calculations with 64-bit.
<a name="l26"></a>
<a name="l27"></a>* </span><a href="https://zeal-operating-system.github.io/ZealOS/Doc/Print.DD.html#l1"><span class=cF4>Print</span></a><span class=cF0>() uses </span><a href="https://zeal-operating-system.github.io/ZealOS/Kernel/StrPrint.CC.html#l249"><span class=cF4>StrPrintJoin</span></a><span class=cF0>(). You cannot use vastly over-sized fields for %f.
2021-07-03 05:07:57 +01:00
<a name="l28"></a>
<a name="l29"></a>* </span><a href="https://zeal-operating-system.github.io/ZealOS/System/Gr/GrPrimatives.CC.html#l1018"><span class=cF4>GrEllipse3</span></a><span class=cF0>() is broken on transformations.
2021-07-03 05:07:57 +01:00
<a name="l30"></a> </span></pre></body>
</html>