Aug-28-2019, 07:09 PM
i've done so much programming in assembly and C, where nothing to very little was available as tools (i did write a lot of my own) that doing things myself, without such tools, is just "second nature" to me. without argument parsing tools, i just wrote loops in a few hundred projects. with C there was getopt() and i started in C using it. but it could not do what i had already decided doing based on my experience with commands. even today, i write commands that "figure out" arguments and configuration "in context" rather than depend on lots of specific options, where i can. for example, in cloud programming, i have a big script that understands dozens of possible meanings of argument strings. if the string matches one of the region names, then i know a region was named. it does not need a "--region" option or need to be in a specific position. command line and config file parsing is something i have handled a lot and now can do very well. for Python, though, i have changed how i do config files: i read in the whole file, pass it to exec() with an empty dictionary, and use whatever it put in there.
Tradition is peer pressure from dead people
What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.
What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.