Need some advice on CLI design, I need to provide simple but powerful command line options
I am writing a utility that runs on RHEL5 command line. I need my command line options to be simple but powerful. I looked at the various UNIX utilities to get an idea of how simple command line utilities have to be. Do you guys suggest any documents/links that talk about command line etiquette? I am modelling my utility on top of LVM (that’s all the info I can give for now). I know it’s a software engineering question, but I thought it would be appropriate to post here. Please advise….
Few big libraries or many small libraries?
Over the course of some months I’ve created a little framework for game development that I currently include in all of my projects.
What is ServletUtilities?
The answer in this question suggests creating a ServletUtilities class to handle text conversion between Java strings and XML text.
What is ServletUtilities?
The answer in this question suggests creating a ServletUtilities class to handle text conversion between Java strings and XML text.
Static console object or dependency injection?
For a current project I have created a Console class which wraps up C++’s usual cout, writes output to a file or uses Console::WriteLine depending on the environment. Currently I’ve setup my code base to inject a console object into each class that I use, making all of them extend a base class: Debuggable. This seemed like a great plan at first but now that I have to pass the console to every object and ensure that it is created before all of them I’m having second thoughts.
Static console object or dependency injection?
For a current project I have created a Console class which wraps up C++’s usual cout, writes output to a file or uses Console::WriteLine depending on the environment. Currently I’ve setup my code base to inject a console object into each class that I use, making all of them extend a base class: Debuggable. This seemed like a great plan at first but now that I have to pass the console to every object and ensure that it is created before all of them I’m having second thoughts.
How small is too small for a library or package?
Background I came across this question about whether few big libraries, or many small libraries is better. I tend to agree with the accepted answer, that many small libraries is better. However, since there is some overhead with creating and referencing a library, I came to wonder, how small is too small? Questions Are there […]