Re: multiple inheritance and instance data?

bugbear (bugbear@xxxxxxxxxxxxxxxxxxxxxxxxx) wrote on MMMMCMLIX September
MCMXCIII in <URL:news:460cc25b$0$8748$ed2619ec@xxxxxxxxxxxxxxxxxxxxxxxxxx>:
<> Abigail wrote:
<>
<> (a nice treatise on OO design).
<>
<> I read your stuff. I am *very* grateful,
<> and it looks complicated enough to be good (!)
<>
<> But, frankly, it's beyond my perl knowledge.
<>
<> In particular, \do, Scalar::Util 'refaddr', \my,
<> and the (I assume careful...) use of blocks
<> is all new to me.

\ is an operator, described in perlop. It returns a reference, references
are described in perlref. Scalar::Util is a module, with its own manual
page. my is described in perlsub, IIRC. Blocks are standard syntax, and
I think described in perlsyn.

<> Rather than ask you a load of questions about
<> your design, do you have a reference or tutorial
<> you could point me too?

Not really. Google for inside-out objects. Or buy Damian Conway's
Perl Best Practises.

<> I'm assuming you're writing up "conventional" practice
<> for me (for which, again, I'm grateful).
<>
<> BTW, in answer to your other question,
<> "Or are you going to break encapsulation, and peek inside package B
<> while developping package A? But if you're going to break encapsulation,
<> why bother with OO?"
<>
<> IMHO inheritence/overriding are powerful enough tools
<> (without encapsulation) to merit
<> their use, but if I can "have it all", that's wonderful.


With inside-out objects, you can have it all.


Abigail
--
A perl rose: perl -e '@}-`-,-`-%-'
.

Relevant Pages

  • Re: multiple inheritance and instance data?
    ... (a nice treatise on OO design). ... for me (for which, again, I'm grateful). ... "Or are you going to break encapsulation, ... while developping package A? ...
    (comp.lang.perl.misc)
  • Sonar Design
    ... This is about the allocation of program resources, and distributed design ... This section is from chapter 2 of the reference book in Advanced ... PowerBuilder 4 Techniques, pp. 6 which describes high-level concepts used to ... when designing an architecture for a application. ...
    (comp.lang.misc)
  • Re: Class Hierarchy design problems...
    ... incorrect design, although I am not entirely sure it is as clean cut as ... exist on that type (which causes the problem of being able to reference the ... ItemEditor via the Items indexer. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: create design time library using vs.net
    ... design version and others are used for the run time version. ... > - copy the runtime library project file to a new design time project file ... You must add a reference to assembly 'System.Windows.Forms'. ... > The dependency 'Accessibility' could not be found. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Call by reference in Java?
    ... > call by reference. ... > public void checkParameter(String strPreisProLiter, ... indicator that there is a flaw in your design. ... abstraction to fit the problem at hand. ...
    (comp.lang.java.help)