I’ve done another minor update. It was originally going to be a
moderately-sized update, but some work that I did … didn’t pan out
in the tests.
After I finish some other work, I’m going to add module
Text::Formattable to the package and extend String and Array with
this module. In this way, you will be able to do:
"foo".format
"foo".format!
And get the expected results. There will be ways of setting the
formatter from the objects themselves, too.
This will tentatively become Text::Format 0.52.3. My question for
Rubyists at large is – should I keep the Perl versioning scheme for
this package? If not, then I think that this potential improvement is
worthy of a significant version increase (possibly even to 1.0). It
makes sense to keep MIME::Types at the same major/minor version as
the Perl package, but Text::Format hasn’t been updated since 1998 –
it just /works/.
-austin
– Austin Ziegler, austin@halostatue.ca on 2002.10.30 at 14.26.11
This will tentatively become Text::Format 0.52.3. My question for
Rubyists at large is – should I keep the Perl versioning scheme for
this package? If not, then I think that this potential improvement is
worthy of a significant version increase (possibly even to 1.0). It
makes sense to keep MIME::Types at the same major/minor version as
the Perl package, but Text::Format hasn’t been updated since 1998 –
it just /works/.
I don’t think that keeping major/minor version numbers synced with Perl
makes too much sense. I’d hope that the ruby community finds ways to
improve one (or at lease ruby-ize) things we bring in from other
languages), so there is likely to be some feature skew anyway.
-pate
···
On Thu, 31 Oct 2002, Austin Ziegler wrote:
-austin
– Austin Ziegler, austin@halostatue.ca on 2002.10.30 at 14.26.11
I’ve done another minor update. It was originally going to be a
moderately-sized update, but some work that I did … didn’t pan out
in the tests.
After I finish some other work, I’m going to add module
Text::Formattable to the package and extend String and Array with
this module. In this way, you will be able to do:
"foo".format
"foo".format!
And get the expected results. There will be ways of setting the
formatter from the objects themselves, too.
You’re the package author, and are doing a good job, so I’ll just make one
suggestion. I think extending String and Array should be optional, perhaps by
require “text/format”
require “text/format/ext”
What do you think?
Gavin
···
From: “Austin Ziegler” austin@halostatue.ca
That may be a better idea, although I’m not sure that I want to
create another directory for this, but I don’t really know how I
would do this otherwise. Perhaps a function:
Text::Format::extend(:String)
I have to consider how I’m going to do this anyway; I want to keep
it as efficient as possible, so I’m debating whether or not the
extension’s formatter should be an object or class variable (or
perhaps both).
-austin
– Austin Ziegler, austin@halostatue.ca on 2002.10.30 at 19.05.25
···
On Thu, 31 Oct 2002 08:34:49 +0900, Gavin Sinclair wrote:
You’re the package author, and are doing a good job, so I’ll just
make one suggestion. I think extending String and Array should be
optional, perhaps by
require “text/format”
require “text/format/ext”