Argument parsin in python seems to add a level of complexity compared to that of c++. In c++, one only needs to define the argument vector and the arguments are already stored in the vector. They can be easily accessed without some sort of extra STL library. On the other hand, python requires the use of the argparse module which is interesting. One would assume that it would be like c++ and allow for easy access to the given arguments. I think it’s safe to assume that argument parsing is used widely enough to justify auto inclusion of the argparse module.
Then again, it does allow you to be completely customizable with the python program. I guess that if you’re not going to be parsing arguments, having the argparse module would be pointless and possibly slow down the program. I guess this fits in more with the Unix design philosophy.
While this post doesn’t really pertain to ECE 2524 as much, it relates to linux software development. I just finished up making my first project on a linux platform using Qt for my 3574 class. My first thoughts? Not good at all. I was writing code without a debugger and it was terrible. I spent way more time debugging than actually writing the main parts of the code. At least in visual studio they give you little hints on what could be wrong when you build.
I used the simple gedit editor to create my files. I didn’t think I really needed something too fancy and I think gedit served me pretty well for what it is. Also, the experience of software development on Windows and Linux is completely different. In Windows, I usually used visual studio to build, compile, and execute my code. On Linux, none of that exists. It’s just basic command line and text editor. Nothing fancy at all. This has its ups and downs. Yea you don’t get the extra tools that would help you alot, but programming in linux feels alot cleaner and simpler.