Hi Dave,
Congrats on getting Lucy approved!
WRT the proposed Ferret api changes, is there a good reason you chose
:yes/:no as opposed to true/false for some of the boolean settings?
Kind Regards
Neville B.
Hi Dave,
Congrats on getting Lucy approved!
WRT the proposed Ferret api changes, is there a good reason you chose
:yes/:no as opposed to true/false for some of the boolean settings?
Kind Regards
Neville B.
On 6/5/06, Neville B. [email protected] wrote:
Hi Dave,
Congrats on getting Lucy approved!
WRT the proposed Ferret api changes, is there a good reason you chose
:yes/:no as opposed to true/false for some of the boolean settings?
Hi Neville,
I don’t know if it’s a “good” reason. That’s up to you to decide. The
reason is that yes and no aren’t the only options. For example, :store
could be :yes, :no, :compressed and :term_vector could be :yes, :no,
:with_positions, :with_offsets and :with_positions_and_offsets. It
would seem strange to me to have the choices true, false and
:compress. I hope that makes sense.
Cheers,
Dave
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs