Archive for April, 2012

MANUAL MAINTENANCE

April 27, 2012

The activity associated with the maintenance of Programmable Software Development Environment Manual be presented here. Of critical importance is the use of strictly portable (Win32, Linux) standard methods for preparing the associated “*.html” files.

SUNDAY: The software part file table of contents has been successfully updated. To prepare for the next step, the return linkages in the pages referenced by the software parts file table of contents need to be updated using Front Page.

MONDAY: The return linkages in the pages referenced by the software parts file table of contents need to be updated.

TUESDAY: The Software Parts Definition table of contents has been prepared. The Program Control Instruction table of contents is next.

Advertisements

Can Programming Be Strictly Portable Relative To Language?

April 27, 2012

The activity associated with development of strictly portable methods of software development will be presented here. Included in this Portability effort will be Windows based C, C++, C#, and Visual Basic; and Linux based C and C++.

FRIDAY: The formal tests associated with the common routine software parts associated with loading one or more routines into a class has been completed. This includes all relevant error conditions.

SUNDAY: In order to minimum potential for error, every variable name must have a single point of definition. This includes the routine and argument names. The routine and argument names have been defined in the class definition development step. The routine and argument names will be re-enter during the definition of the actual routine. These names will be verified as being identical with those entered in the class definition development step.

MONDAY: The routine definition step functionality of the common routine library has been thoroughly tested.  Error response of the routine definition phase will be tested next.

TUESDAY: The formal tests of routine definition step of the common routine library is complete.  The user definition step of the common routine library is next.

WEDNESDAY: In C++, there are three different representations for each routine: 1) class declaration, routine definition, and the one used for calling the routine. A single point definition is a necessary requirement for portable error free software. This should be done in the class definition step and stored in the Programmable Software Development Environment post office where it can be read in the other steps. To rigorously implement this one step requirement, modification of the name routine library to add a second representation will be needed.

MANUAL MAINTENANCE

April 20, 2012

The activity associated with the maintenance of Programmable Software Development Environment Manual be presented here. Of critical importance is the use of strictly portable (Win32, Linux) standard methods for preparing the associated “*.html” files.

TUESDAY: The update of the Programmable Software Development Environment manual has been restarted. It is vitally important to eliminate the need of Front Page which is not portable between Windows and Linux. Front Page has been used to modify the Software Parts File Table of contents to enable the update to take place. Specifically, the associated *.htm files and associated links have been converted to *.html files.

Open Source Software Development Tool: Upgrade Progress

April 20, 2012

It is planned to update the Programmable Software Development Environment to provide the capability of preparing a text file copy of the command line screen display.  It is also planned to update the debug screen menu to provide the capability of making a comment (which would be recorded in the screen display file). A person desiring to learn how to use this program would want to look over my shoulder when I am using it.  This screen display file would provide an equivalent capability.

TUESDAY: The modifications to Programmable Software Development Environment are currently being identified and are expected to be finished in the next several days.

Can Programming Be Strictly Portable Relative To Language?

April 20, 2012

The activity associated with development of strictly portable methods of software development will be presented here. Included in this Portability effort will be Windows based C, C++, C#, and Visual Basic; and Linux based C and C++.

SUNDAY: Formal testing of the common routine name software parts has been completed. The common routine software parts will be started.  Some upgrades to these parts may be necessary.

TUESDAY: The Formal testing of the common routine name software parts has emphasize the need of well-defined purposes of each of the libraries in the chain leading up to the preparation of the class-defining files. In CPP, there are two additional steps between the class-definition library and what has been accomplished. The first one is a routine common parts library and the second one is a CPP parts library. The previously developed library sets associated with this process (include and typedef libraries) must be  subjected to the same formal testing which will result in appropriated upgrades. I have learned an easy means of using the Testing capability of the Programmable Software Development Environment to checkout and thoroughly test a software parts library!

THURSDAY: The common routine software parts associated with loading one or more routines into a class has been thoroughly tested. During these test, a restriction was found; each of the arguments in the definition must have a different name. This restriction might be an inconvenience since common arguments such as an index normally have the same name. On the other hand, it will improve the resulting program from a self-documenting point of view.

Can Programming Be Strictly Portable Relative To Language?

April 13, 2012

The activity associated with development of strictly portable methods of software development will be presented here. Included in this Portability effort will be Windows based C, C++, C#, and Visual Basic; and Linux based C and C++.

MONDAY: I have now achieved a simple set of test software parts libraries and now the checkout of the common routines names software parts is rapidly proceeding.  The need to upgrade the Error subsystem of the Programmable Software Development Environment has now been put on the back-burner.

TUESDAY: As I am increasing the test specification and the number of Monte-Carlo tests for the common routine names software parts, I am running into the unexpected errors again.  Errors in the test specification are assumed to be the cause. I will be updating the test libraries to improve my ability to manage the test specifications

THURSDAY: I have updated the test libraries adding a space and “|” to the test specifications to help visualize the test conditions and was able as a consequence to solve the unexpected error problem.  Testing of the common routine name software parts continues.

2012-04-04 ERROR

April 8, 2012

SUNDAY: The corrected Programmable Software Development Environment has been uploaded to the web-site and are now available for download.  Additional TEST TASK related changes to Programmable Software Development Environment are expected.

Can Programming Be Strictly Portable Relative To Language?

April 6, 2012

The activity associated with development of strictly portable methods of software development will be presented here. Included in this Portability effort will be Windows based C, C++, C#, and Visual Basic; and Linux based C and C++.

WEDNESDAY: The Programmable Software Development Environment is equipped with a Test sub-system which is quite comprehensive in nature but is difficult to use. The basic software parts for writing the “Test Program Step” have been checked-out and appear to be quite easy to use. The name routine library is currently being checked out using the “Test Program Step”. One improper error has been detected by the TEST TASK sub-system. This error has not as yet been located.  I plan to build an additional error report library to help me to easily find and correct these kind of errors.

THURSDAY: I plan to increase the error-reporting capabilities of the Programmable Software Development Environment.  Currently, it includes the name that follows the _ERROR statement. I plan to automatically add the software library name, software part name, and the software part line number of the _ERROR statement. additional commands for reading this data will need to be added.  I believe that these changes are needed to facilitate the location of unexpected errors found during the TEST TASK.

2012-04-04 ERROR

April 6, 2012

Another functional error in the testproj.cpp routine has been discovered.

PCG ERROR: Precfile — 373
PCG ERROR: testproj — 5249
PCG ERROR: testproj — 4991
PCG ERROR: testproj — 3734
PCG ERROR: mainprj — 1404
PCG ERROR: explrpde — 168

The cause of this error: lack of use. My apologies for the large number of errors in the TEST TASK sub-system (see manual).  It has been a difficult system to use; hence it has not been used for a considerable period of time. Hopefully there are no more of these errors.

WEDNESDAY: The functional error in the testproj.cpp routine has been corrected. It will be available for download within the next several days.