Andy Green andygreen1

## readme.md

      
              1 file
            
          
              3 forks
            
          
              11 comments
            
          
              83 stars
            
          
                josefnpat
                / readme.md
            
            
              Last active
              May 26, 2024 09:00
            
              
                Going from Lua 5.2 to PICO-8's Lua
              
          
    This information applies to the PICO-8 0.1.6 release.
This document is here to help folks with a proficiency in Lua understand the limitations and discrepencies between Lua and PICO-8's Lua.
You can always view the manual or yellowafterlife's extended 0.1.1 manual.
General


anything written in uppercase the PICO-8 editor or .p8 is made lowercase by the editor. → editing the .p8 file directly can work
print(function() end) outputs the string function instead of the string function: 0x0000000.


## Memory, Cache, CPU optimization resources.md

      
              1 file
            
          
              54 forks
            
          
              12 comments
            
          
              332 stars
            
          
                ocornut
                / Memory, Cache, CPU optimization resources.md
            
            
              Last active
              June 7, 2024 00:05
            
          
    Memory Optimization (Christer Ericson, GDC 2003)

http://realtimecollisiondetection.net/pubs/GDC03_Ericson_Memory_Optimization.ppt
Cache coherency primer (Fabian Giesen)

https://fgiesen.wordpress.com/2014/07/07/cache-coherency/
Code Clinic 2015: How to Write Code the Compiler Can Actually Optimize (Mike Acton)

http://gdcvault.com/play/1021866/Code-Clinic-2015-How-to

  
## preprocessor_fun.h
// Just before switching jobs:
// Add one of these.
// Preferably into the same commit where you do a large merge.
//
// This started as a tweet with a joke of "C++ pro-tip: #define private public",
// and then it quickly escalated into more and more evil suggestions.
// I've tried to capture interesting suggestions here.
//
// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_,
// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant,
	// Just before switching jobs:
	// Add one of these.
	// Preferably into the same commit where you do a large merge.
	//
	// This started as a tweet with a joke of "C++ pro-tip: #define private public",
	// and then it quickly escalated into more and more evil suggestions.
	// I've tried to capture interesting suggestions here.
	//
	// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_,
	// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant,