View this PageEdit this PageAttachments to this PageHistory of this PageHomeRecent ChangesSearch the SwikiHelp Guide
Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007

Discussion 2 Vasilios Pantazopoulos

Part 1)
4)

http://c2.com/ppr/about/portland.html

The Portland Form is a style of description of a language pattern which lays out the pattern in an easy to read form. Basically, it's simply a formal way to describe the patterns and their interactivity through the use of technical writing. It's set up as a series of paragraphs, some which describe a "force" to be dealt with and how to deal with it, and others which simply summarize the language patterns in their own way.

If well constructed, a pattern documented in Portland Form could not only be thoroughly educational, but also extended easily for use with another pattern. The Form itself just provides for a standardized way of looking at these patterns and analyzing them. Having them documented in this way allows for the pattern to be easily learnedand tweaked in order to create a new way of thinking in Object Oriented.

Part 2)

http://c2.com/ppr/temps.html

Temporary Variables - Simply a pattern which describes the use of temporary variables in order to be more efficient and for better readability.
It describes tactics such as:
Collecting Temporary Variables - Describes the use of a temporary variable to hold a collection or merge of other objects
Caching Temporary Variables - The primary use of temporary variables for efficiency, details the use of temporary variables for reuse so that instead of calculating multiple times in a loop, use the variable instead
Explaining Temporary Variables - Use temporary variables in order to help explain complex methods by helping simplify the techniques used
Reusing Temporary Variables - Improves readability (similar to caching), where a constant is reused in a variable form
Role Suggesting Temporary Variable Names - Similar to Explaining, its a method of using variable names to explain their use in the program, again, another way to prove readability

This pattern is very simple, and very easy to use. As for it's possibilities for help in readability, it seems like a very good idea to use it. I would use it often, in that as long as it helps me remember what the purpose of what I wrote was. This seems hard to explain now, because it seems like common sense that it's easier and more readable.

Links to this Page