Re: An opurtunity for work, for only some small code!
Agreed with everyone else. No dev is going to do this. I won't go into the biases displayed with object-oriented programming in this topic (because after you learn Rust you learn quite quickly that OOp isn't everything and that most of the time its *bad*). However, you cannot make *anything* other than a guess the number game (and even that's questionable) without using any, one, or all of the following:
* OOP-based: classes, objects, interfaces, inheritance
* Functional: multimethods, prototypes, pattern matching, branching/conditions
And so on. Even if you write in a procedural language like C, your still going to use a form of OOP combined with functional programming, to a degree; you'll be passing structs around all over the place. Hell, you might want to throw in some unions too. And lots and lots and lots of pointers (or the equivalent i your language of choice). No language is ever fully complete without giving you some way of accessing raw memory (which is handy in many cases). Even rust, which encourages safety to the degree where the compiler requires you to write safe code and you have to explicitly tell it when something won't be safe, allows you to access memory. And didn't you know? Even Python lets you access memory, manually allocate/free, etc. (I wouldn't do that in Python or Rust though -- manually manage memory. Let the compiler/interpreter handle that for you.) However, poking around in memory is a very nice feature to have, and you'll use it a lot, especially in C and C++. (And did you know? In the DMPA/DMNB era, we did use memory poking/peeking functions. Several times, in fact.)
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
