Is there any compelling reason not to compile PL/Ruby with the
–enable-conversion option?
Is it hellaciously slow? Does it make kittens explode?
It seems like such an obviously-useful feature that I can’t imagine why
anyone wouldn’t use it…and yet it’s an option. Not enabled by
default. Which makes me fret, and worry.
Can I use this option in a production environment? Will my cats be safe?
–
(-, /\ / / //
Gavin Kistner wrote:
Is there any compelling reason not to compile PL/Ruby with the
–enable-conversion option?Is it hellaciously slow? Does it make kittens explode?
I think because it’s experimental. 0.39 is the first version to have
that feature. Future versions might enable it by default.
It seems like such an obviously-useful feature that I can’t imagine why
anyone wouldn’t use it…and yet it’s an option. Not enabled by
default. Which makes me fret, and worry.
–
dave
Is there any compelling reason *not* to compile PL/Ruby with the
--enable-conversion option?
it's experimental and for me it's a toy because it make only a few
conversions. Look at
PostgreSQL: Documentation: 7.4: Data Types
to find all postgres types. This is why I've added
--enable-network and --enable-geometry
to have something more complete
Is it hellaciously slow? Does it make kittens explode?
well, it must be faster with --enable-conversion because with the old
version it make the transformation
Datum ==> String ( ==> Float : optional with a call to Float(string))
Float ==> String ==> Datum
with --enable-conversion it make
Datum ==> Float
Float ==> Datum
Now for --enable-network and --enable-geometry it's perhaps best to wait
for 0.4.1 (0.4.0 is out) because I'll add an option --enable-autoload to
give him the possibility to autoload classes like NetAddr, Point, Circle,
etc even with $SAFE >= 4
Guy Decoux