Posts Tagged ‘script based programming’

Can Programming Be Strictly Portable Relative To Language?

March 19, 2013

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: 2013/03/19

STATUS: The software parts for generating and running the format
scripts has been modified to use a post office rather than a local
dictionary.

DETAIL: This will render it possible to define a standard format set
separately from its use.

NEXT TASK: I have not forgotten about the software parts associated
with calling a format.  The next task will be to prepare format
commands associated with adding a pseudo-random string of blanks.  This
will be used as a means of protecting proprietary information.  A
varying number of blanks at the end of each line is hard to visually
detect and is a very good means of making the source files detectably
unique.

Advertisements

Development of Script Utility Libraries

February 20, 2013

The effort associated with the development, upgrading and testing the  script software parts library will be documented here. Specifically, the script software parts library will be upgraded to behave more like a software part. It will also be formally tested.

The software parts of the script library are currently being updated so that one or more parameters can be passed to the script at the _RUN_SCRIPT execution level.

WEDNESDAY: 2013/02/20

STATUS: The capability of passing parameters from the _RUN_SCRIPT level has been implemented. Formal tests have been started.

RESULTS: The formal tests performed have indicated that the new capability is functional.

NEXT TASK: Formal testing of this new capability will continue. This new capability will now be used in the development of the common source output language which is documented in the portability blog.

Development of Script Utility Libraries

February 19, 2013

The effort associated with the development, upgrading and testing the
script software parts library will be documented here. Specifically,
the script software parts library will be upgraded to behave more like
a software part. It will also be formally tested.

The software parts of the script library are currently being updated so
that one or more parameters can be passed to the script at the
_RUN_SCRIPT execution level.

TUESDAY: 2013/02/19

STATUS: The capability of passing parameters from the _RUN_SCRIPT level
has been implemented and appears to be functional.

NEXT TASK: Formal testing of this new capability will begin.

Development of Utility Libraries

November 2, 2012

The activity associated with development of utility software parts libraries will be presented here.

The effort associated with the development, upgrading and testing the  script software parts library will be documented here. Specifically, the script software parts library will be upgraded to behave more like a software part. It will also be formally tested.

SCRIPT MONDAY ACTIVITY: Being able to pass parameters to the script in the _RUN_SCRIPT command is next script library upgrade to be performed. I have now included the capability of insuring that the _BEGIN_RUN_SCRIPT, the _RUN_SCRIPT_ARGUMENT, and the _END_RUN_SCRIPT software parts are used in the proper order.  The next step is to prepare the _RUN_SCRIPT_ARGUMENT software part.

Can Software Be Assembled Not Written?

November 2, 2012

The software part is roughly equivalent to an integrated circuit. Can we assemble a software product in a manner similar to producing a a hardware product?

I believe that it is possible assemble a software product without any intimate knowledge of the product’s source language. Instead of writing the code in a computing language such as C++, the appropriate software parts will be selected from a system of menus.

This blog will be used to document my research and development efforts associated with a menu-driven product assembly capability.

ASSEMBLY THURSDAY ACTIVITY: The best way of creating the Programmable Software Development Environment capability for finding files, adding new directories,  compare file modification dates, and finding paths is to add an software parts instruction for launching a executable. This will enable a command-line script to be processed.

Development of Utility Libraries

October 19, 2012

The activity associated with development of utility software parts libraries will be presented here.

The effort associated with the development, upgrading and testing the  script software parts library will be documented here. Specifically, the script software parts library will be upgraded to behave more like a software part. It will also be formally tested.

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…

SCRIPT FRIDAY ACTIVITY: Being able to pass parameters to the script in the _RUN_SCRIPT command is next script library upgrade to be performed. In as much as I do not want to lose the use of this library for any length of time, this upgrade process will performed slowly with tiny steps.

Can Programming Be Strictly Portable Relative To Language?

October 12, 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++.

THURSDAY: Currently, I believe that the common name problem can be resolved using the script calling capability of the script software parts library. This require a different form of certification chain capabilities which will probably require upgrading the certified copy library. The script software parts library has been sufficiently upgraded that I should be able to restart this development activity.

Development of Utility Libraries

September 28, 2012

The activity associated with development of utility software parts libraries will be presented here.

The effort associated with the development, upgrading and testing the  script software parts library will be documented here. Specifically, the script software parts library will be upgraded to behave more like a software part. It will also be formally tested.

SCRIPT THURSDAY ACTIVITY: The modifications of the calling load commands have been made and partially tested. The testing of this command can only be completed when these calling commands are executed. The inclusion of this error detection software part will continue.

Development of Utility Libraries

September 21, 2012

The activity associated with development of utility software parts
libraries will be presented here.

The effort associated with the development, upgrading and testing the
script software parts library will be documented here. Specifically,
the script software parts library will be upgraded to behave more like
a software part. It will also be formally tested.

SCRIPT TUESDAY ACTIVITY: I have prepared an error software part that
detects a lack of initial preparation before loading the commands. The
implementation of this software part is progressing. The modifications
of the calling commands will be performed next. This will include the
inclusion of this error detection software part.

Development of Utility Libraries

September 7, 2012

The activity associated with development of utility software parts libraries will be presented here.

The effort associated with the development, upgrading and testing the  script software parts library will be documented here. Specifically, the script software parts library will be upgraded to behave more like a software part. It will also be formally tested.

SCRIPT FRIDAY ACTIVITY: This script calling and data loading software parts have been modified. Unfortunately, these modifications look very much like a patch and I am not satisfied with my first efforts. I will re-examine these software parts and make the necessary modifications to clean up my work-products.

SCRIPT SATURDAY ACTIVITY: I believe that I have made the required modifications to clean up my work-products. I believe that the next step is to formally test this capability.  I have not as yet provide the needed modifications to provide the parameters of a script from the parameters of the _RUN_SCRIPT software part. It is my current plan to make these modifications after I test the script-calling commands.

SCRIPT TUESDAY ACTIVITY: During the check-out/test process of the script calling commands I discovered another error detection deficiency in the script software parts library. Specifically, the script software parts are capable of defining multiple scripts pretty much at the same time (there are a few exceptions).  Unfortunately I did not prepare an error software part that detected a lack of initial preparation before loading the commands. This will be fixed next.