Why not use fields? Nhibernate supports them and you can't say you know all use-cases. In this case it's for graphics which according to spec needs to be quick and fields allow me to optimize access to these which will be called many hundreds of times per second.
On May 23, 6:18 pm, James Gregory <jagregory....@gmail.com> wrote: > It's a known issue, one that probably won't be fixed for a while either; > it's an architectural issue that is fairly low priority compared to > everything else. > I'd personally recommend not using fields anyway, regardless of whether FNH > supports them or not. > > On Sat, May 23, 2009 at 6:06 PM, H F <echo...@gmail.com> wrote: > > Hi, > > > Failing test. > > > Cheers --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to fluent-nhibernate@googlegroups.com To unsubscribe from this group, send email to fluent-nhibernate+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en -~----------~----~----~----~------~----~------~--~---
