Quote:
Originally Posted by AtomicDryad
Personally I don't think eliminating function prefixes is worth additional requirements.
|
It's really a very difficult problem: finding the right balance between the added deployment charge of upped requirements and the reduced coding charge these new versions allow. With my own work projects, I'm very lucky in that I can control everything from server installations to client deployment, so I don't have to worry about that balance. But you're right; in this project, coding comfort lose charge of against additional requirements. This is unfortunate for the programmers, but good news for users who can't or don't want to upgrade.
Quote:
Originally Posted by AtomicDryad
I also fail to see the problem with -limited- global variables such as $CONFIG and $opt nested hashes (in runtime, cfg loading is another matter). KISS FTW.
|
Well, there's nothing
wrong per se, it's really just a matter of code structure and maintainability. We could, in a functionality standpoint, stay with global variables; the script would technically still work just as well. But since we're going the OO route, it makes sense, structurally, to also make those into objects.
It also has relatively bad effects (
http://en.wikipedia.org/wiki/Global_variable) in certain situations, but this project is still small enough that we don't really have to care about that. Unless FLAG continues to grow in functionality and complexity, in which case globals can become a hindrance rather than a help (that's my real-life experience about such things).
Quote:
Originally Posted by AtomicDryad
I'll take a look at the github discussion when I get home tuesday. I'll also have a r29mod ready which will support drop-in source modules, with one that grabs stories from forum.spacebattles.com :P
|
Spacebattles.com? The name itself is made of win. I'm gonna
have to check this one out.
N.