Hi Alberto,
Terrence Brannon [EMAIL PROTECTED] wrote in message news RULES foo
aa==bb
cd==ef
ENDRULES
I don't get it. Are you just creating syntactics sugar for:
my %rules =
( aa = 'bb',
cd = 'ef'
);
Terrence Brannon wrote:
your original post said something about
Hi, I haven't tested your code (will do this week-end) and I think it's a
good idea.
I already do what your module proposes to help with but I haven't had the
idea to make a module out of it.
my format looks like this:
my @flags_and_help =
(
'h|help' =
I agree with you. A build system is no more than a dependency system with
some fluff around.
The fluff, in this case, is 10% of the code.
Say I put those 10% under PBS as it is an application. I still have a
problem finding out where to put the 90% left because some smart guy decided
that Devel
Hi,
Suresh Govindachar [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Hello,
I defined the concept of an Editable User Interface (EUI)
on www.sonic.net/~suresh/eui and illustrated it with
an extensive application
on www.vim.org/scripts/script.php?script_id=1052 .
Any other app
Hi,
What about DB_File::Clean instead? Either you have a function to which you
can give diffrent types of cleaning operations or you may have multiple
modules to do the different operations. As an example (certainly incorrect
as I don't have the slightess clue of what you can clean in a DB file),
I'm going to polute witha new top level namespace! PBS::
Don't anyone have any idea of where we should put this type of modules?
Devel::
Devel::Build::
Build::
App::BuildSystem
I'd appreciate some input.
Cheers, Nadim.
Hi,
It seems to me that few documents describe what to put in a documentation or
in which form. I haven't found any inteligent or complete description on
CPAN. There are a few heros that wrote some tips but looking at the new
modules coming into CPAN. I'd say we are lacking one standard document.
Andrew savige [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
khemir nadim wrote:
I'd love to review the second module that is offered for sacrifice ;-)
Anything to offer?
How about Apache::MVC? It was posted for review on Simon's code review
ladder mailing list in February
Andrew savige [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
So far this node has been ignored and downvoted.
I saw that, well that's life.
I suggest you start by creating a perl monks account (rather than
posting anonymously). Then hang around for a while to get a feel
for how
Randy W. Sims [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
wrote:
Hmm, we have:
1) Simon's code review ladder:
http://lists.netthink.co.uk/listinfo/code-review-ladder
Seems rather dead to me. A very interresting link anyhow. Let's see if we
can get more life there
2) Ask's
for the module, etc.. Some
thought that there was
too much dependency on SourceForge.
I hope this wraps it up. I still don't know where/how/when to help to get
some changes in place.
Cheers, Nadim.
Khemir Nadim [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Hi all,
I can live
A. Pagaltzis [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
* khemir nadim [EMAIL PROTECTED] [2004-06-16 13:53]:
I once wrote that it would be great to have the equivalent of
sourceforge for perl module, the answer I got was use
sourceforge. Hmm talk about not answering
Hi David,
It's just 10 days ago. The author might be on holidays or is too buisy to
answer you right now.
In the worst case, release you module under a different name for the time
being. What about:
Benchmark::Timer::Sampling.
Cheers, Nadim.
David Coppit [EMAIL PROTECTED] wrote in message
My two modest cents,
It seems to me that we'll never find __THE__ perfect name. The proposed
names all have something right. Isn't the problem somewhere else? Why can't
we name the same module differently? or (this might exist already) where do
we put description strings for the module (like at
This is exactly wht I wanted to say in my previous post but my post was not
phrased as good.
I also think the abstract/real hierarchy is a good idea.
My last point would be about the library that is used. Is it JavaCscript or
something more specific?
Cheers, Nadim.
[EMAIL PROTECTED] wrote in
Fergal Daly [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Hi all,
One of my modules has a failure noted against it that was caused by the
tester's wonky Perl installation. How can this be removed?
I don't have this problem but my modules sometimes fail on windows platform
when
Eric Wilhelm [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
FORBID any module without a meaningful readme with all its (possibly
recursive) dependencies, its pod and any other relevant information
inside.
I don't think it is in the spirit of CPAN to FORBID anything.
OK. but a
the documentation in one line.
-Original Message-
From: khemir nadim [mailto:[EMAIL PROTECTED]
I think it would be appropriate to further catalogue the
module name under Java or the name od the specific library
you interface with.
Amen.
Today that work is left to the module writer, setup a web site, setup a
mailling list etc ...
I once wrote that it would be great to have the equivalent of sourceforge
for perl module, the answer I got was use sourceforge. Hmm talk about not
answering the question. The most disturbing
Michael Peppler [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Personally I think the current rating system should be enough - only not
enough people use it (for example my modules have only one or two
ratings, yet they are used by a lot of people, and have been for many
years).
I
Lincoln A. Baxter [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
On Tue, 2004-05-11 at 14:29, Michael A Nachbaur wrote:
I'm working on a web application that is almost 100% perl (the styling
is
handled in XSL). The entire application's test and installation
procedure is
managed
Hi,
[EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
One possibility would be to force each known language to become a module
(Lingua:Identification::EN for English, etc)... the downside of this
solution is that once I have 50 languages, I'll have 51 modules... :-|
1 or 100, it doesn't
Hi, within the development cathegory, I think it would be good to separate
modules that are for the perl interpreter (debugging, profiling, ...) and
other development tools. As an example, I have a module called Devel::Cpp
which I put tin the Devel root because I foun no better place (and I didn't
Hi,
David [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
There's not really much a module author can to do help a user like that.
yes there is, it's the custom VERSION subroutine. Your legacy program
dies with the error message
until it is edited, after the module upgrade.
Michel Rodriguez [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Generating the doc (from the POD) for each module (with a link to the
tarfile or to the CPAN search page for the lates release of the module),
and putting it on CPAN in something like cpan.org/docs/module name.
Does
Vagn Johansen [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
How do you avoid breaking old programs when the interface changes?
You don't. IMHO it's the users responsibility to check for what version they
are using not the module author. With Module Build you can ask for a
specific
Sam Vilain [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
- encourage curators to step forward, or groups of curators, for
each category; possibly even create mailing lists for people with
a general interest in the technology in that category; to field
questions about
in message
news:[EMAIL PROTECTED]
[EMAIL PROTECTED] (Khemir Nadim) writes:
Everything that was said in this thread was very interresting and I,
too,
belive things should get better and I encourage those that want to do
things
_now_.
None of these ideas are new.
- Any one can start whatever
Andy Lester [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Because:
a) I wasn't happy with the API
b) I'm a lazy SOB and couldn't find the time to sort it out
I'll be glad to help with the second part. Mail me the parts and I'll
bundle it up all nice for ya.
Hi, I also have
Hi Fergal and other,
The difference is that Module::Build forces the Foo::Bar's author to work
out what current versions of Some::Module and Other::Module are suitable
and
to try to predict what future version will still be compatible. This is
time
consuming and error prone (predicting the
grepmail : grep program for mailboxes. Currently only supports mbox
format.
Not sure about the last one. Do/can we register namespaces for scripts?
what about grepmbox instead? you can always go to grepmail when you
support other formats (like mail spool for instance)
Cheers,Nadim.
Version 0.04 is out. Check out the documentation at:
http://search.cpan.org/src/NKH/Spreadsheet-Perl-0.04/README
http://search.cpan.org/~nkh/Spreadsheet-Perl-0.04/Perl.pm
I still need your input and I still need some help if any brave soul is
available.
Nadim.
David Manura [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
khemir nadim wrote:
I agree that a way of describing a range without naming one of the
limits
should exist, I just don't know how to make it visually clear. What
about
'B1:B*' 'B*:B10' 'B*:B*' ?
'*' might
Hi David, Thank you for your answer.
-Original Message-
From: David Manura
Nadim,
This module looks neat. The way speadsheets automatically
update data on dependencies, like a continually running makefile,
seem to be their main benefit, but they do have some limitations
Hi All, this seems to be the group I have been looking for (and missed for
few years).
The module I am working on lately is a Spreadsheet (Spreadsheet::Perl),
There is also a Data::TreeDumper that can be of interrest wich is very good
at filtering data, it looks good and is easier to follow
35 matches
Mail list logo