Project

General

Profile

Actions

Bug #26

open

Commands options not well propagated, when declared within an OvalFile

Added by Chamont David almost 13 years ago.

Status:
New
Priority:
Low
Assigned To:
Category:
Implementation
Start date:
02/16/2009
Due date:
% Done:

0%

Estimated time:

Description

Intro: so to ensure user interface and commands consistency, each single feature is implemented in a single command, and when a command needs another command feature, it is internally instanciating this command and use it. Behind this nice concept, since the internal command is not instanciated in the same way as the main command, we must propagate to it some "fake command line" options, and fakely calls its functions, as would do the main oval framework with the top level command. This fake calls are not done automatically, but case by case and "by hand" by the top command. This is why there could be and there is some
errors or awkward situation.

The general bug: in the current implementation, when a commmand option is set within an OvalFile, it is not
correctly propagated to the internals commands.

Example: if I set "-sh" for the runtime command, it will not be propagated to "environnement" command, and the
resulting output will be a mix of csh and sh commands.

Solution: review the use of internal commands, and the way they are managed, so that they are in the same state if they are instanciated as user commands or as internal commands.

No data to display

Actions

Also available in: Atom PDF