TweetFollow Us on Twitter

September 90 - Meta-spaghetti

Meta-spaghetti

Donald E. Carlile

(BILL: I FORGOT TO GET A COMPANY NAME FROM DON. WANT TO GIVE IT A SHOP?)

I'm a fairly conscientious programmer-I like to think I write good clean code; I take the trouble to use modular techniques; I even stood on my head to learn object-oriented techniques. But in spite of all this, I found out I was writing spaghetti.

Spaghetti code! Someone still uses GOTO!?

Well, possibly I exagerrate: I don't mean spaghetti code in the old BASIC GOTO sense-```I mean spaghetti code that is only possible when you are writing in an OOP language. Maybe we'd better call it meta-spaghetti.

I found I was writing meta-spaghetti when I was asked by someone if I would let him use some of my objects. I had known I had only one unit, but I hadn't realized how tangled it was. It was then that I developed the term meta-spaghetti to define the condition of my code.

What I mean by meta-spaghetti is objects which refer to each other recursively. That is, objects which in their definitions include fields of each other's type, as in

TMyDocument = OBJECT(TDocument)
	
	fStar : TStar;
	…

	TStar = OBJECT(TObject)

		fMyDocument : TMyDocument;
	…

This leads to strange loops and to units which cannot easily be decomposed into simpler entities.

As anyone who has read even part of Hofstader's Gödel, Escher, Bach knows, it is impossible to entirely banish strange loops: you made that reference in the object definition for some reason, and it cannot be easily abandoned without some thought and work. That being said, you might still want to introduce some measure of isolation between your objects.

I can tell you from experience that it is difficult to undo the damage once it's done. As I was unraveling my code, however, I developed some guidelines for avoiding and dealing with meta-spaghetti. Perhaps they will prove helpful to you as well, as you design your code from the beginning to avoid this condition.

1. References should only to be to objects down the ownership chain.

As I was defining my set of rules, this is the first one that became apparent: when defining an object, references can be made to the internals of the objects it owns. This is what I mean by references down the ownership chain. (For a more complete discussion of the ownership chain, see the author's Chains Required, Whips Optional, an unpublished, and indeed unwritten, article.)

As an example, in my Trek-style game I had a method to add text to a textedit window. This method belonged to my document object. In order for my ship objects to add text about their status to the window, they had to have a reference to my document object. This caused a problem when I wanted my ship objects in a separate unit so that others could use them.

I solved this problem by changing the way I added text to the window. Instead of calling the document method, I added a text handle field to the ship object. I then changed my document DoIdle to check the texthandle of each ship object. In this way I followed the rule of having only references down the ownership chain.

If this rule is followed, the separation of objects into units becomes very clear and simple. There is no confusing interdependence of objects, and it is clear what the unit dependencies should be.

There is only one problem with this rule: it's not always possible or desirable to follow it. Some objects need to be interrelated; when this is the case, they probably should not be separated. This brings us to the next rule:

2. When it is impossible to remove references between objects, include them in the same unit.

The universe of my game is defined by two object types, TGalaxy and TQuadrant. These two object types refer to each other quite a lot, and it makes a great deal of sense for them to both be in the same unit. It is also unlikely that they would need to be separated to be reused. Therefore, I have put them into their own unit.

3. When it is impossible to untangle references and they must be in separate units, define a new object to make the references and push it down the ownership chain.

Don't be afraid to revise your structure. Although it will save you work to think out your structure ahead of time, sometimes this proves impossible. When you find you have painted yourself into a corner, cut a new doorway.

In my original design, my TMyDocument object owned all the lists of quadrants and other data containers. Thus, all my data objects referred back to it in order to refer to each other. When I wanted to separate out my ships, stars and quadrants into other units to make them usable elsewhere and to decrease compile time, I found the task impossible.

I then defined a new object, a TGalaxy, to contain all the objectionable fields and methods (no pun intended) and made a new field in the revised TMyDocument object to refer to an instantiation of TGalaxy. This made it possible to cleanly make the separation.

Make vanilla references when Rule 1 is impossible.

Another strategy for avoiding meta-spaghetti is to make references to the parent type rather than the type that is giving you trouble. This is not always possible, but sometimes the method or field you need to reference is contained in the object's parent or ancestor.

In my game, I call the draw method of my TQuadView object type from one of the methods of TQuadrant. I do this to avoid the flicker introduced when I use the invalid rectangle methods of MacApp. Originally TQuadrant included a field fMyDocument of type TMyDocument. TMyDocument, of course, had a reference to an fQuadView, of type TQuadView. TQuadView was a specialized descendant of TView. When I needed to do a drawing, I called fMyDocument.fQuadView.Draw. In this way, TQuadrant absolutely needed to be in the same unit as TQuadView. It was also specifically geared to my application only.

To untangle this particular mess, I added a field fQuadView, of type TView, to my TGalaxy object. Since variables of an ancestor type can contain any descendent, this field can contain an object of the specialized type TQuadView. The only limitation is that specialized fields and methods may not be called using this reference.

At the time an object of type TQuadView is made, it is passed to fGalaxy of the TMyDocument. Then I can call Draw, since Draw is one of the methods of the ancestor TView class.

5. Define proto-objects for objects up the chain when Rule 1 is impossible.

Sometimes all the above rules fail: you still want to break up objects into different units but they can't come completely apart. When this happens, it is important to remember that it is permissible to define objects or abstract classes which have no instantiation. You can define these "proto-objects" to contain those fields and methods which are necessary for the objects lower down the ownership chain and can include these classes in the same unit with those objects. Then USE that unit in the unit which defines the real objects and make them descendants.

As I mentioned earlier, TGalaxy and TQuadrant define the universe of my game. I found it impossible to completely divorce these objects from the objects I refer to, i.e., my ships, stars, bases,and torpedoes. I reasoned further that any structure which made use of my entities would also need some kind of quadrant and galaxy. I then defined a TProtoGalaxy and TProtoQuadrant, which had references for the fields and methods necessary for my entity unit, while not burdening the unit with the heavy details and the bulk of the fields and methods. I then defined TGalaxy as a descendant of TProtoGalaxy and TQuadrant as a descendant of TProtoQuadrant.

This one might be just a bit tricky to follow. Let me try and restate it thusly: the Galaxy and Quadrant objects have several fields and methods which ships and things need to reference. Two examples of such fields are the galaxy array and the list of other entities in the quad. An example of a referenced method is the one which detects when collisions occur. I therefore defined objects, which I call proto-objects, which contain references to these things. I don't define the methods-e.g., the collision procedure in the protoQuad consists of a Begin and an End, as do the rest of the methods in my proto-objects. In a different unit I then create descendants of the proto-objects with all the fields and fleshed-out methods fully defined.

I don't claim that these rules are the simple once-and-for-all solution to the problem of meta-spaghetti, but they are a start. You can probably come up with a few rules and methods of your own. Good luck!

Rules for avoiding meta-spaghetti:

  1. References should only to be to objects down the ownership chain.
  2. When it is impossible to remove references between objects, include them in the same unit.
  3. When it is impossible to untangle references, and they must be in separate units, feel free to define a new object.
  4. Make vanilla references when Rule 1 is impossible.
  5. Define proto-objects for objects up the chain when Rule 1 is impossible.

If you have any questions or comments for Don, he can be reached on AppleLink at N0231.

 

Community Search:
MacTech Search:

Software Updates via MacUpdate

Latest Forum Discussions

See All

Can PokeMatch help you find love with Po...
The unofficial Pokemon GO companion app space has exploded almost as fast as the game itself over the last few weeks. Aspiring app developers, many of them working solo, have given us apps that locate Pokemon, keep track of the server status, and... | Read more »
How to get started with Prisma
If there's one thing people like to do more than taking pictures with their smartphones, it's tinkering with those photos in some way. Numerous apps have sprung up over the last several years that allow you to use filters and special effects to... | Read more »
6 Pokemon GO updates you can expect, acc...
Pokemon GO had a scheduled appearance at this year's San Diego Comic-Con for a while, but it was only relatively close to the show that it was upgraded to a spot in Hall H. That's the biggest venue at SDCC, one usually reserved for the largest... | Read more »
How to evolve Eevee in Pokemon GO
By now, almost everyone should be hip to how to evolve Pokemon in Pokemon GO (and if not, there's a guide for that). Just gather enough candy of the appropriate type, feed them all to the Pokemon, and evolution happens. It's a miracle that would... | Read more »
CSR Racing 2: Guide to all game modes
It might not seem like there are all that many ways to go fast in a straight line, but CSR Racing 2 begs to differ. [Read more] | Read more »
Bulb Boy (Games)
Bulb Boy 1.0 Device: iOS Universal Category: Games Price: $2.99, Version: 1.0 (iTunes) Description: Multi-award winning 2D point & click horror adventure about a boy with a glowing head. | Read more »
5 top free emoji keyboard apps
If we're not at peak emoji yet as a society, it feels like we definitely should be. The emoji concept has gone far beyond what anyone in Japan could have envisioned when the people there unleashed it on an unsuspecting world, but the West has... | Read more »
How to unlock more characters in Disney...
One of the big charms of Disney Emoji Blitz is seeing a wide variety of beloved Disney and Pixar characters transformed into smiling emojis. Even someone like the sneaky Randall from Monsters Inc., who probably never cracked a smile on film, is... | Read more »
Cubway (Games)
Cubway 1.0 Device: iOS Universal Category: Games Price: $1.99, Version: 1.0 (iTunes) Description: Cubway is a journey with an abstract story of lifecycle of rebirth, called Samsara. Guide the cube through the long way full of dangers... | Read more »
Colorcube (Games)
Colorcube 1.0 Device: iOS Universal Category: Games Price: $1.99, Version: 1.0 (iTunes) Description: Turn pieces and blend colours in this minimal yet visually stunning puzzler.Over 200 handcrafted and challenging levels. Features... | Read more »

Price Scanner via MacPrices.net

GSK Rheumatoid Arthritis Study Leverages iPho...
Global healthcare products company GlaxoSmithKline (GSK) says that since 2014 they have begun transforming the way they conduct research, by leveraging state-of-the-art digital technologies — a... Read more
Clearance 12-inch Retina MacBooks, Apple refu...
Apple has Certified Refurbished 2015 12″ Retina MacBooks available starting at $929. Apple will include a standard one-year warranty with each MacBook, and shipping is free. The following... Read more
13-inch Retina MacBook Pros on sale for up to...
B&H Photo has 13″ Retina MacBook Pros on sale for up to $150 off MSRP. Shipping is free, and B&H charges NY tax only: - 13″ 2.7GHz/128GB Retina MacBook Pro: $1199 $100 off MSRP - 13″ 2.7GHz/... Read more
13-inch 1.6GHz/128GB MacBook Air on sale for...
Amazon has the 13″ 1.6GHz/128GB MacBook Air on sale for $200 off MSRP for a limited time. Shipping is free: - 13″ 1.6GHz/128GB MacBook Air (sku MMGF2LL/A): $799.99 $200 off MSRP Their price is the... Read more
13-inch 1.6GHz/256GB MacBook Air on sale for...
Amazon has the 13″ 1.6GHz/256GB MacBook Air on sale for $200 off MSRP for a limited time. Shipping is free: - 13″ 1.6GHz/256GB MacBook Air (sku MMGG2LL/A): $999.99 $200 off MSRP Their price is the... Read more
Free iOS Business App notably* Helps Service...
PayStudio Inc. has introduced their new business app notably* 1.0, developed for iPhone and iPod touch. notably* was specifically developed to help service and trade professionals go digital and... Read more
27-inch iMacs on sale for $200 off MSRP
Amazon has 27″ iMacs on sale for $200 off MSRP including free shipping: - 27″ 3.3GHz iMac 5K: $2099 $200 off MSRP - 27″ 3.2GHz/1TB Fusion iMac 5K: $1799.99 $200 off MSRP - 27″ 3.2GHz/1TB HD iMac 5K... Read more
Mac Pros on sale for $200 off MSRP
B&H Photo has Mac Pros on sale for $200 off MSRP. Shipping is free, and B&H charges sales tax in NY only: - 3.7GHz 4-core Mac Pro: $2799, $200 off MSRP - 3.5GHz 6-core Mac Pro: $3799, $200... Read more
Save up to $600 with Apple refurbished Mac Pr...
Apple has Certified Refurbished Mac Pros available for up to $600 off the cost of new models. An Apple one-year warranty is included with each Mac Pro, and shipping is free. The following... Read more
Apple price trackers, updated continuously
Scan our Apple Price Trackers for the latest information on sales, bundles, and availability on systems from Apple’s authorized internet/catalog resellers. We update the trackers continuously: - 15″... Read more

Jobs Board

*Apple* Retail - Multiple Positions, Willow...
Job Description:SalesSpecialist - Retail Customer Service and SalesTransform Apple Store visitors into loyal Apple customers. When customers enter the store, Read more
*Apple* Evangelist - JAMF Software (United S...
The Apple Evangelist is responsible for building and cultivating strategic relationships with Apple 's small and mid-market business development field teams. This Read more
*Apple* Solutions Consultant - APPLE (United...
Job Summary As an Apple Solutions Consultant, you'll be the link between our future customers and our products. You'll showcase your entrepreneurial spirit as you Read more
*Apple* Professional Learning Specialist - A...
Job Summary The Apple Professional Learning Specialist is a full-time position for one year with Apple in the Phoenix, AZ area. This position requires a high Read more
*Apple* Picker - Apple Hill Orchard (United...
Apple Hill Orchard, Co. Rte. 21,Whitehall, NY 9/7/16-10/228/16. Pick fresh market or processing apples Productivity of 60 boxes and 80 boxes processing fruit per Read more
All contents are Copyright 1984-2011 by Xplain Corporation. All rights reserved. Theme designed by Icreon.