Archive for the ‘MANUAL MAINTENANCE’ Category

UPDATED VERSION AVAILABLE FOR DOWNLOAD

July 1, 2014

The _ERROR command has been updated so that during a test project, an _ERROR command with the optional Name parameter will continue executing the test project if the terminating comment is a date. If the terminating comment is missing or has the
break-point symbol (<—-), it will terminate execution. The error message will be displayed in all cases. This modification will formalize the _ERROR checkout/test process defined by the test project.

As before, The Linux executable must be prepared through a make process; All of the files have been provided in the source directory.

This upgrade will be found in the version 3 downloads contained in my website. All versions can be found PROGRAMMABLE SOFTWARE DEVELOPMENT
ENVIRONMENT in http://www.codeplex.com.

Also, if a WIN32 version was downloaded before 1800 Pacific Standard Time, please downloaded it again.

Advertisements

Open Source Software Development Tool: Upgrade Progress

June 28, 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/06/27

STATUS: The manual description of the __GET_ERROR_MACRO and
_GET_ERROR_TYPE commands have been successfully modified.

RESULTS: The manual descriptions for the Error Message Command Group
have now been updated,

NEXT TASK: The revised Programmable Software Development Environment
will now be prepared for publication.

 

Open Source Software Development Tool: Upgrade Progress — 2014-06-09

June 11, 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.

WEDNESDAY: 2014/06/11

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

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

Open Source Software Development Tool: Upgrade Progress

May 28, 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/05/27

STATUS: The manual description of the ERROR RESOURCE has been modified.

NEXT TASK: The manual description of the _STATE_ERROR Command needs to
be modified.

 

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.

 

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

February 14, 2014

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

Major improvement have been made from the 1) Implementation of the experimental, alpha, beta, and release versions of a software parts library and 2) the ability to detect whether the product text files have modified manually (patched).

To certify a software parts library, every command defining this library must be executed. This includes all error detection and reporting statements.  These error statements not only include those associated with the user but also those that detect and report programming and Programmable Software Development Environment errors.

Ideally, those _ERROR statements that report programming and Programmable Software Development Environment errors will never be executed. Therefore, they currently can not be included in the certification test sequence. The challenge is to provide a set of commands which will be executed during a test sequence and report a specified programming or Programmable Software Development Environment failure should it occur.

The following two commands need to be developed: 1) _CONTINUE_IF which will error out if the preceeding test condition is false and 2) _CONTINUE_IF_NOT which will error out if the preceeding test condition is true. These statements replace the currently used _JUMP_IF and _JUMP_IF_NOT statements.

THURSDAY: 2013/02/13

STATUS: I have modified the Program Control section of the manual to include the _CONTINUE_IF and _CONTINUE_IF_NOT  commands.

DETAIL: The other commands which were documented using Microsoft Front Page have not been updated.

NEXT TASK: The new version will next be prepared for publication,

Open Source Software Development Tool: Upgrade Progress

February 11, 2014

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

Major improvement have been made from the 1) Implementation of the experimental, alpha, beta, and release versions of a software parts library and 2) the ability to detect whether the product text files have modified manually (patched).

To certify a software parts library, every command defining this library must be executed. This includes all error detection and reporting statements.  These error statements not only include those associated with the user but also those that detect and report programming and Programmable Software Development Environment errors.

Ideally, those _ERROR statements that report programming and Programmable Software Development Environment errors will never be executed. Therefore, they currently can not be included in the certification test sequence. The challenge is to provide a set of commands which will be executed during a test sequence and report a specified programming or Programmable Software Development Environment failure should it occur.

The following two commands need to be developed: 1) _CONTINUE_IF which will error out if the preceeding test condition is false and 2) _CONTINUE_IF_NOT which will error out if the preceeding test condition is true. These statements replace the currently used _JUMP_IF and _JUMP_IF_NOT statements.

MONDAY: 2014/02/10

STATUS: I have examined the Program Control section of the manual and have found that the _CONTINUE_IF and _CONTINUE_IF_NOT  commands can be added to this section without modifying the existing command presentation files (The table of contents will, of course, need to be modified).

DETAIL: The existing command presentation files were written by Microsoft Front Page and need to be replaced.  This can be done at a later time.

NEXT TASK: The next task will be to prepared the sub-directories, files, and modification to the table of contents associated with the _CONTINUE_IF command.

Open Source Software Development Tool: Upgrade Progress

December 26, 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.

THURSDAY: 2013/12/26

STATUS: I have completed the re-documentation process of the INPUT FILES software parts commands.

NEXT TASK: The next step will be to make a final proof of the updated manual pages, Once this is done, the updated Programmable Software Development Environment will be prepared for uploading to my website and my CodePlex account.

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.