Comments on: static reflection – INotifyPropertyChanged

By: Dmitri

Dmitri — Sun, 03 Jan 2010 15:51:54 +0000

Err, what about the situation where you cannot really subclass from NotifyPropertyChanged because you’re already inheriting from something else? This whole approach hinges on inheritance which prevents it being used anywhere. At this point, I’d typically suggest a mixin, except that mixins cannot contain state (without a lot of pain), and you have an event whose value must be accessible.

I think, for the time being, it makes sense to just use PostSharp for the INotifyPropertyChanged problem.

By: Igor Yalovoi

Igor Yalovoi — Thu, 01 Oct 2009 15:34:55 +0000

Great work. Helped me very much.

By: Static Reflection: Say What? - Brownie Points

Static Reflection: Say What? - Brownie Points — Mon, 23 Feb 2009 18:19:41 +0000

[...] do things that appear to be dynamic but in reality are checked at compile time. Like for instance, getting the name of a property for firing an INotifyPropertyChanged.PropertyChanged event. My colleague, Jon Fuller, showed me his code for Method Guards and my first comment was that this [...]

By: Alexey Romanov

Alexey Romanov — Sat, 27 Dec 2008 08:17:06 +0000

Sorry for the double comment

By: Alexey Romanov

Alexey Romanov — Fri, 26 Dec 2008 14:04:46 +0000

It seems like you really want a decent macro system. In .Net that means, at the moment, either Nemerle or Boo.

I don’t remember Boo syntax, but in Nemerle you can just write

[Accessor(flags = WantSetter)]
mutable _someField : int;

and it will be converted at compile time to

mutable _someField : int;
public SomeField : int {
get { some_field }
set { some_field = value }
}

Writing a macro which would insert FirePropertyChange calls as well is pretty easy.

By: Alexey Romanov

Alexey Romanov — Fri, 26 Dec 2008 13:05:09 +0000

It seems like you want a decent (i.e. not C preprocessor) macro system. On .Net the best language for this is probably Nemerle or Boo. You can just write (in Nemerle, I don’t remember Boo syntax)

[NotifiableProperty]
public string _firstName;

and it will be converted to

public string FirstName
{
get { return _firstName; }
set
{
if (_firstName != value)
{
_firstName = value;
FirePropertyChanged(”FirstName”);
}
}
}

at compile time, no run time overhead! See here: http://nemerle.org/Macros

By: private override » Blog Archive » static reflection - Method Guards

private override » Blog Archive » static reflection - Method Guards — Thu, 11 Dec 2008 15:48:08 +0000

[...] private override « static reflection – INotifyPropertyChanged [...]

By: .Net Ramblings » Blog Archive » Cleaning up INotifyPropertyChanged

.Net Ramblings » Blog Archive » Cleaning up INotifyPropertyChanged — Wed, 10 Dec 2008 20:06:05 +0000

[...] (_name != value) conditions that have to be in every setter. Therefore, I was really excited to see this post from my friend Jonathan Fuller and his much cleaner way of implementing [...]

By: Paul

Paul — Wed, 10 Dec 2008 19:43:29 +0000

I was always annoyed by implementing INotifyPropertyChanged. I’ll definitely being using this in the future

By: Matt

Matt — Mon, 08 Dec 2008 19:14:55 +0000

I like it!