Posts Tagged ‘Programming Standards’

Can Programming Be Strictly Portable Relative To Language?

March 30, 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 Programmable Software Development Environment is equipped with a Test sub-system which is quite comprehensive in nature but is difficult to use. One of the most difficult steps is the use of the “Define Test Step” program generation file (See Manual) and the internal pseudo-random generator to prepare the “Test Program Step” program generation file. I believe that I have a simple method for accomplishing this task. I will try to use facility to perform a much more thorough check/test of the various routine libraries.

MONDAY: The basic Test Definition File will be a source definition file with the random generator specification presented as a comment following the source definition command. This file will be read as an input file, not a source definition file.  On a line-by-line basis, if the actual random generator string matches the specification, the line gets copied into the output file. Otherwise, it does not.

TUESDAY: The basic software parts for writing the “Test Program Step” have been prepared. These software parts can be used to define both a source definition file and a software parts file. The next step will be to build and test the associated software parts library.

WEDNESDAY: I started to prepare the test project for the common name routine software parts kit.  The test project (*.tmk) is still a difficult project to set up. I do believe that I will be capable of building a generic version that can be copied and quickly modified. The The basic software parts for writing the “Test Program Step” appears to be easy to write. I plan to make a source definition file rather than a software parts file. Some modifications of the common name routine software parts kit to render it easier to test are expected.

Advertisements

Can Programming Be Strictly Portable Relative To Language?

February 10, 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++.

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.

Can Programming Be Strictly Portable Relative To Language?

October 28, 2011

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 common and C, C#, and Visual Basic typedef software parts library updates have been tested in the stand-alone mode of operation.

SATURDAY: The service class base library, where its client owns the data, is currently being developed. Integration with the modified includes library for C++ has been started.

MONDAY: The service class base library where its client owns the data, is currently being developed. Integration with the modified includes library for C++ has been accomplished. Output source files have been generated. I am currently considering revising the certification parts library to render it possible to certify the output source files using the same source generation files.

For more information and free downloads, please visit my web-site, “www.whatifwe.com”.

PORTABLE SOFTWARE DEVELOPMENT

September 30, 2011

SATURDAY: A major portability problem has been encountered in the Includes library.  Strict portability demands that functionally identical cpp, c, csharp, vbasic source files from exactly the same source generations file.  Unfortunately, the inclusion of system routines requires a different number of references.  In C and C++, there are a varying number of “#include” statements.  In C#, a large number of system routines can be accessed by the “using system;”. I plan to divide the system includes category into a collection of sub-categories. Multiple references to the same system statement will not result in multiple lines in the output source code.

SUNDAY: The C++ and C# Includes libraries have been modified and tested for stand-along use.

MONDAY: The C and VBasic Includes libraries have been modified and tested for stand-along use.

TUESDAY: The C++, C, C#, and VBasic Typedef libraries have been modified by the corresponding Includes library and tested for stand-alone use.

THURSDAY: The development of the Class Base library has been restarted. The following three class types are included: service class; client_class; and the main_class. The service class, where its client owns the data, is currently being developed. Integration with the includes library and typedef library for C++ and C# has been accomplished.

PORTABLE SOFTWARE DEVELOPMENT

August 26, 2011

MONDAY: To properly update the certification software parts library, it is necessary to update the libraries that prepare the output source files.

TUESDAY: A means of updating the certification software parts library that did not require updating the libraries that prepare the output source files was found. Testing of the certification software parts library has been started.

THURSDAY: The testing of Includes software parts library has been completed. Minor changes in  the libraries that prepare the output source files were required. The certification library will need to be further modified relative to testing of the product source code. (Common Criteria, First Article Test, etc).

PORTABLE SOFTWARE DEVELOPMENT

August 21, 2011

FRIDAY: A certification software parts library is used to place the comments into the output source files that facilitate testing for the absence of patches,  Upgrading the interface  between this library and the includes library is the next task.

PORTABLE SOFTWARE DEVELOPMENT

August 19, 2011

FRIDAY: The script software parts library has been successfully used to
write the #include statements into the source file.  Making some minor
Format and file management modifications is next.

MONDAY: The format and file management modifications have been made and
tested.

PORTABLE SOFTWARE DEVELOPMENT

August 5, 2011

FRIDAY: The Include Type (System, Service Class, Client Class,  Data) is not a workable identifier for organizing the *.h file.  An additional identifier must be added to include software parts kit.

MONDAY: The additional identifier has been added to the common (the library used for all output source languages) include software parts kit.

TUESDAY: The additional identifier has been added to the CPP include software parts kit.

THURSDAY: The revised CPP and COMMON Include software parts kits are ready for test.

PORTABLE SOFTWARE DEVELOPMENT

July 29, 2011

SATURDAY: The stand-alone version of the include software parts library is operational relative to the preparation of a script needed to write the CPP #include statements.

MONDAY: In attempting to write the CPP #include statements, it has become apparent that the current script implementation is not as yet adequate. A script is still needed in as much as entries will be made throughout the class-definition sub-task.

THURSDAY: Extensive Script Modifications to the Software parts defining the Common Include library have been prepared. Hopefully, the needed flexibility in script definition and use has been achieved.

PORTABLE SOFTWARE DEVELOPMENT

July 22, 2011

SUNDAY: The Include software parts kit have successfully integrated into the Class Definition sub-task. The Typedef software parts kit is next.

MONDAY: To be able to link the class definition output source code lines to the defining source definition file line number, the class definition steps (Class Definition Beginning, Includes, Typedefs, Routines, Data Structure, and Class Definition Completion) must be defined in one source definition file.

TUESDAY: To be able to use the script software parts to facilitate the writing of the statements associated with the Includes step, the script calling capability must include using a text expression as an argument.

THURSDAY: The script software parts library has been modified. Preliminary functional tests have been performed.