Archive for June, 2010

HTML RESEARCH STATUS REPORT — 2010-06-25

June 25, 2010

The development of the latest version with the capability of reading up to 16 text files has made it possible to prepare specialized *.html files such as used in a users manual. In particular, an effort to rebuild the user’s manual for the Programmable Software Development Environment using the tool is progressing.

The development of software parts library for writing lines of a *.html file has been completed. Each line begins with a comment containing the source line number, the date contained at the end of the source line, and the optional longitudinal parity associated with the line.  As in the source code certification process, the text, date and source line number are included in the longitudinal parity computation.

The software parts needed to prepare the primary table of contents has been completed and the primary table of contents for the manual (explrpde.html) has been prepared.  The software parts for providing the the required linkages between various pages is currently under development. Postoffice files are being used to contain the needed linkage information.

As in all of my development activities, strict portability between the Linux and Windows operating systems is being rigorously maintained.  I have worked on either system with all of the defining files on a Flash Drive.

Advertisements

CPP-CSHARP PORTABILITY STATUS — 2010-06-18

June 18, 2010

In CPP one can return more than one element of data from a routine.   This is accomplished by passing an  address as one of the routine arguments.   Such cannot be done in CSHARP.

In the original CPP standards, a routine returns up to three items: an upgraded version of the associated  data structure,  data resulting from a particular operation, and the status/error value.   There is no clean way of doing this in CSHARP.

The solution of this portability challenge can be found by adopting a “driver philosophy”.  There will be  three categories of routines; routines that update the associated data structure, routines that produce data without updating the associated data structure, and routines that return the processing or test status without  updating the associated data base.  Errors can be handled by CSHARP’s exception handling capability.

These three categories of routine can be easily implemented in CPP and may expand strict portability to the development of drivers.

UPGRADE–2010-06-11

June 14, 2010

Over the last several months, my primary research effort has been directed at producing strictly portable development methods between C++ and C# .  This effort uses a system of Post Office communication files.  As this effort progressed, I have encountered errors in the post office system which I have repaired.

I completely forgot about the fact that there are applications that do not use a post office.  When I started testing the *.html output file which does not use a Post office, I encountered an error that occurred because there was no post offices specified in the source definition sub-task files.

I have now upgraded the Programmable Software Development Enviroment to correct the reported problem.  I have successfully used the tool on the both the *.html and portability development efforts.  The new version can be downloaded.  Please note that there have been revisions in the syntax of the source development sub-task file.

Please be advised that this software development tool is still a beta version.  It is still a work in progress that is being driven by my personal research and development efforts.

MY APPOLOGY–2010-06-11

June 11, 2010

Over the last several months, my primary research effort has been directed at producing strictly portable development  methods between C++ and C# .  This effort uses a system of Post Office communication files.  As this effort progressed,  I have encountered errors in the Post office system which I have repaired.

I completely forgot about the fact that there are applications that do not use a Post office.  When I started testing the *.html output file which does not use a Post office, I encountered an error that occurred because there was no post offices specified in the source definition sub-task files.

My apologies for this oversight.  There is only one of me in this effort and my priorities will on occasion allow an error to go undetected.  I am thankful that my error-detection methodology has been quite effective in this maintenance process.

If a user encounters an error involving the maildict source file in an application which does not involve a Post office, please insert a legitimate _POSTOFFICE instruction in the source definition sub-task file and it should go away.

The correction of this error is now my top priority.

HTML RESEARCH STATUS REPORT — 2010-06-11

June 11, 2010

The development of the latest version with the capability of reading up to 16 text files has made it possible to prepare specialized *.html files such as used in a users manual. In particular, an effort to rebuild the user’s manual for the Programmable Software Development Environment using the tool is progressing.

All of the *.html commands needed to prepare the user’s manual have been identified and explored.  The development of software parts library for writing lines of a *.html file has been started and is in checkout.   Each line will begin with a comment containing the source line number, the date contained at the end of the source line, and the optional longitudinal parity associated with the line.  As in the source code certification process, the text, date and source line number are included in the longitudinal parity computation.

DEVELOPMENT OF *.html FILES — STATUS REPORT

June 4, 2010

The development of the latest version with the capability of reading up to 16 text files has made it possible to prepare specialized *.html files such as used in a users manual. In particular, an effort to rebuild the user’s manual for the Programmable Software Development Environment using the tool has begun.

The basic design philosophy will be to produce a unique file for each section of the document.  This will produce many more document files, each of which will be much smaller than those currently containing the manual.  The definition of the associated software kit library is the next task.

ERROR ALERT — 2010-05-31

June 3, 2010

The following error has been encountered

PCG ERROR: srcproj — 1954
PCG ERROR: devproj — 1474
PCG ERROR: mainprj — 1281
PCG ERROR: explrpde — 168

This error was the result of improper user error handling. This error occurred when an input text file was being opened. It may be due to system timing considerations; i.e., a request to open a file before the previous file closing operation was completed.

The user error handling problem has been corrected and is presently being tested. Other upgrades are currently being considered.  When completed, a new version will be published.