Posts Tagged ‘programmable software’

Open Source Software Development Tool: Upgrade Progress

May 25, 2014

The overall purpose of the current Programmable Software Development
Environment upgrade process is to certify that a product generated is
certifiably releasable.

To certify a software parts library, every command except the _ERROR
command defining a library must respond to a ‘<—‘ debug flag comment
at the end of a the command line. Specifically, when the debug flag is
present, the subject command will be executed first and then the
command data (command, arguments, and results) will be displayed and
then the operator will be given a option of terminated execution or
continuing.

The _ERROR command must be corrected to equivalently respond to the
debug flag.

The major difference between the _ERROR command and all other commands
is that the debug flag will be processed before the command is executed.

The Programmable Software Development Environment will be modified so
that the _ERROR command will respond to the debug flag before
terminating execution.

FRIDAY 2014/05/24

STATUS: The manual description of the _ERROR command has been
successfully modified.

NEXT TASK: The manual description of the ERROR RESOURCE needs to be
modified.

 

Advertisements

Open Source Software Development Tool: Upgrade Progress

April 5, 2014

The overall purpose of the current Programmable Software Development
Environment upgrade process is to certify that a product generated is
certifiably releasable.

To certify a software parts library, every command except the _ERROR
command defining a library must respond to a ‘<—‘ debug flag comment
at the end of a the command line. Specifically, when the debug flag is
present, the subject command will be executed first and then the
command data (command, arguments, and results) will be displayed and
then the operator will be given a option of terminated execution or
continuing.

The _ERROR command must be corrected to equivalently respond to the
debug flag.

The major difference between the _ERROR command and all other commands
is that the debug flag will be processed before the command is executed.

The Programmable Software Development Environment will be modified so
that the _ERROR command will respond to the debug flag before
terminating execution.

FRIDAY 2014/04/04

STATUS: I have re-examine all of the code associated with the _ERROR
command with a single argument.

DETAIL: The _ERROR command basically terminates the execution of the
development process. When a test project is being executed and an
_ERROR command with an argument is encountered, the specific test case
is terminated and the test project is allowed to process the next test
case.

RESULTS: I found that if the _ERROR command with an argument and no
“<—-” or date will behave as it was original defined.

NEXT TASK: The manual description of the _ERROR command needs to be
modified.

 

Open Source Software Development Tool: Upgrade Progress

April 1, 2014

The overall purpose of the current Programmable Software Development
Environment upgrade process is to certify that a product generated is
certifiably releasable.

To certify a software parts library, every command except the _ERROR
command defining a library must respond to a ‘<—‘ debug flag comment
at the end of a the command line. Specifically, when the debug flag is
present, the subject command will be executed first and then the
command data (command, arguments, and results) will be displayed and
then the operator will be given a option of terminated execution or
continuing.

The _ERROR command must be corrected to equivalently respond to the
debug flag.

The major difference between the _ERROR command and all other commands
is that the debug flag will be processed before the command is executed.

The Programmable Software Development Environment will be modified so
that the _ERROR command will respond to the debug flag before
terminating execution.

TUESDAY: 2014/04/91

STATUS: The manual section defining the _ERROR command was examined to
determined what changes need to be made.

RESULTS: I realized that I dud not know exactly how the changes that I
have made to the _ERROR command will affect its behavior when neither a
date or “<—-” was present.

NEXT TASK: I will re-examine the associated code to evaluate its
behavior and if necessary perform the necessary tests.

 

Open Source Software Development Tool: Upgrade Progress

March 28, 2014

he overall purpose of the current Programmable Software Development
Environment upgrade process is to certify that a product generated is
certifiably releasable.

To certify a software parts library, every command except the _ERROR
command defining a library must respond to a ‘<—‘ debug flag comment
at the end of a the command line. Specifically, when the debug flag is
present, the subject command will be executed first and then the
command data (command, arguments, and results) will be displayed and
then the operator will be given a option of terminated execution or
continuing.

The _ERROR command must be corrected to equivalently respond to the
debug flag.

The major difference between the _ERROR command and all other commands
is that the debug flag will be processed before the command is executed.

The Programmable Software Development Environment will be modified so
that the _ERROR command will respond to the debug flag before
terminating execution.

FRIDAY 2014/03/28

STATUS: The WIN32 precsrce source files was restored to the archival
files. Both the WIN32 and the LINUX precoper source files were then
modified to implement the above revised _ERROR definition.

DETAIL: The _ERROR command basically terminates the execution of the
development process. The zero argument _ERROR statement rendered
obsolete by the _CONTINUE_IF and _CONTINUE_IF_NOT commands is still
available.

RESULTS: Both the updated WIN32 and LINUX Programmable Software
Development Environment prepared, built and tested and found to be
functional.

NEXT TASK: The next task will be to examine the manual to see what
changes need to be made.

 

Open Source Software Development Tool: Upgrade Progress

March 27, 2014

The overall purpose of the current Programmable Software Development
Environment upgrade process is to certify that a product generated is
certifiably releasable.

To certify a software parts library, every command except the _ERROR
command defining a library must respond to a ‘<—‘ debug flag comment
at the end of a the command line. Specifically, when the debug flag is
present, the subject command will be executed first and then the
command data (command, arguments, and results) will be displayed and
then the operator will be given a option of terminated execution or
continuing.

The _ERROR command must be corrected to equivalently respond to the
debug flag.

The major difference between the _ERROR command and all other commands
is that the debug flag will be processed before the command is executed.

The Programmable Software Development Environment will be modified so
that the _ERROR command will respond to the debug flag before
terminating execution.

THURSDAY: 2013/03/27

STATUS: My preliminary experimental modifications of the precsrce
source file were unsuccessful and it occurred to me this morning that
my original approach was probably overkill.

DETAIL: The _ERROR command basically terminates the execution of the
development process. The one argument _ERROR statement provides the
capability of running a test project. I believe that the “<—-” is
indicative of the fact that this statement has not as yet been tested
and requires that the process should be unconditionally stopped.
Permission to continue in a test project can be granted by replacing
the “<—-” with the date.

NEXT TASK: The precsrce source files will be restored to the archival
files. The precoper source files will be then be modified to implement
the above revised _ERROR definition.

 

Open Source Software Development Tool: Upgrade Progress

March 23, 2014

The overall purpose of the current Programmable Software Development
Environment upgrade process is to certify that a product generated is
certifiably releasable.

To certify a software parts library, every command except the _ERROR
command defining a library must respond to a ‘<—‘ debug flag comment
at the end of a the command line. Specifically, when the debug flag is
present, the subject command will be executed first and then the
command data (command, arguments, and results) will be displayed and
then the operator will be given a option of terminated execution or
continuing.

The _ERROR command must be corrected to equivalently respond to the
debug flag.

The major difference between the _ERROR command and all other commands
is that the debug flag will be processed before the command is executed.

The Programmable Software Development Environment will be modified so
that the _ERROR command will respond to the debug flag before
terminating execution.

SATURDAY: 2014/03/22

STATUS: I have made the necessary modifications to the precoper source
file and have found that these modifications were inadequate.

DETAIL: I am a victim of the phrase “all you have do is…”.  The
routines that I called in the precoper source file set the stage for
debug management routine that is called in the precsrce source files.
The debug management routines are only called for a continuing process,
not a terminating error condition.

NEXT TASK: Experimental modifications of the precsrce source file is
the next task.

Open Source Software Development Tool: Upgrade Progress

March 17, 2014

The overall purpose of the current Programmable Software Development
Environment upgrade process is to certify that a product generated is
certifiably releasable.

To certify a software parts library, every command except the _ERROR
command defining a library must respond to a ‘<—‘ debug flag comment
at the end of a the command line. Specifically, when the debug flag is
present, the subject command will be executed first and then the
command data (command, arguments, and results) will be displayed and
then the operator will be given a option of terminated execution or
continuing.

The _ERROR command must be corrected to equivalently respond to the
debug flag.

The major difference between the _ERROR command and all other commands
is that the debug flag will be processed before the command is executed.

The Programmable Software Development Environment will be modified so
that the _ERROR command will respond to the debug flag before
terminating execution.

MONDAY: 2014/03/17

STATUS: I have examined the relevant source files and have determined
this correction can most likely be accomplished by modifying the
precoper source files.

NEXT TASK: The next task will be to create the appropriate archival
file and start the modification process in the Windows version of the
Programmable Software Development Environment.

Open Source Software Development Tool: Upgrade Progress

December 25, 2013

It is planned to upgrade the Programmable Software Development
Environment to include the capability of reading the paste-in text
files where the each paragraph is one very long line.  You may need to
download the latest version of the Programmable Software Development
Environment to fully understand my reports.

Currently, the Programmable Software Development Environment has the
capability of reading a standard ASCII text file where the TAB
character is replaced with a suitable number of blanks. Each line of
the text file cannot be longer than 256 characters. On the other hand,
the Programmable Software Development Environment has the capability of
writing a paste-in text file where each paragraph is one very long
line. This capability includes the ability to include special
characters such the TAB.

The ability to read the paste-in text file is needed to certify that
the file has not been changed, was developed using the agree-upon
standard libraries, or has not been illegally copied.

TUESDAY: 2013/12/24

STATUS: The manual page associated with the _TEXT_BASE_NAME (not the
_TEXT_PATH as originally planned) has been updated.

NEXT TASK: The next task will be to update the _TEXT_PATH manual page.
There are two more pages to update.

Open Source Software Development Tool: Upgrade Progress

December 17, 2013

It is planned to upgrade the Programmable Software Development
Environment to include the capability of reading the paste-in text
files where the each paragraph is one very long line.  You may need to
download the latest version of the Programmable Software Development
Environment to fully understand my reports.

Currently, the Programmable Software Development Environment has the
capability of reading a standard ASCII text file where the TAB
character is replaced with a suitable number of blanks. Each line of
the text file cannot be longer than 256 characters. On the other hand,
the Programmable Software Development Environment has the capability of
writing a paste-in text file where each paragraph is one very long
line. This capability includes the ability to include special
characters such the TAB.

The ability to read the paste-in text file is needed to certify that
the file has not been changed, was developed using the agree-upon
standard libraries, or has not been illegally copied.

MONDAY: 2013/12/16

STATUS: I have re-documented the _TEXT_NAME manual page.

NEXT TASK: The next task will be to update the _TEXT_PATH manual page.
There are three more pages to update.

Open Source Software Development Tool: Upgrade Progress

December 14, 2013

It is planned to upgrade the Programmable Software Development
Environment to include the capability of reading the paste-in text
files where the each paragraph is one very long line.  You may need to
download the latest version of the Programmable Software Development
Environment to fully understand my reports.

Currently, the Programmable Software Development Environment has the
capability of reading a standard ASCII text file where the TAB
character is replaced with a suitable number of blanks. Each line of
the text file cannot be longer than 256 characters. On the other hand,
the Programmable Software Development Environment has the capability of
writing a paste-in text file where each paragraph is one very long
line. This capability includes the ability to include special
characters such the TAB.

The ability to read the paste-in text file is needed to certify that
the file has not been changed, was developed using the agree-upon
standard libraries, or has not been illegally copied.

FRIDAY 2013/12/13

STATUS: I have re-documented the _NO_TEXT_FILES manual page.

NEXT TASK: The next step will be to prepare the _TEXT_NAME manual page.