Re: An opinion please (ordering of command parameters)

James,

Like Simon wrote, if you decide on the name of the command, you´re half way there. If you stick to the wonderfully logical system that the creators of the System 38 invented, use a three letter abbreviation for the action and another one for the object. IOW: What are you going to do? Update. What are you going to update? A foo. So the command should be UPDFOO and the name of the foo you are going to update should be the first parameter.

Joep Beckeringh


James H. H. Lampert schreef:

I'm working on a utility that will update a "application environment" library by pulling in file definitions from another environment library (the "source" library, usually a "test" version of the application environment) and applying them to the existing data in the "target" library (usually a "production" version of the product environment).

Scenario: Universal Foobar has been running the application on the environment in the FOO_PROD library for some time, but they have prepared an improved version of the database, and have been running tests on a modified version in the FOO_TEST library. They are now satisfied that the environment as defined in FOO_TEST is going to work as advertised, and want to put that version into production.

So for this utility that programmatically upgrades FOO_PROD to the new data definitions in FOO_TEST, should the command be

UPDATEFOO FOO_TEST FOO_PROD

or should it be

UPDATEFOO FOO_PROD FOO_TEST

???

--
JHHL