Hi,
>
>It makes the contract much more loose and the method >names turn into a mess. Right
>now, if I see a method >named "configure" then I know where it fits in.
>
I agree and suggest the following.
We can implement both variants.
Let people decide what way they should go.
Personally I got accustomed to the interface model
cause I came to .NET from Java but others ...
I believe delegate and attribute model is very important as well and we shouldn't
forget it.
There are pros and cons of every of them.
and I think we might have a long discussion.
In regards to attribute model:
I don't like untyped manipulations with names like that:
AvalonLifecycle("configurable")
The mistake will appear at run-time only.
That's very bad.
I think Berin's example to me was perfect:[AvalonInitialize]
public void setUp()
{}
[AvalonStart]
public void comenzar()
{}
Of course, we don't still avoid the problem of run-time exceptions due to using
delegates but this variant seems to be more correct.
---
Best Regards,
Yauheny Mikulski (Jeff)
"Religion is what the common people see as true,
the wise people see as false, and
the rulers see as useful" - Seneca
---------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
