[-] Remove notepad.txt notes feelsbadman

Include/Aurora/Loop/nnnnn.txt

@@ -1,69 +0,0 @@
-WaitMultipleWayland
-    WaitMultipleFd
-WaitMultipleGlib
-    WaitMultipleFd
-    + other hacks
-WaitMultipleX11
-    WaitMultipleFd
-WaitMultipleFd
-    win: cast to handle, queue handle
-    bsd: queue kqueue source
-    linux: queue poll poll
-WaitMultipleAsync
-    all: WaitMultipleSemaphore
-WaitMultipleWin32
-    win: switch to MsgWait...
-    others: n/a
-WaitMultipleApple
-    mac: hijack mainloop, add kqueue sources
-    others: n/a
-WaitMultipleTimer
-    bsd: queue kqueue source
-    linux: timerfd_create
-    win32: CreateTimer
-WaitMultipleSemaphore
-    win32: CreateSemaphore
-    linux: eventfd semaphore
-    bsd: 
-          mutex (as in, au primitive mutex) lock non-blocking reads
-          pipe
-WaitMultipleMutex
-    win32: CreateMutex
-    linux + bsd: WaitMultipleSemaphore
-WaitMultipleAIO
-    win32: waitmultiple
-    bsd/posix: select
-    linux: switch over to io_submit, IOCB_CMD_PREAD for fds
-
-
-IPCSemaphore:
-    linux: eventfd semaphore
-    win32: CreateSemaphore
-    bsd: 
-        shm spinlock  -> Does this require a security note? 
-                         I guess we could trust people in our user session
-                         Having a page one could write 1 across seems more exploitable than 
-                          named pipes, semaphores, and mutexes, but it doesn't seem to reduce
-                          the required scope of attack, so it doesnt really matter 
-           protected pipe
-IPCMutex
-    win32: CreateMutex
-    linux + bsd: IPCSemaphore
-
-IPCCV:
-    all: ipcsemaphore
-    
-IPCServer
-     win32: CreatePipe
-     posix: pipe
-     
-     
-     
-class ILoopSourceEx : public ILoopSource
-{
-public:
-    virtual void   OnPresleep() = 0;
-    virtual bool   OnTrigger(AuUInt handle, bool atomicSignal) = 0;
-    virtual void   OnFinishSleep() = 0;
-    virtual AuList<AuUInt> GetHandle() = 0;
-};