TempleOSCDV4.12.ISO

Doc/Strategy.DD

@@ -4,7 +4,7 @@ Everybody is obsessed, Jedi mind-tricked, by the notion that when you scale-up,
 
 I limited it to 100,000 lines of code, forever!  I never need a linker or make utility and I can use small labels.
 
-People mock Bill Gates for, "640K should be enough."  I say, "2 Gig for code should be enough."  The same people who mock Bill Gates are probably just like the black woman who sued for a trillion dollars.
+People mock Bill Gates for, "640K should be enough."  I say, "2Gig for code should be enough."  The same people who mock Bill Gates are probably just like the black woman who sued for a trillion dollars.
 
 My Dad worked on converting the Titan missile to the Gemini Mission rocket.  It had to be "man-rated".  You can bet that everything got an order of magnitude more complexity and documentation.  My vision is a souped-up C64, not a 1970's mainframe; a kayak, not a Titanic.
 
@@ -32,7 +32,7 @@ A three button mouse is like a leg you cannot put weight on.  TempleOS just does
 
 * Least (greatest) common denominator hardware support.  Mostly, one driver for each device class.  I can't be in the business of different drivers.  Compatibility is the greatest challenge for PC operating systems.  Disk code does not use interrupts, avoiding compatibility risks.  $FG,2$PS/2$FG$ keyboard/mouse is used instead of $FG,2$USB$FG$, also more compatible.
 
-* $FG,2$640x480$FG$ 16 colors.  Updates whole screen at $FG,2$30 fps$FG$, optimized for full screen games where $FG,2$InvalidRectangle$FG$s are counter-productive.
+* $FG,2$640x480$FG$ 16 colors.  Updates whole scrn at $FG,2$30 fps$FG$, optimized for full scrn games where $FG,2$InvalidRectangle$FG$s are counter-productive.
 
 * One font, 8x8.  Text and graphic layers done in software with text normally on an 8x8 grid.  It can run in Text mode if graphic initialization fails.
 
@@ -58,6 +58,6 @@ A three button mouse is like a leg you cannot put weight on.  TempleOS just does
 
 * All tasks have a heap and a sym table.  Scope is that of environment vars in other operating systems.  As text is typed at the command line or you run programs by $FG,2$#include$FG$ing them, the syms go in the table.  If a sym is not found, the parent task's table is checked.  The father of all tasks has the API syms you'll need waiting in it's table.  No need to $FG,2$#include$FG$ headers.
 
-* No need for namespaces -- scoping occurs automatically based on task symbol table hierarchy with the $FG,2$Adam task$FG$'s symbol system-wide global.
+* No need for namespaces -- scoping occurs automatically based on task symbol table hierarchy with the $LK,"Adam Task",A="FF:::/Doc/Glossary.DD,Adam Task"$$FG$'s symbol system-wide global.
 
 * Sometimes, I $LK,"cut corners",A="FI:::/Doc/CutCorners.DD"$ in the interest of keeping the code beautiful.