Databases
StackOverflow2013
Postsdbo
POwhich GOF Design pattern(s) has entirely different implementation (java vs Scala)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POwhich GOF Design pattern(s) has entirely different implementation (java vs Scala)
    primarykey
    data
    text
    <p>Recently I read following SO question : </p> <blockquote> <p>Is there any use cases for employing the Visitor Pattern in Scala? Should I use Pattern Matching in Scala every time I would have used the Visitor Pattern in Java?</p> </blockquote> <p>The link to the question with title: <a href="https://stackoverflow.com/questions/8618082/visitor-pattern-in-scala">Visitor Pattern in Scala</a>. The accepted answer begins with</p> <blockquote> <p>Yes, you should probably start off with pattern matching instead of the visitor pattern. See this <a href="http://www.artima.com/scalazine/articles/pattern_matching.html" rel="nofollow noreferrer">http://www.artima.com/scalazine/articles/pattern_matching.html</a></p> </blockquote> <p>My question (inspired by above mentioned question) is which GOF Design pattern(s) has entirely different implementation in Scala? Where should I be careful and not follow java based programming model of Design Patterns (Gang of Four), if I am programming in Scala?</p> <p><strong>Creational patterns</strong></p> <ul> <li>Abstract Factory</li> <li>Builder</li> <li>Factory Method</li> <li>Prototype</li> <li>Singleton : <em>Directly create an Object (scala)</em></li> </ul> <p><strong>Structural patterns</strong></p> <ul> <li>Adapter</li> <li>Bridge</li> <li>Composite</li> <li>Decorator</li> <li>Facade</li> <li>Flyweight</li> <li>Proxy</li> </ul> <p><strong>Behavioral patterns</strong></p> <ul> <li>Chain of responsibility</li> <li>Command</li> <li>Interpreter</li> <li>Iterator</li> <li>Mediator</li> <li>Memento</li> <li>Observer</li> <li>State</li> <li>Strategy</li> <li>Template method</li> <li>Visitor : <em>Patten Matching (scala)</em></li> </ul>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USOptimight
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POwhich GOF Design pattern(s) has entirely different implementation (java vs Scala)
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POwhich GOF Design pattern(s) has entirely different implementation (java vs Scala)
      1. This table or related slice is empty.
      1. VTDownMod
    3. VO
      singulars
      1. POwhich GOF Design pattern(s) has entirely different implementation (java vs Scala)
      1. This table or related slice is empty.
      1. VTUpMod
    1. COA lot of these design patterns are just work around the absence of first class functions.
      singulars
      1. POwhich GOF Design pattern(s) has entirely different implementation (java vs Scala)
      1. USDaniel C. Sobral
    2. CO@ Daniel C. Sobral Sir, Which are the patterns I should critically study and replace it with first class functions. Currently my mind is structured to think in terms of these Design Patterns to solve the programming task.
      singulars
      1. POwhich GOF Design pattern(s) has entirely different implementation (java vs Scala)
      1. USOptimight
    3. CO@DanielC.Sobral, I'd say rather that first-class functions make it easier to implement the patterns. In most cases I don't think having first-class functions invalidates the pattern entirely.
      singulars
      1. POwhich GOF Design pattern(s) has entirely different implementation (java vs Scala)
      1. USThe Archetypal Paul
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload