No, this is my mistake. I should have deprecated and added new methods
that returned the Fieldable.
The cast is only going to be safe when using non lazy field loading,
which is the standard before this anyway.
Chris Hostetter wrote:
: Is this intentional?
: If not, uses of "Field" in unit tests should not have been changed to
Fieldable.
If it was intentional, then at a minimum it should be documented as an
API Change (and not just a new feature).
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Grant Ingersoll
Sr. Software Engineer
Center for Natural Language Processing
Syracuse University
School of Information Studies
335 Hinds Hall
Syracuse, NY 13244
http://www.cnlp.org
Voice: 315-443-5484
Fax: 315-443-6886
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
