InFloyd Programming LanguagebyMarcus Zetterquist·Jun 11, 2019ERRORS, COMPOSITION & NOT GOING CRAZY(PART 2)This is part 2. Here is part 2.
InFloyd Programming LanguagebyMarcus Zetterquist·Jun 11, 2019ERRORS, COMPOSITION & NOT GOING CRAZY (PART 1)I’m researching error handling for the programming language Floyd. https://github.com/marcusz/Floyd (check it out!)A response icon2A response icon2
InFloyd Programming LanguagebyMarcus Zetterquist·Mar 19, 2019Which code is faster? Part 3MY EXPECTATIONS VS REALITY
InFloyd Programming LanguagebyMarcus Zetterquist·Mar 16, 2019Which code is faster? Part 2Disclaimer: If you find errors, don’t just laugh — please help me understand. I want to get this right.
InFloyd Programming LanguagebyMarcus Zetterquist·Mar 15, 2019Which code is faster?Both functions read and sum 32 MB of data, enough data to force CPU to miss all caches and read from main RAM. Using Google Benchmark to…A response icon1A response icon1
InFloyd Programming LanguagebyMarcus Zetterquist·Feb 21, 2019Think about memory accesses, not instructions, when optimising codeMain memory on modern processors is extremely slow compared to the number crunching they can do.
InFloyd Programming LanguagebyMarcus Zetterquist·Feb 18, 2019Floyd programming languageToday I released my hobby project, the programming language Floyd, on github. It’s an alpha version but it’s quite robust and has most…