<rant volume="low"> Folks, this node is a good example of how we often take a vague statement of requirements and jump right in to solutions before we're clear on the problem that we're trying to solve. (I'm guilty here, too.)

Take a moment to look at the problem statement we were given to work with. Does it warrant the solutions that have been proposed, or might it be more appropriate to get clarifications before proceeding to code.

Here's what we were given to work with:

1. Find the length of a string.
2. Remove the last two characters from the string.
3. Save the remaining character to a variable.

We can drop item 1) as being a non-requirement. It's really one step towards a possible implementation of 2)

Next we're given an example:

If I had the following strings: "1ST", "21ST" and "101ST", I would like to remove the "ST" and retain the numbers.

At this point we should stand back and ask:

1. Will all input be leading digits plus a two character suffix?
2. Will the suffix always be "ST"? What about "st"? What about "TH"?
3. What should we do with input that isn't leading digits plus a two character suffix?

Only after we get answers to theses are we really in a position to start suggesting implementations. To do otherwise risks having the problem come back to us n more times, each time revealing a new requirement that our solution didn't satisfy.

</rant>