Posts Tagged ‘Programmable Software Development Environment errors’

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.

Advertisements

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

January 27, 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.

SUNDAY: 2014/01/26

STATUS: The update of the Programmable Software Development Environment has been completed and tested in both the Win32 and Linux environments.

DETAIL: The _CONTINUE_IF, and _CONTINUE_IF_NOT have been implemented in the in the global, precmac, precoper source files, compiled and tested. I am now using the resultant Windows and Linux executables.

NEXT TASK: The next task will be to update the manual to include these commands..