Of course, nothing will stop someone extremely motivated – hopefully, not even my less encouraging replies, or this blog post. ![]() Learning how to program, even in a “easy” language and common platform, can be overwhelming for a programmer that is used to higher-level programming, learning the Prizm, a poorly documented platform with a small developer community, can be overwhelming combine learning how to program with learning a poorly documented embedded system, and it will most likely be very overwhelming. Anyway, I already wrote a post on my programming experience – it needs updating, but it should do. I’m glad my first contact with programming was through sloppy Visual Basic code. However, I do hope it’s for the best, and that these people will still learn programming – just not by developing add-ins! Had my first contact with programming been through Prizm add-in development, most certainly I would have chosen other career path than computer engineering. I usually end up saying that learning programming using the Prizm it’s a bad idea, probably coming across as extremely discouraging. It certainly helped that I had some previous experience with programming in other languages, even if it was just sloppy code, but I don’t have much of an idea of what to say to someone who intends to learn programming using the Prizm. When I started developing add-ins for the Prizm, I had little to no knowledge of the C programming language, and yet, despite the fact that add-ins can’t make use of all the stuff “normal” C programs can (the libc provided by libfxcg is incomplete the filesystem uses a different API, there’s no threading, the stack is giant compared to the heap, etc.), I managed to learn it. Why are these messages annoying? Because I don’t really know how to answer. ![]() Most annoyingly, I also get messages about Prizm development, usually about how to start making add-ins. Because of this, once in a while I still get messages about my add-ins, which I’m happy to support when possible. A few years ago, I was very active in the Casio Prizm development community, having developed three notable add-ins, contributed to the Prizm wiki, libfxcg ( my fork), and even done a bit of reverse-engineering (the calculator OS is closed-source and there is no official SDK), that resulted in the discovery of a couple of syscalls and more detailed documentation on some other ones.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |