Ruby Object Model Diagram

How does ruby internally represent and connect classes objects superclasses etc.

Ruby object model diagram. Everything is an object. You can open your irb console and see it for yourself by typing. You can t get very far into ruby land without hearing that phrase. So if you re a ruby programmer you probably know that everything in ruby is an object.

It shows a snapshot of the detailed state of a system at a point in time thus an object diagram encompasses objects and their relationships which may be considered a special case of a class diagram or a. But another thing that s worth noting is ruby objects hierarchy. A diagram showing superclass and eigenclass links between ruby objects but not the module inclusion links is available at www atalon cz. When you write ruby code you are inside a main object that s why you can just write puts hello world instead of kernel puts hello world.

The interesting thing is how those objects are linked together and classified. Likewise a static uml object diagram is an instance of a class diagram. Since 11 january 2012 there is a diagram containing module inclusion links. Hash array string integer and float.

Using class ancestors included modules and superclass diagram the object model of these several commonly used ruby classes. Object is an instance of a class in a particular moment in runtime that can have its own state and data values. Differently from languages like java and c. Ruby s extreme decoupling and duck typing philosophy doesn t judge a class by its hierarchy.

For ruby this post probably doesn t contain much new stuff for you. It s true though everything in ruby is an object. We now have a mental model for how ruby manages classes instances superclasses and modules but why does it matter. Object includes the kernel module so object has all the instance methods of kernel like puts gets exit.

Since ruby 1 9 its hierarchy is like this. Umlify uses yuml probably the most used uml textual tool to render the diagram. There are just a few things that exist in ruby that you need to understand to really grok its object model. As part of my compiler project one of my imminent decisions is what object model to use and sine i like ruby it seemed a good time to go through ruby and look at the guts of the ruby object model if you ve dabbled in meta programming etc.

If you re a beginner you may want to look at a tutorial instead. This is not an easy task since as the author comments.