Open Source Software Development Tool: Upgrade Progress

It is planned to upgrade the Programmable Software Development Environment to include the capability of reading the paste-in text files where the each paragraph is one very long line.

Currently, the Programmable Software Development Environment has the capability of reading a standard ASCII text file where the TAB character is replaced with a suitable number of blanks. Each line of the text file cannot be longer than 256 characters. On the other hand, the Programmable Software Development Environment has the capability of writing a paste-in text file where each paragraph is one very long line. This capability includes the ability to include special characters such the TAB.

The ability to read the paste-in text file is needed to certify that the file has not been changed, was developed using the agree-upon standard libraries, or has not been illegally copied.

MONDAY: 2013/01/21

STATUS: Checkout of the updated Programmable Software Development Environment relative to reading a LINUX text file in a WIN32 enviroment has begun.

DETAIL: The files defining this blog, written on my LINUX machine, will be used as the test LINUX text files.

RESULTS: This capability has been successfully tested.

NEXT TASK: Install the updated Programmable Software Development Environment on my LINUX machine and verify proper operation.

TUESDAY: 2013/01/22

STATUS: The updated Programmable Software Development Environment has been successfully installed and tested on my LINUX machine.

DETAIL: To avoid problems resulting from differences between WIN32 and LINUX, the precfile source generation file was appropriate modified. The early forms of the Programmable Software Development Environment are not strictly portable between WIN32 and LINUX.

RESULTS: Release forms of the updated Programmable Software Development Environment were installed on both my WIN32 and LINUX machines.

NEXT TASK: Plan the additional Programmable Software Development Environment commands for reading the long “Paste In” lines.

WEDNESDAY: 2013/01/23

STATUS: To facilitate the certification of long “Paste In” lines, a read command set similar to that of the Buffer Output Command set was selected.

DETAIL: Specifically, the commands will be _BEGIN_READ, _READ_SEGMENT, and _END_READ. Special characters such as the TAB will be returned in the “Name” format. Text data will be returned in the “Text Expression” format.

NEXT TASK: The Buffer Output command can only be done one file at a time.  The equivalent read command set can simultaneously process multiple files. The next task will be to determine if the Buffer Output command set can/should be upgraded to be able to simultaneously process multiple files.

THURSDAY: 2013/01/24

STATUS: I have examined the three Buffer Output commands and have found that there is no reason why they cannot be updated to simultaneously process multiple files.

DETAIL: The primary problem is that the modifications will significantly change the commands and hence the current libraries that use them.

RESULTS: I believe that these changes, particularly if from a user point of view, cause the Write commands to behave in an identical manner with the corresponding Read commands. The command names may need to change; For example, _BEGIN_WRITE, _WRITE_SEGMENT, AND _END_WRITE.

NEXT TASK: Plan the upgrade to the Programmable Software Development Environment to implement the _BEGIN_READ, _READ_SEGMENT, and _END_READ commands.

Tags: , , , , , , ,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.


%d bloggers like this: