2004 World Series

The 2004 season went out with a bang as Boston finally ended the curse.

To paraphrase [[The Bard]]:

…proclaim it, Bellhorn, through my host,

That he which hath no stomach to this fight,

Let him depart; his passport shall be made,

And crowns for convoy put into his purse;

We would not die in that man’s company

That fears his fellowship to die with us.

This day is call’d the feast of Schilling.

He that outlives this day, and comes safe home,

Will stand a tip-toe when this day is nam’d,

And rouse him at the name of Schilling.

He that shall live this day, and see old age,

Will yearly on the vigil feast his neighbours,

And say ‘To-morrow is Saint Schilling.’

Then will he strip his sleeve and show his scars,

And say ‘These wounds I had on Schillings’s day.’

Old men forget; yet all shall be forgot,

But he’ll remember, with advantages,

What feats he did that day. Then shall our names,

Familiar in his mouth as household words-

Manny the King, Ortiz and Martinez,

Millar and Cabrerra, Mueller and Damon-

Be in their flowing cups freshly rememb’red.

This story shall the good man teach his son;

And this day shall ne’er go by,

From this day to the ending of the world,

But we in it shall be remembered-

We few, we happy few, we band of brothers;

For he to-day that sheds his blood with me

Shall be my brother; be he ne’er so vile,

This day shall gentle his condition;

And gentlemen in New England now-a-bed

Shall think themselves accurs’d they were not here,

And hold their manhoods cheap whiles any speaks

That fought with us upon Saint Schilling’s day.

[[2004 World Series YES|show_thumbnail=no]]

Here are a few things that should never be forgotten about the year the [[Red Sox]] finally broke through and ended the curse.

* The incredible comeback after being down 3-0 to the vaunted [[Yankees]], winning 4 straight to take the [[2004 League Championship Series]].
* The timely home runs from [[David Ortiz]] during the [[2004 League Division Series]] against the [[Angels]] to close out that series, during the [[2004 League Championship Series]] to keep the team’s hopes alive, and during the series itself
* The home runs of [[David Bellhorn]] agains the [[Yankees]] during that series to win games
* The home runs of [[Johnny Damon]] during the final game of the [[2004 League Championship Series]] to put the last game out of the reach of the [[Yankees]]
* [[Manny Ramirez]] hitting in 17 straight post season games, tieing the all-time record.
* [[Manny Ramirez]] hitting more RBIs that there were games in the series
** The mythic guts of [[Curt Shilling]], allowing doctors to perform an experimental surgical procedure to sew a tendon in his right ankle in a dislocated position *”*twice*** to pitch the team to victory in game 6 of the [[2004 League Championship Series]] and game 2 of the [[2004 World Series]].
* The stolen base of [[Dave Roberts]] during game 4 of the [[2004 League Championship Series]] against the [[Yankees]] in the 9th inning with 2 outs to put himself in scoring position, and eventually scoring the tieing run to keep the series going
* The pitching of [[Derek Lowe]]. Fans had written him off as a head case, but he ends up winning the clinching games in the [[2004 League Division Series]], the [[2004 League Championship Series]], and the [[2004 World Series]], something that has never been done before
* The unbelievable performance of [[Keith Foulke]] in pitching 18 innings with only one earned run to shutdown anything that came his way

Moon Over St. Louis

The [[Red Sox]] have finally ended an 86 year drought and won the world series by sweeping the [[Cardinals]] in 4.

Well, it’s over.

Could it have been any more symbolic? A curse being lifted under a blood-red total lunar eclipse?

The [[2004 World Series]] went gently into that good night as [[Boston]] finally winning in four straight games.

It seems so obvious now. the [[Red Sox]] won the first world series in 1903, and now have won the 100th edition of the fall classic (there was no world series in 1904 due to a dispute between the [[National League]] and the [[American League]].

World Series Bound

The [[Red Sox]] have completed the greatest comeback in baseball history.

The [[Red Sox]] defeated the [[Yankees]] 10 to 3 in nine innings to earn their way to the [[2004 World Series]].

Congratulations boys. It was spectacular!!!

Game Seven!!!

The [[Red Sox]] did it!


It’s never been done before, but its been done now. All the momentum and intangibles are are in the [[Red Sox]]’ favor.

A-Rod Should be Ashamed

Clearly the umpires made the right call.

Cheaters never win and winners never cheat.

A-Rod, I expected more from you.

I’m sitting here at 11:29pm watching the [[Red Sox]] beating the [[Yankees]] in game 6 of the [[2004 ALCS]]. Jeter makes a clutch hit to drive in a run with one out to make the score 4-2. Suddenly, A-Rod hits a little squib shot down the first base line and while tagging him out, Bronson Arroyo drops the ball. Yikes… here we go again.

Then we get to see the replay. Alex took an illegal swipe at Bronson’s glove to knock the ball out.

First off, why would you cheat like that Alex? I lost a lot of respect for you at that moment. Also, you have a lot of gaul to act surprised like that.

Kudos to the umpires for getting the call right!

C++ Coding Standard

The C++ coding standards were developed to insure consistency throughout our C++ source code. It is the intention of these standards to provide necessary source code consistency, while not being overly restrictive. The standards are conveyed as a set of general rules and source code examples. The standards, as supplied, do not comprise a definitive list. They do however, provide general guidelines to coding style.

##File Layout
###Standard File Header
All C++ source files shall contain the following comment at the top of the file:

// Instrumentation Laboratory
// Copyright (C) 2002. All Rights Reserved.
// FILE:

###Header Files

Header files should always be bracketed by #ifdef, #define, and #endif to ensure that if they are never included more than once.

// Above header comment
# ifndef **_HPP
# define **_HPP

# endif

###Commenting Code
####Interface Documentation

Typically, header files (either .h or .hpp) contain the interface spec for a piece of functionality, whether it is a class, a collection of functions, or a set of global variable extern declarations. The purpose of this file is to describe to the user of this functionality how to use it.

Each class should have a descriptive comment describing what the class is used for. Each function/member function should have a comment describing its functionality and its interface.

Publicly accessible functionality (whether global functions, public member functions or protected member functions) requires the most complete descriptions in the header file. Private, implementation oriented comments should be put in the implementation file (typically a .c or .cpp file).

####Strategic Comments

Strategic comments are used to describe the intended functionality of a block of code, not to describe what the code does (see below). These are meant to help a code maintainer understand the purpose of the code, not the implementation details.

####Tactical Comments

Tactical comments describe what individual pieces of code do. They are especially useful in complicated pieces of code. These are meant to help a code maintainer understand the implementation details of the code.

##Coding Conventions

The purpose of coding conventions is the make code from different developers have a similar appearance making it easier to understand the code. It is not intended to make the code look perfect, as there is no such thing.

* Never use tabs in code. Always use spaces.
* Standard indentation level is 3 spaces
* All control structures shall be indented on level deeper than the level containing them.
* All braces should be on lines by themselves indented to the same level as the block that contains them.
* Complex expressions should be fully parenthesized.
* Line breaks in complex expressions should be before an operator
* Class member names (either functions or variables) should begin with “m_”
* Global variable names should begin with “g_”
* The first letter of the name of a variable of a simple type (not including the above prefix) should be a letter indicating the basic type:
**** “i” for integer types
**** “f” for floating point types
**** “b” for Boolean
**** “e” for enumeration
**** “c” for character

###General Rules
####Prefer Includes in .cpp files

The more that header files include other header files, the more dependencies are created that are not needed. As much as possible, header files should only include other header files that are necessary for the interface being defined.

####Avoid #define
The #define provides no type safety and no scoping.

* Prefer inline functions to macros
* Prefer static const to defined constants
* Prefer enumerations
* Prefer templates
* Use #define only for conditional compilation


Variables should be scoped as tightly as possible. The rationale is that it is trivial to increase the scope of a variable if needed, but reducing the scope can be next to impossible (i.e. the genie is out of the bottle).

####Use const as much as possible

Similar to scoping, taking away constness is trivial, but adding it later is next to impossible. This is especially important with the use of reference variables.

####Prefer exceptions to assert

Assert is non-recoverable. On failure it exits the process. Therefore:

* If the assert is not encountered during testing, the only thing that is known is that the error condition didn’t happen during testing. We don’t know if it will never happen.
* Since we don’t know that it will never happen, we need to write code to properly recover from that error condition.
* Therefore, throw a c++ exception rather than using an assert.

####Always provide a bool expression in control statements

The fact that any non-zero expression results in a true value in control statements should not be depended on.

####When comparing a variable against a constant, the constant shall be to the left of the comparison operator.

This helps ensure that the variable isn’t accidentally assigned to during the comparison by leaving out one of the ‘=’.

####All subsystems should be enclosed in namespaces of the same name.

By enclosing subsystems in namespaces, the use of third party products is easier since the chance of name clashes is greatly reduced.

####Prefer dynamic*cast and static*cast to C-style Casting

C++ provides type-safe casting as part of the language. A c-style cast breaks type safety and makes it more difficult to write robust code

####Prefer descriptive variable names to short names

The more descriptive a variable name is, the easier maintenance is later. This does not mean that variable names should be made artificially long, but rather however long they end up being they should be very descriptive of their intended use.

##C++ Classes
###Prefer STL

STL (The Standard Template Library) is a collection of proven C++ classes that provide functionality for many common programming techniques, for instance stacks, queues, maps, vectors, etc. These are well debugged, well documented classes and should be used instead of re-implementing their functionality.

A good reference for STL can be found at: http://www.cppreference.com/cpp_stl.html
Class Specific Coding Rules

* All classes shall be declared in header files of the same base name
* All classes shall be implemented in source files of the same base name
* Always provide an initialization for every member variable in a constructor
* The C++ language specification specifies that the order of construction of member variables is in the order they are declared, not in the order specified in the constructor. Therefore, in order to avoid invalid implications, the order that the member variables are listed in the constructors should be in the order declared in the class. This is a visual reminder as to the actual construction order which is always the order declared in the class.
* Construct each member on a line by itself. This makes it easier to find.
* Always call a constructor for a base class.
* Avoid multiple inheritance.
* Avoid the use of friends as much as possible. It breaks encapsulation.

####Class Organization

The purpose of a class definition is two-fold

* The first is to tell the compiler information about the class
* The second, and more important from a developers perspective, is to tell a user of the class everything needed in order to use the class. In this sense, it is to be considered a document which describes the usage of the class.
Given that, the class should be organized with this in mind.


* The entire public interface should be defined first. This is the code that any usage of the class requires
* The protected interface is second. This is the code that a derived class implementation needs to understand
* The private interface is third. This is only relevant to the implementation of the class.


In order to preserve as much encapsulation as possible, the scoping in classes should be as tight as possible.

* Every member (either function or variable) should be private unless it is needed by derived classes or public users.
* If not private, every member should be protected, unless it is needed by a public user
* Anything needed by a public user.

###Constructors and Destructors

####Always declare default constructors and assignment operators

C++ provides default implementations for the default construct, the copy constructor, and the assignment operator if not declared in the class specification. These default implementations are wrong most of the time. By providing at least a declaration of these, it prevents the automatic creation of them by the compiler.
If the class has no use for any of these, the declarations should still be made in the private interface, and no implementation needs to be provided. This will catch at compile time any external reference to these, and at link time any reference in the class.

####All destructors should be virtual

Vanila Markup Language

You don’t need anything fancy to produce beautiful documents in Vanila.

##Text markup

Test surrounded by:
** ***: rendered as bold.
* ”: rendered as italic
* **: rendered as underlined

***’This””” ”is” ””a”” ””””””test”””’***.

is rendered as:

***’This””” ”is” ””a”” ””””””test”””’***.

##Block Quotes

Consecutive lines beginning with whitespace are grouped together as a blockquote.

This is a


Note that the blank lines above have

blank whitespace so that they end up

inside the blockquote.

Renders as:

This is a


Note that the blank lines above

have blank whitespace so that they end up

inside the blockquote.


Headlines are used to divide a document into sections. Headlines in Vanila are defined by beginning lines with 3 or more asteriks. the more asteriks, the higher the level of headling.


##Level 1
###Level 2
####Level 3
####Level 4

Renders as:
##Level 1
###Level 2
####Level 3
####Level 4


* Bulleted lists are specified by a group of lines beginning with ‘-‘
* Number lists are specified by a group of lines beginning with ‘#’
* Definition lists are specified by a group of lines beginning with ‘?’. A ‘:’ separates the term from the definition.
* Lists are nested by indenting the ‘-‘ or ‘#’ by multiples of 2 spaces (once for each nest level).

####Bulleted List

* This
* Is
* A
* List

Renders as:
* This
* Is
* A
* List

####Ordered List

# One
# Two
# Three
# Four

Renders as:
# One
# Two
# Three
# Four

####Definition List

? One : Definition of One
? Two : Definition of Two

Renders as:
? One : Definition of One
? Two : Definition of Two

####Mixing and Matching

* Bullet 1
* Bullet 2
# number 1
# number 2
? One : Definition of One
? Two : Definition of Two
# number 3
* Bullet 3

Renders as:
* Bullet 1
* Bullet 2
# number 1
# number 2
? One : Definition of One
? Two : Definition of Two
# number 3
* Bullet 3


Tables are described by lines starting with ‘|’. Each ‘|’ represents the beginning of a new cell in the table. Optionally, immediately after the ‘|’:
** **h* means that the cell is a header
** **c followed by a number* means that the cell spans that many columns
** **r followed by a number* means that the cellspans that many rows

Leading and trailing spaces in each of the cells is ignored, so that you can use this space to help align the columns visually in the text.


|h This |hc3 Is
|r2 A | Test of | the |r2 Emergency
| Broadcast | System

Renders as:
|h This |hc3 Is
|r2 A | Test of | the |r2 Emergency
| Broadcast | System

##Cross References

* Enclose text in quotation marks
* Enclose text in double [ brackets


[[Vanila Markup Language]] is a cross reference to [[Vanila Markup Language]],
and [[Example Forward Reference]] makes a link to an undefined page.

Renders as:

[[Vanila Markup Language]] is a cross reference to [[Vanila Markup Language]], and [[Example Forward Reference]] makes a link to an undefined page (please don’t define this page so that the above reference makes sense). Note that if you are not logged in as a member, the forward cross reference example will appear as plain text.

###Special Cross References

Certain document types have special cross reference handling. Using the above syntax with a reference to a Picture document includes the picture in the page. A cross reference to a Shortcut inserts a reference to the URL specified in the shortcut.

For instance, typing:

[[Apple]] [[mac]]


[[Apple]] [[mac]]

##Horizontal Lines

Horizontal lines are made a line of three ‘-‘ by themselves.


This is a horizontal rule

Renders as:

This is a horizontal rule

##Verbatim text
Text that is surrounded by: