If the files are generated for known projects, headers shall be placed into appropriate include directory and implementation into appropriate source directory.
If the files are user specified, the user shall have some way to designate locations, and utility shall place appropriate files where directed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A) public default constructor
B) public copy constructor
C) public destructor
D) public assignment operator overload
E) public equality operator overload const
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A utility that can be invoked to generate the CoreLinux++ Code Standard conforming *.hpp and *.cpp initial files.
Shall generate files that are either specific
to known projects:
A) libcorelinux
B) libcoreframework
C) testdrivers
D) utils
or for user specified.
If the files are generated for known projects, headers shall be placed into appropriate include directory and implementation into appropriate source directory.
If the files are user specified, the user shall have some way to designate locations, and utility shall place appropriate files where directed.
Utility shall be able to run in batch mode with a redirection of a list that describes the individual generation requests.
Utility shall accept, as input, a generator script.
Script file will contain declaration for target Class
Script file shall support copyright declaration
Script file shall support declaration for indicating either Header file, Source file, or both are to be generated.
Script file shall support declaration of super-class for Class
Script file shall support declaration indicating a template class is being generated.
Script file shall support configurable accessability options to standard class declarations.
Script file, at a minimum, shall support declarations of options available on the command line.
Script file shall support declaration of data members to declare in Header file generation.
Upon unrecoverable errors, the utility shall remove any work that has been performed up to the point of error.
Users shall be able to specify unrecoverable error dispositions in relation to work rollback.
If generating for known projects, utility shall included appropriate namespace.
For known projects, utility shall insert CoreLinux++ Consortium copyright and LGPL license in header and source files.
For known projects, utility shall insert the RCS tags that are used for the project.
For known projects, utility shall use comment forms that are consistent with project standards.
Utility shall insert spaces instead of tabs for indentation.
Utility shall be able to accept inheritence declarations in the case where a target is a subclass of an existing class.
Utility shall be able to accept the following subclass access declarations:
A) public
B) protected
C) private
D) virtual (in combination with A-C)
Utility shall be able to generate templated classes.
Utility shall generate the following methods:
A) public default constructor
B) public copy constructor
C) public destructor
D) public assignment operator overload
E) public equality operator overload const
Utility shall enable translation of all text output (display, error, exception, etc.).
For subclass generation, utility shall generate appropriate '#include' of the named super class.