Robust-first Computing Wiki

User Tools

Site Tools

Trace:
ulam_programming_conventions

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
ulam_programming_conventions [2015/05/26 09:15] – [Utilities vs Services] ackleyulam_programming_conventions [2015/05/26 09:28] (current) – ackley
Line 19: Line 19:
  
 <code - Evaporator.ulam> <code - Evaporator.ulam>
 +/** \symmetries all */
 element Evaporator { element Evaporator {
   EventWindow ew;   EventWindow ew;
Line 28: Line 29:
  
 <code> <code>
 +/** \symmetries all */
 element Evaporator { element Evaporator {
   Void behave() {    Void behave() { 
Line 37: Line 39:
 even though, in this case, both versions behave identically.   even though, in this case, both versions behave identically.  
  
-The reasoning for this **Make *Utils data members** guidance has an obvious point and a subtle point:  +The reasoning for this **Make *Utils data members** guidance has both obvious and subtle points.  
  
-The obvious point is that since a *Utils is size 0, it doesn't impact the atomic bit budget at all, so it's harmless to make them data members.  Furthermore, placing them as data members makes them available to all methods with a single declaration, and can provide a systematic place (e.g., at the top of the class) for all *Utils declarations.+An obvious point is that since a *Utils is size 0, it doesn't impact the atomic bit budget at all, so it's harmless to make them data members, while conversely, a *Services data member //does// impact the bit budget, so we don't want to do it thoughtlessly.  Furthermore, placing *Utils as data members makes them available to all methods with a single declaration, and also provides a systematic place (at or near the top of the class) for all *Utils declarations.
  
-The subtle point is that even though a *Utils is size 0, when a *Utils method is called, the ''self'' object passed into the called method can differ depending on how the *Utils was declared.  For example, this definition:+A subtle point is that even though a *Utils is size 0, when a *Utils method is called, the ''self'' object passed into the called method can differ depending on how the *Utils was declared.  And that can affect how the called *Utils method behaves.  For example, this definition:
    
 <code - Announcer.ulam> <code - Announcer.ulam>
ulam_programming_conventions.1432631731.txt.gz · Last modified: 2015/05/26 09:15 by ackley