Blogs >> Technology >>
Can Programming Be Strictly Portable Relative To Language?
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++.
SUNDAY: Formal testing of the common routine name software parts has been completed. The common routine software parts will be started. Some upgrades to these parts may be necessary.
TUESDAY: The Formal testing of the common routine name software parts has emphasize the need of well-defined purposes of each of the libraries in the chain leading up to the preparation of the class-defining files. In CPP, there are two additional steps between the class-definition library and what has been accomplished. The first one is a routine common parts library and the second one is a CPP parts library. The previously developed library sets associated with this process (include and typedef libraries) must be subjected to the same formal testing which will result in appropriated upgrades. I have learned an easy means of using the Testing capability of the Programmable Software Development Environment to checkout and thoroughly test a software parts library!
THURSDAY: The common routine software parts associated with loading one or more routines into a class has been thoroughly tested. During these test, a restriction was found; each of the arguments in the definition must have a different name. This restriction might be an inconvenience since common arguments such as an index normally have the same name. On the other hand, it will improve the resulting program from a self-documenting point of view.
SUNDAY: Formal testing of the common routine name software parts has been completed. The common routine software parts will be started. Some upgrades to these parts may be necessary.
TUESDAY: The Formal testing of the common routine name software parts has emphasize the need of well-defined purposes of each of the libraries in the chain leading up to the preparation of the class-defining files. In CPP, there are two additional steps between the class-definition library and what has been accomplished. The first one is a routine common parts library and the second one is a CPP parts library. The previously developed library sets associated with this process (include and typedef libraries) must be subjected to the same formal testing which will result in appropriated upgrades. I have learned an easy means of using the Testing capability of the Programmable Software Development Environment to checkout and thoroughly test a software parts library!
THURSDAY: The common routine software parts associated with loading one or more routines into a class has been thoroughly tested. During these test, a restriction was found; each of the arguments in the definition must have a different name. This restriction might be an inconvenience since common arguments such as an index normally have the same name. On the other hand, it will improve the resulting program from a self-documenting point of view.
|
|
