When MD5 changed to Digest::MD5, Gisle's strategy was to reissue MD5
as a shell around Digest::MD5.
Lincoln
Tim Bunce writes:
> On Wed, Feb 23, 2000 at 06:38:25AM -0500, Chris Nandor wrote:
> > At 10.59 + 2000.02.23, Tim Bunce wrote:
> > >Issue a new version that just the name change, no
On Wed, Feb 23, 2000 at 06:38:25AM -0500, Chris Nandor wrote:
> At 10.59 + 2000.02.23, Tim Bunce wrote:
> >Issue a new version that just the name change, no API changes, so
> >people can migrate with a simple edit.
>
> I have a bunch of changes due to the module, and was going to make a new
>
At 10.59 + 2000.02.23, Tim Bunce wrote:
>Issue a new version that just the name change, no API changes, so
>people can migrate with a simple edit.
I have a bunch of changes due to the module, and was going to make a new
release soon (in the next few weeks). What do you think about
simlultane
On Tue, Feb 22, 2000 at 08:07:37PM -0500, Chris Nandor wrote:
> At 19.48 -0500 2000.02.22, Jon Orwant wrote:
> >Chris writes:
> >> I am not sure if MP3:: is a great base name. What about AIFF::, MOV::,
> >> WAV::, etc.?
> >>
> >> Maybe Audio::MP3::Info ... ? I am not keen on changing the name, b
At 19.48 -0500 2000.02.22, Jon Orwant wrote:
>Chris writes:
>> I am not sure if MP3:: is a great base name. What about AIFF::, MOV::,
>> WAV::, etc.?
>>
>> Maybe Audio::MP3::Info ... ? I am not keen on changing the name, but I
>> wouldn't mind if it were a good name. :) I dunno. Orwant, are a
Chris writes:
> I am not sure if MP3:: is a great base name. What about AIFF::, MOV::,
> WAV::, etc.?
>
> Maybe Audio::MP3::Info ... ? I am not keen on changing the name, but I
> wouldn't mind if it were a good name. :) I dunno. Orwant, are any of us
> treading down the path to hell here?
On Tue, Feb 22, 2000 at 03:46:42PM -0500, Lincoln Stein wrote:
> I'd prefer MPEG:: to Audio::MP3:: because of the name length issues.
> I'm sure we're all going down the road to hell... %-)
We are. But I'd be happy on the road with the AudioMP3:: signpost.
The AudioWAV:: etc names would also be f
I'd prefer MPEG:: to Audio::MP3:: because of the name length issues.
I'm sure we're all going down the road to hell... %-)
Lincoln
Chris Nandor writes:
> At 20.32 + 2000.02.22, Tim Bunce wrote:
> >On Tue, Feb 22, 2000 at 03:24:40PM -0500, Lincoln Stein wrote:
> >> I'd prefer MP3:: myself
At 20.32 + 2000.02.22, Tim Bunce wrote:
>On Tue, Feb 22, 2000 at 03:24:40PM -0500, Lincoln Stein wrote:
>> I'd prefer MP3:: myself because MPEG makes people think first of
>> video.
>
>Go for MP3::* then and let others follow... :-)
>
>Tim.
>
>> Any chance Chris has thought about changing his
On Tue, Feb 22, 2000 at 03:24:40PM -0500, Lincoln Stein wrote:
> I'd prefer MP3:: myself because MPEG makes people think first of
> video.
Go for MP3::* then and let others follow... :-)
Tim.
> Any chance Chris has thought about changing his module's name
> to MP3::Info?
>
> Lincoln
>
> Tim B
I'd prefer MP3:: myself because MPEG makes people think first of
video. Any chance Chris has thought about changing his module's name
to MP3::Info?
Lincoln
Tim Bunce writes:
> On Tue, Feb 22, 2000 at 12:55:52PM -0500, Lincoln Stein wrote:
> > Hi,
> >
> > I'm nearly ready to release a pure-
Hi,
I'm nearly ready to release a pure-perl interface to the Napster MP3
search and download engine. Currently, I'm calling it MPEG::Napster,
which would put it in the sparsely-populated MPEG namespace. I think
this makes sense because Napster is an MP3-specific protocol, and my
module hass ano
12 matches
Mail list logo
