You could be right on the fluent interface, my attempts in my own apps have resulted in APIs that are nice to use but a pain to write (lots of adapter/decorator code and the rest). Guess if there are more examples then the whole closure approach would be clearer, I was just expecting Fluent NHibernate to be a bit more fluent is all :P
Yeah I could (and probably should) map it as a user type at some point but didn't want to get into that at this stage if I can avoid it because it'll be easy to change later. Thanks again. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en -~----------~----~----~----~------~----~------~--~---
