Comments by "Anony Mousse" (@anon_y_mousse) on "LaurieWired" channel.

  1. Are you writing a PS1 emulator to aid with disassembly? If not, I'd advise you to start there, because you could step through the code as it's running. If you don't want to write one yourself, then consider using one of the numerous open source PS1 emulators as a starting point. I would recommend PCSX-ReARMed, as I found its source code rather easy to navigate when I used it on my Raspberry Pi and had to modify it to work with my controller.
    4
  2. In idiomatic modern C++, you shouldn't manually allocate memory at all. Better to either use std::vector if you want dynamic storage, or std::array to allocate on the stack. Calling to an allocator to store a single item is rather unconventional too. C doesn't require you to cast a void pointer to any other pointer type when assigning, and you should have mentioned that if someone wants the data to be initialized upon allocating, that they could use calloc() instead of malloc(). Of course, if you really need to manually allocate, you can still use all of the standard C functions in C++ and assembly, and in C++ you would need to cast the output of malloc(). Also, you can call `gcc` to both assemble and link, since you're using `as` anyway.
    3
  3. I like to name things with synonyms when I have to write interface code between languages. Since both C++ and Java use `this`, I would've gone with the Pythonic `self`. This whole video makes me think I should write a code generator for my language to target the JVM.
    3
  4. More programmers need to learn how to properly handle concurrency. I see far too many bugs in code all over the place when it comes to concurrency.
    2
  5. This is pretty funny. Obviously you didn't include C in the list of languages because it would've trounced everything else. Although, I do wonder why you'd include a singular point test in the loop to print the entire array. Just print each number with a space before it and be done. If you don't like unnecessary spaces, then print the first alone, then loop on 1-N.
    2
  6. My favorite is still Banks' entry from 1998. Shaped like an airplane and it's a primitive flight sim. Although, not all of the entries will still compile on modern computers. Take for instance some of the older ones that did code injection on PDP's and the like.
    2
  7. Makes me wonder if I ever worked with you. Did your colleague also close functions by sorting in the exact opposite direction? Christmas tree to open, inverted Christmas tree to close?
    2
  8. You should implement it non-recursively, especially since you can't use division on ARM. Well, in general you should avoid recursion anyway, especially as it can blow the stack. Only question I've got is what color scheme are you using for Vim on your Pi?
    1
  9. The only issue I have is with your pronunciation of contiguous. Otherwise good video and nice 60's aesthetic.
    1