In case anyone is interested a working module is now available at
https://github.com/kenneth-olwing/grep-query.git, also see an entry for
it on PrePAN.
ken1
On 2016-07-26 10:39, kenn...@olwing.se wrote:
Hi David,
Many thanks for taking the time!
...
So, first of all, please do not take
Hi David,
Many thanks for taking the time!
...
So, first of all, please do not take Scrooge. I am rather fond of that
name, and plan to publish my module with that name some day.
Noted :-) !
As to your idea, it looks like you're working with something like
grep. The key difference is that
Hello Kenneth,
My background: I have been working on a generic greedy pattern matching
engine for my years. It is called Scrooge. The original itch was to be able
to write "regexes" for numerical data (i.e. PDL). It took a long time
before that idea grew into an implementation (starting around
Hello all,
I'd like to request some advice/thoughs/help on selecting a name for a
module.
The working name is 'Regexp::Query', but as it happens the realization
of the
original idea has moved slightly ahead of that so I'm no longer
confident on the
suitability...
The Scratched Itch:
I have
Currently I've been running with this named as String::Clean but I
think that it could be more descriptive. The end goal is to have a
collection of things that you would need to be replaced or striped
from a string. This all started because each of the developers at work
had seperate lists of
On 07/05/27 21:27 +0200, A. Pagaltzis wrote:
well, i don't like the way to prereq sthg in pococm that i
won't really use - that is, the whole non-poe logic of
audio::mpd.
What whole non-POE logic? All the logic I can find is the
as_string method. Are we talking about the same modules?
i
Le lundi 28 mai 2007 à 08:47, Jerome Quelin écrivait:
thus, the dist audio::mpd::items would not be enough - unless i also
release separately audio::mpd::stats and... which is a bit silly imo.
therefore:
- audio::mpdhelper?
- audio::mpdcommon?
Maybe Audio::MPD::Common, so that
Le lundi 28 mai 2007 à 13:11, Jerome Quelin écrivait:
On 07/05/28 12:31 +0200, Philippe 'Book' Bruhat wrote:
thus, the dist audio::mpd::items would not be enough - unless i also
release separately audio::mpd::stats and... which is a bit silly imo.
therefore:
- audio::mpdhelper?
hi there,
i'm working on a module to interface with music player daemon (mpd).
i've released:
- audio::mpd, a traditional oo interface
- poe::component::client::mpd, a poe-aware interface
they're both under development.
for each of them, i've defined an item class to map the items
manipulated
* Jerome Quelin [EMAIL PROTECTED] [2007-05-27 09:50]:
so here's my question: how should i name this new module?
- audio::item= isn't it too vague?
- audio::mpditem = isn't it too specific? (would it be used by others?)
- other?
The modules I see are just structs, and the only code in
On 07/05/27 17:31 +0200, A. Pagaltzis wrote:
* Jerome Quelin [EMAIL PROTECTED] [2007-05-27 09:50]:
so here's my question: how should i name this new module?
- audio::item= isn't it too vague?
- audio::mpditem = isn't it too specific? (would it be used by others?)
- other?
The
* Jerome Quelin [EMAIL PROTECTED] [2007-05-27 18:05]:
On 07/05/27 17:31 +0200, A. Pagaltzis wrote:
I’d suggest Audio::MPD::Item as the distro name, since you’ve
already organised them as a hierarchy in there. As a bonus
you won’t even need to change any of the Audio::MPD code,
just add
12 matches
Mail list logo
