Monday, June 4, 2012

Application.Orbs: Extend Anything Onto Object Classes

“Periodic Table of [Well-Known] Elements,” that sounds more practical than the system of all atoms with every possible orbital in observable positions despite not everyone's first-person, all said, possible phenomena. It is the difference between containers and the non-containable. Maybe you realized there is the more appropriate table than the said offset, upside-down bikini ion, but it hasn't changed for awhile. Maintenance cost weighs-in if you want that to look good. Obviously the universities studied that cost factor and stayed ahead in the art of their own periodic addition. Their addition is not always well-known to everybody, however, but everybody wants to show-off their best extensible class.

Some people got smart and kept the maintenance of the (virtual) machine out of the cost of language. Yes, people were taught in class that it was the same thing. Maybe they only wanted the one cost factor and not more than one because it was easier on the books. The problem there is that it required specialization, like student loans. People objected.

“Did you mean the CORBRA apps?” No, yet you see how that started if you are familiar enough with the language, or the art of it. Someone, like me, wanted beyond that art (of insurance/debt-resolution). Comments are useless without intent known.

It is an elemental manipulation when we compose objects out of space, like something from nothing. The debate runs deep.

The class I have put together below considers such manipulations by orbital data. Usually containers use the linked-list or double-linked list, and I have said prior-art on this trinary version without such container perspective. What is the periodic element here if I can replace the VM with another that manipulates the same atomic structure by proven logic flow? Besides “cost”, [...to be continued].

[Note: Over the last 20 years, people used (code) certifications as patent acquisition schemes. Sounds good? How much do you like underwriters.]

using System ;

namespace Application.Orbs
        {
        public abstract class Orbital
                {
                public Orbital
                        orbit ,
                        internet , s ;
                }
               
        public partial class Orb : Orbital
                {
                static protected Orbital alpha = new Orb() ;
                public Orbital Orbit
                        {
                        set
                                {
                                if( orbit == value.orbit )
                                        return;
                                if( value.orbit != null )
                                        {
                                        if( value.orbit.internet == value )
                                                value.orbit.internet = value.s ;
                                        else
                                                {
                                                Orbital o = value.orbit.internet ;
                                                while( o.s != value )
                                                        o = o.s ;
                                                o.s = value.s ;
                                                }
                                        value.orbit = null ;
                                        }
                                if( orbit == null )
                                        return ;
                                value.orbit      = orbit ;
                                value.s            = orbit.internet ;
                                orbit.internet   = value ;
                                }
                        }
                public Orb()
                        {
                        orbit = alpha ;
                        }
                }
        }