Posts Tagged ‘programmable software’

PROGRESS REPORT

March 23, 2018

This purpose of this post is to publish single line
reports on the projects performed during the week.

**************************************************************
**************************************************************

2018/03/16

MAKE FILE GENERATOR

The Make file generator program has been updated so that it will be able
to make the STNDPCG program. The Make file project will be updated
so that it will be exportable to the Apple Machine.

2018/03/20

MAKE FILE GENERATOR

The Make file project has been updated so that it can easily imported
to the Apple Machine. The preparation of the STNDPCG make file
will be started.

CLASS COMMON STRUCT PROJECT

A collection of prototype parts software parts for the classcommonstruct
library. The next task will be to prepare this prototype library.

Advertisements

PROGRESS REPORT

March 9, 2018

This purpose of this post is to publish single line
reports on the projects performed during the week.

**************************************************************
**************************************************************

2018-02-28

RELATIVITY BOOK / TOASTMASTERS

The preparation of the seventh segment of the Relativity book has been started

COMMON CLASS LIBRARIES

The software parts for the classcommonstruct library have been prepared and
are ready for library development.

2018-03-04

COMMON CLASS LIBRARIES

The software part for the classcommonarray has been modified to prevent an
array size of less than 2 elements from being loaded.

Can Programming Be Strictly Portable Relative To Language?

June 14, 2016

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++.

TUESDAY: 2016/06/14

STATUS: The CPP output library has been successfully tested. It is
ready for use.

NEXT TASK: The next task will be to examine previously CPP development
activities to determine the next step.

Open Source Software Development Tool: Upgrade Progress

April 18, 2015

The purpose of this update task is improve capability of the
Programmable Software Development Environment to certify that a product
is error free and functions according to specification.

The current version control defines the status of the software parts
files. Specifically, the alpha version is still being tested; the beta
version still has code that needs to be tested; and the release version
has been completely tested.

A Programmable Software Development Environment equivalent to the First
Article Test and the Factory Acceptance Test needs to be developed.

SATURDAY: 2015/04/18

STATUS: Modifications to the Programmable Software Development
Environment are needed.

NEXT TASK: The first sub-task will be selected.

Open Source Software Development Tool Error

February 28, 2015

An** Programmable Software Development Environment system error has been
discovered,

The WIN32 error message is as follows:

PCG ERROR: MacCert — 455
PCG ERROR: macproj — 2698
PCG ERROR: macproj — 315
PCG ERROR: devproj — 1400
PCG ERROR: mainprj — 1461
PCG ERROR: explrpde — 153

The LINUX error message is as follows:

PCG ERROR: MacCert — 474
PCG ERROR: macproj — 2717
PCG ERROR: macproj — 334
PCG ERROR: devproj — 1419
PCG ERROR: mainprj — 1480
PCG ERROR: explrpde — 172

FRIDAY 2015/02/27

STATUS: I restored what I thought was the original WIN32 version. I
compiled both a debug version and release version, and performed some
preliminary tests. To my surprise, I found that nothing changed. The
“restored” versions did not produce the subject error where as the the
production tool being used did.

DETAIL: This surprise caused me to very carefully re-examine the
associated routines, macproj, precmac, maccert, and crypto. I was
looking for a very subtle error or some old coding method no longer
supported and I got my next big surprise. Specifically, my archival
version was not the original version. I checked the Linux version and
it was the equivalent original version.

RESULTS: My version control practices failed! I have a primitive
version control implemented in the Programmable Software Development
Environment and it is woefully inadequate. Improving it will be high
on my priorities.

NEXT TASK: Ny next task will be to very carefully compare the
associated routines of the Linux version with the Windows version to
determine how extensive the version control error is. Once this is
done, I will probably attempt to upgrade the Linux version to see if
it’s original difficulties can be resolved.

Open Source Software Development Tool Error

November 14, 2014

An Programmable Software Development Environment system error has been
discovered,

The WIN32 error message is as follows:

PCG ERROR: MacCert — 455
PCG ERROR: macproj — 2698
PCG ERROR: macproj — 315
PCG ERROR: devproj — 1400
PCG ERROR: mainprj — 1461
PCG ERROR: explrpde — 153

The LINUX error message is as follows:

PCG ERROR: MacCert — 474
PCG ERROR: macproj — 2717
PCG ERROR: macproj — 334
PCG ERROR: devproj — 1419
PCG ERROR: mainprj — 1480
PCG ERROR: explrpde — 172

THURSDAY: 2014/11/13

STATUS: The following error was encountered when I was attempting to
separate the very large CSS Web Site Library into a system of smaller,
more compact libraries

DETAIL: When I developed the Programmable Software Development
Environment Version Control capabilities, I did not properly handle the
the include source files needed for the above library conversion effort.

NEXT TASK: An upgrade to the Version Control Capabilities is indicated.
Minimally, the Include statement must be included in the computation of
its pseudo-random parity computation. Furthermore, to insure that the
software parts files defining the release version of library are not in
any way altered, it may be appropriate to include the comments in the
pseudo-random parity computation The next step is to prepare a plan.

Open Source Software Development Tool Error

November 11, 2014

An Programmable Software Development Environment system error has been
discovered,

The WIN32 error message is as follows:

PCG ERROR: Preccall — 574
PCG ERROR: mainprj — 1723
PCG ERROR: explrpde — 153

The LINUX error message is as follows:

PCG ERROR: Preccall — 593
PCG ERROR: mainprj — 1742
PCG ERROR: explrpde — 172

TUESDAY: 2014/11/11

STATUS: The corrected version of the Programmable Software Development
Environment has been uploaded and is now available.

DETAIL: The Windows version is a command line program that requires no
installation. To install the LINUX version, one must make it from the
source files. Make files have been provided in the Workspace sub
directory and if the EXPLRPDE directory is extracted onto the HOME
directory, script files (make_debug, instal_explrpde) that have been
included will perform the installation process

NEXT TASK: This task has been concluded.

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.