Cutting Corners

There are a few places where I cut corners in the interest of not junking-up 
code.  This is part of the LoseThos mentality.  I try not to let, often stupid, 
legacy compatibility issues enter and junk-up LoseThos.

* I made my own type-casting operator, ><(type), because post-fix makes the 
compiler way cleaner and, actually, because LoseThos type-casting is more 
powerful.  It's a shame to break compatibility with C but it's way better.

* LoseThos does not figure-out FAT32 short name alias numbers.  
FAT32DirEntryNew().  It can cause hard drive corruption, so I might have to do 
it.  It would really take a lot of junky code for this hatefully, detestable, 
legacy issue.  "Please don't make me ruin my beautiful shiny-new LoseThos with 
that!"  I am also not enthused about FAT32 because it is in patent limbo.  FAT32 
might get removed from LoseThos.  There is a LoseThos native, 64-bit, file 
system that works perfectly well.  FAT32 is useful, however, because it assists 
in transferring between dual booted operating systems.

* I use Pascal argument order for cout interrupts.  PrsCout().  If I used C 
order it would look like the normal function push args.  Is it worth junking it 
up with code like this?

  CbPush(lx);
    CbOutPtrsInit(lx);
    PrsExpression(lx,NULL,FALSE);
    CbIcAdd(lx,EC_END,0,0);
    CbPush(lx);
    cnt++
  CbPop(lx);
  while (cnt--)
    CbAppend(lx,tempcbh);

* I changed the asm opcodes names to remove the ambiguity between instructions 
with different numbers of arguments, making my assembler simpler and I did 
minimal 16-bit asm support, since 64-bit is what you should be using, unless 
you're doing a boot loader.