James' point was not that he knows all, but that fixing fields is a low
priority at the moment. The code base is in a somewhat awkward state while
the SM is put into place the FI is fleshed out. Adding new features is also
a low priority at the moment, so you can imagine that fixing something that
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
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 wrot
