During the this blog week, it became apparent that I was presenting details in my blog that required access to the associated software parts kits.  I am considering possible access for those readers who are genuinely interested.

SATURDAY: The data return software parts for the CPP routine software part kit have been prepared. The software parts for defining and writing the routine’s arguments will be prepared next.

During the this blog week, it became apparent that I was presenting details in my blog that required access to the associated software parts kits.  I am considering possible access for those readers who are genuinely interested.

FRIDAY: The struggle with the definition of a standard routine methodology is diminishing. The single-point definition of a routine is contained in the post office defined by the common routine software parts library. The way that it is written in the source code is contained in the routine software parts library associated with the specific programming language.

SATURDAY: The are two basic types of routine; public and private. The public routine is available to other classes and its associated class contains its data. The private routine is available only to its associated class which also contains its data. I have started rebuilding the CPP software parts for the public routine. There are three processing paths: 1) declaration path for the class definition file, 2) routine path for the definition of the routine, and 3) user path for its use in other routines.

SUNDAY: The beginning software parts for the public routines have been prepared. In all cases, a script is used to write the CPP code when required. The declaration script sequence must be performed first, At this time, I do not know whether the routine script or the user scripts should be performed next.  I do know that to prepare the user scripts, the automatic storage and the parameters of the routines must have already been defined.

MONDAY: Each routine has not only a specific procedure that performs the required function but also a status reporting procedure. This requirement affects the use of a script in the definition of the routine.

TUESDAY: The principle of “Simplify and add lightness” must now be applied to the common routine parts associated with data return. Originally, the returns were specifically defined by two software parts: One for a data return and other for a status return. These two software parts will be replaced by one.

WEDNESDAY: The modifications to the common routine parts have now been prepared. Modification / creation of the data return software parts of the CPP routine software kit will proceed.

My apologies for inadequacies in my blogging efforts.  I have had a non-related significant distraction from my research/development activities. These distractions have not as yet been completed.  Hopefully in a few weeks…

THURSDAY: Currently, I am struggling with the definition of a routine.  The fact that, in general, a routine is defined in one source file and used in another conflicts with a single point definition of how the associated source code is written. This is a very complex script process. One of the possibilities is a number of standard resource files for each class. Such files would contained standard automatic variables, and usage “define files” standards. I have already accepted a class data resource file. This represents a serious trade-off between serious standard methods, ease of the design process and source file self-documentation.

An Algorithmic Error has been encountered in the _ENCRYPT, _DECRYPT commands which produces an “Illegal InpuLength” user error (Pardon my spelling)

SUNDAY: The corrected Programmable Software Development Environment has been uploaded to the web-site and are now available for download.

An Algorithmic Error has been encountered in the _ENCRYPT, _DECRYPT commands which produces an “Illegal InpuLength” user error (Pardon my spelling)

THURSDAY: I am continuing to modify the common routine software parts library and I have started to modify the CPP routine software parts. I have completed the declaration script up to the argument list.

SATURDAY: I have re-examined the common routine library and have found it to be too complex (Simplify and add lightness).  Every class has a data structure. There are three routine types: 1) Routines that process the data structure and return data, 2) Routines that process the data structure and do not return any data, and 3) a routine the processes and returns the status/error reporting. Their implementation for the service and client classes will be different for each of the languages. I have started to modify the common routine software parts library

MONDAY: The modified Programmable Software Development Environment is capable of accessing up to 16 levels of development task files. This Programmable Software Development Environment has been published and can be downloaded.

FRIDAY: The software part that prepares one or more paragraphs has been modified.