Re: Test::DoubleQuotedEntities
On Tue, Aug 24, 2004 at 01:51:12PM -0400, David H. Adler wrote: (oh, and as an aside I released a new Acme::Test::Buffy, with slightly improved documentation and spelling too - but no one cares about that) Says who? *I* care. And you have no idea how stupid I felt submitting an RT on that module, either. K. -- Kirrily 'Skud' Robert - [EMAIL PROTECTED] - http://infotrope.net/ There's too much blood in my caffeine system.
Re: Updates to modules-related pod
On Tue, Aug 17, 2004 at 07:16:52PM +0200, Tels wrote: +it connected to the rest of the CPAN, you'll need to go to Register +Namespace on PAUSE. Once registered, your module will appear in the +by-module and by-category listings on CPAN. Only a very few of my modules are registered in that namespace. For instance, Math::BigInt::Pari is, while Math::BigInt::GMP is not. The reason is simple: It never worked. I think I sent at least GMP at least two times to the register namespace black hole, and it never happened. AFAIR there was only one guy (Hi Andreas :) working on the registrations, and only every two weeks on Sunday or something like that. There are multiple people who have the ability to administer CPAN in that fashion - I'm one of them, for what it's worth, though I'll admit I haven't touched it in years while I've been on hiatus. I forget who else. So, two (honest) questions: * does it work better now, e.g. should I resub mit my module(s)? * What exactly is the registration good for? I mean, all my dozend or so modules work, and are connected to the rest of CPAN or whatever this means. Having your module registered means it will show up in the category listing as seen on the front page of search.cpan.org and in the by-module and by-category listings (which, yeah, nobody uses anymore AFAIK). However, the by recentness list at http://cpan.org/modules/01modules.mtime.html indicates that something at least is being updated very frequently, at least daily, and I suspect automatically. So the question is, which bits are updated automatically by the mere fact of a module author doing the register namespace thing, and which bits require manual intervention? So, if the register namespace isn't too usefull and/or doesn't work fine, why burden new authors with it? I raised this on [EMAIL PROTECTED] the other day in fact. Register namespace is useful in some ways and not in others, it seems. The most useless part of it is the published modules list, and IMO we should get rid of the thing. K. -- Kirrily 'Skud' Robert - [EMAIL PROTECTED] - http://infotrope.net/ I've decided to rename [Connect's Melbourne border router] 'Madi's Pants' because it keeps dropping. -- Madi (from the Netizen quotes file)
Updates to modules-related pod
In looking through perlnewmod, perlmodlib, perlmodstyle, and other related POD today, I found that most of them are out of date and not in keeping with recent trends in module writing, testing/QA, etc. So, with a due sense of foreboding, I have dived in once again. Errr, hi, long time no p5p. Here's an initial patch to perlnewmod, the main points of which are: * recommend module-starter over h2xs * modernise recommended h2xs invocation * modernise list of recommended modules to learn from * refer to Test::Simple and Test::More instead of Test * modernise PAUSE-related instructions I know module-starter (part of the Module::Starter package) isn't part of the core, but I figure that there are two answers to that: 1) propose M::S for inclusion in the core, or 2) since this doc is aimed at CPAN authors anyway, let's assume that it won't kill them to get the module from there. Thinking of attacking perlmodlib next, and removing a lot of those long lists. I'm pretty sure we're better off pointing to web resources for most of the gunk that's in there. K. -- Kirrily 'Skud' Robert - [EMAIL PROTECTED] - http://infotrope.net/ Fist it. It's my solution to everything. -- Penny (from the Netizen quotes file) diff -ruN bleadperl/.patch myperl/.patch --- bleadperl/.patch2004-08-16 14:19:59.0 -0400 +++ myperl/.patch 1969-12-31 19:00:00.0 -0500 @@ -1 +0,0 @@ -23219 diff -ruN bleadperl/pod/perlnewmod.pod myperl/pod/perlnewmod.pod --- bleadperl/pod/perlnewmod.pod2003-08-27 10:27:41.0 -0400 +++ myperl/pod/perlnewmod.pod 2004-08-16 15:59:16.0 -0400 @@ -73,9 +73,10 @@ Dig into a bunch of modules to see how they're written. I'd suggest starting with LText::Tabs|Text::Tabs, since it's in the standard -library and is nice and simple, and then looking at something like -LTime::Zone|Time::Zone, LFile::Copy|File::Copy and then some of the -CMail::* modules if you're planning on writing object oriented code. +library and is nice and simple, and then looking at something a little +more complex like LFile::Copy|File::Copy. For object oriented +code, CWWW::Mechanize or the CEmail::* modules provide some good +examples. These should give you an overall feel for how modules are laid out and written. @@ -84,8 +85,8 @@ There are a lot of modules on CPAN, and it's easy to miss one that's similar to what you're planning on contributing. Have a good plough -through the modules list and the Fby-module directories, and make sure -you're not the one reinventing the wheel! +through the Lhttp://search.cpan.org and make sure you're not the one +reinventing the wheel! =item Discuss the need @@ -119,18 +120,29 @@ =over 3 -=item Start with Fh2xs +=item Start with Fmodule-starter or Fh2xs -Originally a utility to convert C header files into XS modules, -Lh2xs|h2xs has become a useful utility for churning out skeletons for -Perl-only modules as well. If you don't want to use the -LAutoloader|Autoloader which splits up big modules into smaller -subroutine-sized chunks, you'll say something like this: +The Fmodule-starter utility is distributed as part of the +LModule::Starter|Module::Starter CPAN package. It creates a directory +with stubs of all the necessary files to start a new module, according +to recent best practice for module development, and is invoked from +the command line, thus: -h2xs -AX -n Net::Acme +module-starter --module=Foo::Bar \ + --author=Your Name [EMAIL PROTECTED] -The C-A omits the Autoloader code, C-X omits XS elements, and C-n -specifies the name of the module. +If you do not wish to install the LModule::Starter|Module::Starter +package from CPAN, Fh2xs is an older tool, originally intended for the +development of XS modules, which comes packaged with the Perl +distribution. + +A typical invocation of Lh2xs|h2xs for a pure Perl module is: + +h2xs -AX --skip-exporter --use-new-tests -n Foo::Bar + +The C-A omits the Autoloader code, C-X omits XS elements, +C--skip-exporter omits the Exporter code, C--use-new-tests sets up a +modern testing environment, and C-n specifies the name of the module. =item Use Lstrict|strict and Lwarnings|warnings @@ -164,10 +176,9 @@ =item Use LExporter|Exporter - wisely! -Ch2xs provides stubs for LExporter|Exporter, which gives you a -standard way of exporting symbols and subroutines from your module into -the caller's namespace. For instance, saying Cuse Net::Acme qw(frob) -would import the Cfrob subroutine. +LExporter|Exporter gives you a standard way of exporting symbols and +subroutines from your module into the caller's namespace. For instance, +saying Cuse Net::Acme qw(frob) would import the Cfrob subroutine. The package variable C@EXPORT will determine which symbols will get exported when the caller simply says Cuse Net::Acme - you will hardly @@ -180,21 +191,23 @@ The work isn't over until the paperwork is done, and you're going to need to put in some time
perl6-modules list?
Hi Ask, perl6-meta, and perl6-stdlib, Today at YAPC in the Perl 6 session there was some discussion of modules and what work needs doing in that area for Perl 6. Basically it breaks down the following two topics: WHAT goes into the core? (covered by perl6-stdlib) HOW do we write Perl 6 modules? My notes can be found at http://infotrope.net/opensource/software/perl6/modules/ where I discuss the work that needs to be done on the how side, particularly the issue of a style guide documenting best practice for Perl modules and how we can hopefully apply this best practice as we rewrite modules for Perl 6. I would like to set up a perl6-modules to discuss this topic, which I believe is separate from the question of what goes into the standard library. Discussion should probably be on -stdlib until -modules is set up. Thanks in advance, K.
Re: Art Of Unix Programming on Perl
On Sun, Feb 11, 2001 at 07:13:30PM -0500, Adam Turoff wrote: On Sun, Feb 11, 2001 at 05:03:12PM +, Simon Cozens wrote: There's obvious FUD out there and we don't seem to be giving the impression of getting much done, or doing anything to counter it. Let's be fair. We're not getting much done, and that's a *GOOD* thing. Language design is a very tough nut to crack, and we decided (as a group) that we don't want a language designed by committee, we want a languaged designed by Larry. The best we can do (frustrating as it may be) is to let him think deeply. Wasn't he meant to be keeping us up to date with snippets of what he's doing/thinking about? I recall Nat posting a couple of months ago that he'd talked to Larry and Larry had said he'd do this. K.
perl6-language needs admin help too :)
As many of you may know, I've recently moved to the other side of the world, and my life's a bit hectic. I hadn't counted on p6-l bursting into life just now, and while I'd like to keep right up to date with it I really can't guarantee daily reading. Would anyone like to volunteer to do weekly summaries and/or general list admin? K.
Re: We should have some YAPC talks on Perl 6
I've got one ready to go on the topic of "Perl 6: the story so far". I'm presenting it next week at linux.conf.au and would be happy to submit it for YAPC and/or TPC. K.
intercal
mstevens other languages are great. they are a source of features to steal^Wborrow. Skud INTERCAL mstevens except maybe intercal
Re: Perl Apprenticeship Program
On Tue, Dec 05, 2000 at 11:05:43AM -0800, Steve Fink wrote: David Grove wrote: Also, as far as documentation goes, I think it _should_ be written by apprentices, so that non-masters can understand it too. That's always been a huge criticism of the perldocs. That's not grunt work. That's proper allocation of duties to the best suited personnel for the benefit of the project. Except it's a particular duty that nobody really likes to perform. Which pushes it into the realm of grunt work. Bah. *I* like documenting. K.
Re: Tech documentation (Re: Perl Apprenticeship Program)
On Tue, Dec 05, 2000 at 11:28:31AM -0800, Nathan Wiger wrote: Anyways, that's just one suggestion. Do I have any idea where to find these mythical people? No, unfortunately. Perhaps some feelers on newsgroups might be a good place to start. Personal experience shows that this could be a win, though. Open Source Writers Group (http://oswg.org/) is a good starting point. I'm subscribed to their mailing list. I can think of a couple of other good places to try, too, but they're a bit politically incorrect to mention in this context :-/ K.
