Introducing the “Welcome to Xojo” Bundle!

New to Xojo and looking for guidance? We've put together a terrific bundle to welcome you! Xojo Bundle

This bundle includes six back issues of the magazine -- all of year 19 in printed book and digital formats -- plus a one-year subscription (beginning with 20.1) so you'll be learning all about Xojo for the next year. It's the perfect way to get started programming with Xojo. And you save as much as $35 over the non-bundle price!

This offer is only available for a limited time as supplies are limited, so hurry today and order this special bundle before the offer goes away!

Article Preview

Buy Now

Issue 4.5


Refactoring REALbasic Code

Improving the Design of Existing Code

Issue: 4.5 (May/June 2006)
Author: Joe Strout
Author Bio: For the first time ever in these pages, Joe Strout is not an engineer at REAL Software. He's now working to replace e-mail with something better, and using REALbasic to do it.
Article Description: No description available.
Article Length (in bytes): 15,183
Starting Page Number: 31
Article Number: 4510
Related Link(s): None

Excerpt of article text...

Conventional wisdom and experience say that you design your code first, and then you actually write the code. This up-front design is important, since if you get it wrong, your code will end up an unusable mess, and you'll be forced to throw it out and start over.

Within the last decade, this conventional wisdom has been turned on its head. Software engineers now routinely change the design of existing code, through a systematic process known as refactoring. Refactoring is more than just another tool in your programming toolbox; it fundamentally changes the way you approach software development. This article will show you how to do it, and what it means for your own work.

What is refactoring?

The term "refactoring" is used in two ways. In the generic sense, refactoring is the process of improving the design of existing code. Refactoring is simply making changes to the architecture of your software, without affecting its behavior.

In the more specific sense, a "refactoring" is a particular way of changing the code. The canonical book on the topic (Refactoring by Martin Fowler) details dozens of specific refactorings, and gives each one a name so that we have a common vocabulary for speaking about them. Some of them are quite simple, like "Rename Method" and "Replace Exception with Test." Others are more complex, like "Extract Method" or "Collapse Hierarchy."

Each refactoring can be broken down into a set of step-by-step instructions, like a recipe. Unlike a recipe, you can actually pause after each step and test the final result -- that is, you can run your program and make sure you haven't changed its behavior. Then, with that assurance in hand, you can proceed to the next step, until the full refactoring is complete. Many of the more complex refactorings use simpler ones among their steps. Having clearly defined, verifiable steps makes refactoring a bit mechanical -- yet deeply satisfying, because you'll see your code growing cleaner before your very eyes.

...End of Excerpt. Please purchase the magazine to read the full article.