bor

• About: Perl Developer from Ukraine.

Recent Actions

• Commented on Scratching an itch - interpolable HTTP Status constants
  What is the problem with hash keys? my %hash = ( HTTP_OK() => 'OK', );...
• Commented on Inheritance is Bad: Code Reuse Part I
  Please continue :)...
• Commented on HTTPS-Everywhere rulesets for Perl sites
  Great stuff! Thanks....
• Commented on YAPC::Europe 2011 Day 3
  Could I find video anywhere ?...
• Commented on Plack basics - talk at YAPC::EU 2011
  Thanks for sharing slides. And waiting for video :)...

Recent Actions from bor

Comment Threads

• Robert Rothenberg commented on Scratching an itch - interpolable HTTP Status constants

  Actually, scratch that last reply. I misread it.

  Yes, you can use %hash = ( HTTP_OK() => ... ) or ${\ HTTP_I_AM_A_TEAPOT } but the code is a bit ugly.

  Admittedly, this module does add extra dependencies (although some like Package::Stash are used elsewhere, e.g. Moose).
  

• trp commented on Inheritance is Bad: Code Reuse Part I

  OOP solves the problems you describe with interfaces. Clean, simple, no muss, no fuss.

• Sid Burn commented on Inheritance is Bad: Code Reuse Part I

  Yes,
  interfaces solve Part of it. The Problem is that interfaces itself don't have Code Reuse because their are just interfaces.

  In Part II i describe a solution with Roles. That somewhat gives you what interface have plus an implementation.

  But in Part III i also explain the drawbacks of Roles and that it also makes sense to use Composition instead of Roles.

• mssestak commented on Inheritance is Bad: Code Reuse Part I

  Term you are searching for is tetrapod (or Tetrapoda), which includes amphibians, reptiles, birds, and mammals :).
  See here on Encyclopedia of Life: http://eol.org/pages/4712200/overview .
  BTW, Nice series of articles.

• Sid Burn commented on Inheritance is Bad: Code Reuse Part I

  "Tetrapod" is only for 4-legged animals. For example a snake can also swim and move on the land, but is not a Tetrapod.

  I think one of the main thing i want to explain here is: Even if you find a term to describe something it makes more sense to just use the behaviour names. Because the pure simple behaviour names will never "collide" with something. That means you want to use the behaviour coded in a class but it doesn't make sense to inherit from it.

  If you want to reuse your "swim-movement" in an u-boot you just can do that. Inheriting from "Tetrapod" will probably not mak…

Responses to Comments from bor