Re: ALSA C++ API updated for 1.0.16

From: Michael Gerdau <mgerdau@tiscali.de>
To: alsa-devel@alsa-project.org
Cc: "Clemens Ladisch" <clemens@ladisch.de>,
	"Lasse Kärkkäinen" <tronic@trn.iki.fi>
Subject: Re: ALSA C++ API updated for 1.0.16
Date: Tue, 26 Feb 2008 15:49:50 +0100	[thread overview]
Message-ID: <200802261550.03657.mgerdau@tiscali.de> (raw)
In-Reply-To: <47C3E387.20800@ladisch.de>

[-- Attachment #1.1: Type: text/plain, Size: 810 bytes --]

> > ALSA_HPP_CLASS& set_##name(...) { ...; return *this; }\
> 
> Is there a reason why you return the object itself?  Usually, returning
> an object implies that that object is a _different_ object with the
> setting applied, which would mean that the original object was _not_
> changed, but that isn't true here.

I'm not an OO design guru, but at least IOC (IBM OpenClass; it used to
be a rather powerful multiplatform GUI framework - before they made it
AIX only) used this very paradigma all over the place.

You were supposed to write statements like:
  obj.method1().method2().method3().___.method_n();

At least that's what all their example code looked like.

Best,
Michael
-- 
 Michael Gerdau       email: mgerdau@tiscali.de
 GPG-keys available on request or at public keyserver

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel