µç×ÓÐÐÒµÃâ·Ñ¼ÓÈë
北京天利鑫源科技发展有限责任公司 本公司是一家主要从事集成电路、接插件、网络产品销售以及板卡OEM制作的专业公司，是MAX、AD、DALLAS、BB、TI、NS，CYPRESS等电子厂商在中国的特约经销商，我公司经营品牌齐全,可为您寻找军品级,工业品级，通讯用，较偏门、冷门之高科技元器件。欢迎同行业的朋友提供真实的库存，我们将免费为您发布供求信息，赶快注册！网址 http://tianlxy.5188.org
Re: Namespace Tie::Excel
If you really wanted to go that way then I'd suggest Spreadsheet::Tie::Excel, Spreadsheet::Tie::Gnumeric etc with a Spreadsheet::Tie module acting as an interface. But I suspect Excel is the only one that'll be implemented as most other spreadsheets can read Excel format. Tim. On Thu, Nov 06, 2003 at 09:53:35PM +0100, Simone Cesano wrote: > First of all thanks a lot for answering. Spreadsheet::* sounds good. > > On the other hand, I know it might be late to consider this, but what > happens if someone comes up with an interface to Gnumeric? > > Do we start again with Spreadsheet::TieGnumeric etc.? In this light > what's your opinion on Spreadsheet::Excel::Tie ? Or keep with the > tradition, and go for Spreadsheet::TieExcel? > > Cheers, > > Simone > > Tim Bunce wrote: > > >There's a Spreadsheet::* namespace with things like > >Spreadsheet::ParseExcel::Utility and Spreadsheet::WriteExcel. > > > >So perhaps Spreadsheet::TieExcel would be good. > > > >Tim. > > > >On Wed, Nov 05, 2003 at 08:02:05AM +0100, Simone Cesano wrote: > > > > > >>Hello, > >> > >>I am thinking about uploading a module to CPAN. > >> > >>It is an interface to Excel, so that by tieing filehandles, scalars or > >>arrays you can write transparently to Excel as if it were a Perl > >>variable. > >> > >>I thought about calling the module > >> > >> Tie::Excel > >> > >>providing packages > >> > >> Tie::Excel::Scalar > >> Tie::Excel::File > >> Tie::Excel::Array > >> > >>Anybody have any comments? In particular, is the name the best > >>possible? > >> > >>Regards and thanks, > >> > >>Simone > >> > >> > >> > > > > > > > >
Welcome new user MJP
Welcome Michael J. Pomraning, PAUSE, the Perl Authors Upload Server, has a userid for you: MJP Once you've gone through the procedure of password approval (see the separate mail you should receive about right now), this userid will be the one that you can use to upload your work or edit your credentials in the PAUSE database. This is what we have stored in the database now: Name: Michael J. Pomraning email: CENSORED homepage: http://pilcrow.madison.wi.us enteredby: Johan Vromans Please note that your email address is exposed in various listings and database dumps. You can register with both a public and a secret email if you want to protect yourself from SPAM. If you want to do this, please visit https://pause.perl.org/pause/authenquery?ACTION=edit_cred or http://pause.perl.org/pause/authenquery?ACTION=edit_cred If you need any further information, please visit $CPAN/modules/04pause.html. If this doesn't answer your questions, contact [EMAIL PROTECTED] Thank you for your prospective contributions, The Pause Team
PAUSE ID request (PRATH; Pratheepan Raveendranathan)
Request to register new user fullname: Pratheepan Raveendranathan userid: PRATH mail: CENSORED homepage: www.d.umn.edu/~rave0029/research why: I am working on some Natural Language Processing stuff, and a part of it is involving Google API. I am planning to submit some perl code relating to Google API and Perl. The code will be able to identify the semantic orientation of words. The following links are only valid for PAUSE maintainers: Registration form with editing capabilities: https://pause.perl.org/pause/authenquery?ACTION=add_user&USERID=f350_c29bfd12a4dca6eb&SUBMIT_pause99_add_user_sub=1 Immediate (one click) registration: https://pause.perl.org/pause/authenquery?ACTION=add_user&USERID=f350_c29bfd12a4dca6eb&SUBMIT_pause99_add_user_Definitely=1
Welcome new user PRATH
Welcome Pratheepan Raveendranathan, PAUSE, the Perl Authors Upload Server, has a userid for you: PRATH Once you've gone through the procedure of password approval (see the separate mail you should receive about right now), this userid will be the one that you can use to upload your work or edit your credentials in the PAUSE database. This is what we have stored in the database now: Name: Pratheepan Raveendranathan email: CENSORED homepage: www.d.umn.edu/~rave0029/research enteredby: Johan Vromans Please note that your email address is exposed in various listings and database dumps. You can register with both a public and a secret email if you want to protect yourself from SPAM. If you want to do this, please visit https://pause.perl.org/pause/authenquery?ACTION=edit_cred or http://pause.perl.org/pause/authenquery?ACTION=edit_cred If you need any further information, please visit $CPAN/modules/04pause.html. If this doesn't answer your questions, contact [EMAIL PROTECTED] Thank you for your prospective contributions, The Pause Team
PAUSE ID request (BNEGRAO; Bruno Negrao Guimaraes Zica)
Request to register new user fullname: Bruno Negrao Guimaraes Zica userid: BNEGRAO mail: CENSORED homepage: why: A module to interact with Daemontools executables. Daemontools is a package written in C by Dan Bernstein aiming to control Unix daemons such as smtpd, pop3d, etc. The following links are only valid for PAUSE maintainers: Registration form with editing capabilities: https://pause.perl.org/pause/authenquery?ACTION=add_user&USERID=1450_556dd37e0269fae8&SUBMIT_pause99_add_user_sub=1 Immediate (one click) registration: https://pause.perl.org/pause/authenquery?ACTION=add_user&USERID=1450_556dd37e0269fae8&SUBMIT_pause99_add_user_Definitely=1
Module submission POSIX::RT::Semaphore
The following module was proposed for inclusion in the Module List: modid: POSIX::RT::Semaphore DSLIP: bdhOa description: POSIX.1b realtime semaphores userid: MJP (Michael J. Pomraning) chapterid:4 (Operating_System_Interfaces) communities: similar: IPC::Semaphore Thread::Semaphore rationale: Realtime semaphores are an interesting ball of wax. POSIX::RT::MQ already suggests a reasonable namespace for the 1b Realtime extensions. enteredby: MJP (Michael J. Pomraning) enteredon: Fri Nov 7 16:26:32 2003 GMT The resulting entry would be: POSIX::RT:: ::Semaphore bdhOa POSIX.1b realtime semaphores MJP Thanks for registering, -- The PAUSE PS: The following links are only valid for module list maintainers: Registration form with editing capabilities: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=2450_ae8652e6982faa2f&SUBMIT_pause99_add_mod_preview=1 Immediate (one click) registration: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=2450_ae8652e6982faa2f&SUBMIT_pause99_add_mod_insertit=1
User update for YVES
Record update in the PAUSE users database: userid: [YVES] fullname: [Yves] asciiname: [] email: [CENSORED] homepage: [] cpan_mail_alias: [secr] Data were entered by YVES (Yves). Please check if they are correct. Thanks, The Pause
Module submission Data::Stream
The following module was proposed for inclusion in the Module List: modid: Data::Stream DSLIP: bdhhp description: Stream a data dump to a filehandle userid: YVES (Yves) chapterid:6 (Data_Type_Utilities) communities: www.perlmonks.org similar: Data::BFDump Data::Dumper Data::Dump rationale: Data::Stream is a total rewrite of Data::BFDump. The name change is due to a completely new interface, and the addition of functionality which streams the output to a filehandle instead of constructing it in memory and then returning the total dump, (and user complaints that BFDump is annoying to type :-). This means that the memory overhead of dumping using Data::Stream is signifigantly lower than any of the other perl serializers. Data::Stream does a breadth first traversal of the object being dumped, but this pass is for analysis only. A second depth first pass is required to actually output the structure. This two pass approach means that Data::Stream can correctly handle a number of edge cases that none of the other existing serialization modules currently can. Extra effort was put into ensuring that structures with readonly and aliased elements are dumped correctly. Other module names I considered were Data::Streamer Data::Dumper::Streamer and Data::Serialize and also preserving the BFDump name. After discussions with various people from Perlmonks the consensus was that Data::Stream was the preferred choice. regards yves enteredby: YVES (Yves) enteredon: Fri Nov 7 17:55:20 2003 GMT The resulting entry would be: Data:: ::Stream bdhhp Stream a data dump to a filehandle YVES Thanks for registering, -- The PAUSE PS: The following links are only valid for module list maintainers: Registration form with editing capabilities: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=3450_ca521c7f0c1ff655&SUBMIT_pause99_add_mod_preview=1 Immediate (one click) registration: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=3450_ca521c7f0c1ff655&SUBMIT_pause99_add_mod_insertit=1
Re: Module submission Data::Stream
On Fri, Nov 07, 2003 at 06:55:21PM +0100, Perl Authors Upload Server wrote: > > The following module was proposed for inclusion in the Module List: > > modid: Data::Stream > DSLIP: bdhhp > description: Stream a data dump to a filehandle > userid: YVES (Yves) > chapterid:6 (Data_Type_Utilities) > communities: > www.perlmonks.org > > similar: > Data::BFDump Data::Dumper Data::Dump > > rationale: > > Data::Stream is a total rewrite of Data::BFDump. The name change is > due to a completely new interface, and the addition of functionality > which streams the output to a filehandle instead of constructing it > in memory and then returning the total dump, (and user complaints > that BFDump is annoying to type :-). This means that the memory > overhead of dumping using Data::Stream is signifigantly lower than > any of the other perl serializers. > > Data::Stream does a breadth first traversal of the object being > dumped, but this pass is for analysis only. A second depth first > pass is required to actually output the structure. This two pass > approach means that Data::Stream can correctly handle a number of > edge cases that none of the other existing serialization modules > currently can. Extra effort was put into ensuring that structures > with readonly and aliased elements are dumped correctly. > > Other module names I considered were Data::Streamer > Data::Dumper::Streamer and Data::Serialize and also preserving the > BFDump name. After discussions with various people from Perlmonks > the consensus was that Data::Stream was the preferred choice. A "Data::Stream" could be just about anything. Doesn't say what it does. Although "stream" is _how_ it does it, "dump" is what it actually does. So it should have dump in the name along with stream. I'd suggest: Data::StreamDump Tim.
Re: Module submission IO::Shaper
Great, thanks! Net-Shaper-0.3.tar.gz has been submitted to CPAN. (same as IO::Shaper-0.2 except for name) Ben - Original Message - From: "Tim Bunce" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, November 06, 2003 8:58 AM Subject: Re: Module submission IO::Shaper > On Thu, Nov 06, 2003 at 08:43:19AM +0100, Perl Authors Upload Server wrote: > > > > The following module was proposed for inclusion in the Module List: > > > > modid: IO::Shaper > > DSLIP: adpOp > > description: Simple Multiplexing TCP Traffic Shaper > > userid: BHOLZMAN (Benjamin Holzman) > > chapterid: 21 (File_Handle_Input_Output) > > communities: > > > > similar: > > > > rationale: > > > > When testing a networked application, it is often desirous to limit > > the bandwidth of network connections. This can be used to uncover > > race conditions and to simulate real-world behavior. This module > > implements a multiplexing tcp traffic shaper that accomplishes this. > > Perhaps a better name would be Net::Shaper, but it's built on the > > IO:: modules. > > Lots of Net::* modules (and others elsewhere) are built on the IO:: modules. > Names should reflect what the module does rather than how it dos it. > > Net::Shaper seems okay. > > Tim. >
Welcome new user BNEGRAO
Welcome Bruno Negrao Guimaraes Zica, PAUSE, the Perl Authors Upload Server, has a userid for you: BNEGRAO Once you've gone through the procedure of password approval (see the separate mail you should receive about right now), this userid will be the one that you can use to upload your work or edit your credentials in the PAUSE database. This is what we have stored in the database now: Name: Bruno Negrao Guimaraes Zica email: CENSORED homepage: enteredby: Johan Vromans Please note that your email address is exposed in various listings and database dumps. You can register with both a public and a secret email if you want to protect yourself from SPAM. If you want to do this, please visit https://pause.perl.org/pause/authenquery?ACTION=edit_cred or http://pause.perl.org/pause/authenquery?ACTION=edit_cred If you need any further information, please visit $CPAN/modules/04pause.html. If this doesn't answer your questions, contact [EMAIL PROTECTED] Thank you for your prospective contributions, The Pause Team
PAUSE ID request (TWH; Todd Harris)
Request to register new user fullname: Todd Harris userid: TWH mail: CENSORED homepage: http://toddot.net/ why: I'm preparing a module called GD::SVG that enables scripts that use GD to generate scalable vector graphics (SVG) output simply by changed the "use". The following links are only valid for PAUSE maintainers: Registration form with editing capabilities: https://pause.perl.org/pause/authenquery?ACTION=add_user&USERID=5450_f2da699f9cf38cf4&SUBMIT_pause99_add_user_sub=1 Immediate (one click) registration: https://pause.perl.org/pause/authenquery?ACTION=add_user&USERID=5450_f2da699f9cf38cf4&SUBMIT_pause99_add_user_Definitely=1
Re: Module submission IO::Shaper
Ya know, on second thought, Net::Shaper should really be in chapter 5 (Networking_Devices_IPC), not 21. -Original Message- From: Tim Bunce <[EMAIL PROTECTED]> Sent: Nov 6, 2003 8:58 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Module submission IO::Shaper On Thu, Nov 06, 2003 at 08:43:19AM +0100, Perl Authors Upload Server wrote: > > The following module was proposed for inclusion in the Module List: > > modid: IO::Shaper > DSLIP: adpOp > description: Simple Multiplexing TCP Traffic Shaper > userid: BHOLZMAN (Benjamin Holzman) > chapterid: 21 (File_Handle_Input_Output) > communities: > > similar: > > rationale: > > When testing a networked application, it is often desirous to limit > the bandwidth of network connections. This can be used to uncover > race conditions and to simulate real-world behavior. This module > implements a multiplexing tcp traffic shaper that accomplishes this. > Perhaps a better name would be Net::Shaper, but it's built on the > IO:: modules. Lots of Net::* modules (and others elsewhere) are built on the IO:: modules. Names should reflect what the module does rather than how it dos it. Net::Shaper seems okay. Tim.
Re: Module submission IO::Shaper
oh, you already figured that out :-) -Original Message- From: [EMAIL PROTECTED] Sent: Nov 7, 2003 5:06 PM To: Tim Bunce <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: Module submission IO::Shaper Ya know, on second thought, Net::Shaper should really be in chapter 5 (Networking_Devices_IPC), not 21. -Original Message- From: Tim Bunce <[EMAIL PROTECTED]> Sent: Nov 6, 2003 8:58 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Module submission IO::Shaper On Thu, Nov 06, 2003 at 08:43:19AM +0100, Perl Authors Upload Server wrote: > > The following module was proposed for inclusion in the Module List: > > modid: IO::Shaper > DSLIP: adpOp > description: Simple Multiplexing TCP Traffic Shaper > userid: BHOLZMAN (Benjamin Holzman) > chapterid: 21 (File_Handle_Input_Output) > communities: > > similar: > > rationale: > > When testing a networked application, it is often desirous to limit > the bandwidth of network connections. This can be used to uncover > race conditions and to simulate real-world behavior. This module > implements a multiplexing tcp traffic shaper that accomplishes this. > Perhaps a better name would be Net::Shaper, but it's built on the > IO:: modules. Lots of Net::* modules (and others elsewhere) are built on the IO:: modules. Names should reflect what the module does rather than how it dos it. Net::Shaper seems okay. Tim.
[namespace] new XPath module
Fellow Perlers, I am working on an XPath implementation that is less memory hungry that XML::XPath, which is based on XML::Parser, which creates trees of hashes and arrays. My module is slower than XML::XPath, but uses FAR less memory. It is based on a data structure that does not contain the children of a node, but the (unique) parent. Searches/queries are done backwards. It is therefore very fast on queries like //apples, if you are into fruit. What could be a good namespace for this? Perhaps XML::Xpath::Backwards? Any thoughts are appreciated. Teun van Eijsden PAUSE id: TEUN
Module submission GD::Text::Arc
The following module was proposed for inclusion in the Module List: modid: GD::Text::Arc DSLIP: adpOp description: Draw TrueType text around edge of circle userid: DALLEN (Daniel Allen) chapterid: 18 (Images_Pixmaps_Bitmaps) communities: will be discussed in kw.pm / to.pm mailing lists, possibly perlmonks similar: rationale: GD can draw truetype text at any angle in a straight line. However, to draw text along a curve (such as around the top or bottom of a circle), one must invest some time to make the math work out correctly, as there are no existing modules to do that automatically. The math is not difficult at all, but getting the angles and signs correct can be tricky. This module currently draws text to follow a circular arc. Parameters include: GD image object, font-name, size, text, x and y position of circle origin, angle, justification, and orientation. The angle can either be the starting angle on the circle, or the center of the text (depending on the justification). Justification is either left- or center. Orientation can be clockwise or counterclockwise (as would be natural for at the top or bottom of the circle, respectively). I plan to eventually add "x-axis" and "y-axis" to allow the arc to follow an ellipse as well. Namespace: GD::Text::Arc is as simple and straight-forward a name as any other I have considered. Possible names I've considered and rejected: GD::Text::Wrap::Circle (rejected because it doesn't wrap text inside a circle, as you might expect by the superclass) GD::Text::Path::Arc (appropriate if somebody was going to write the superclass, to follow arbitrary shapes. But the name doesn't sound as clean.) GD::Text::Circular (alternative name; would be OK but it doesn't sound as clean.) enteredby: DALLEN (Daniel Allen) enteredon: Fri Nov 7 22:45:49 2003 GMT The resulting entry would be: GD::Text:: ::Arc adpOp Draw TrueType text around edge of circle DALLEN Thanks for registering, -- The PAUSE PS: The following links are only valid for module list maintainers: Registration form with editing capabilities: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=6450_74cc266877c98489&SUBMIT_pause99_add_mod_preview=1 Immediate (one click) registration: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=6450_74cc266877c98489&SUBMIT_pause99_add_mod_insertit=1
Module submission Array::Judy
The following module was proposed for inclusion in the Module List: modid: Array::Judy DSLIP: idhOp description: Interface to the Judy C library userid: BHOLZMAN (Benjamin Holzman) chapterid:6 (Data_Type_Utilities) communities: Judy was briefly discussed on p5p several months ago. similar: rationale: Judy arrays are extremely fast and memory efficient at virtually all data sizes, beating even hashes. Essentially, they are digital tries with a polymorphic structure; there are multiple storage paradigms for each node in the tree, and each node is automatically upgraded or downgraded according to how many children it has. The JudyL data structure maps words to words/pointers. The JudySL data structure (built of JudyLs) maps strings to words/pointers. Clearly JudyL should have an array-like interface and JudySL should have a hash-like interface. I plan to create a tied interface, but for speed will also supply a light OO interface as well. There is also a Judy1 array (maps word to bit), which could map to an array or hash whose values are implicitly boolean, and extremely space efficient. As an aside, I have used Judy arrays in an object database, and have been extremely impressed with its performance. Before I used Judy arrays, I had a hash table implementation (hash function stolen from perl) and the Judy arrays blew the pants off of it! enteredby: BHOLZMAN (Benjamin Holzman) enteredon: Fri Nov 7 23:44:18 2003 GMT The resulting entry would be: Array:: ::JudyidhOp Interface to the Judy C library BHOLZMAN Thanks for registering, -- The PAUSE PS: The following links are only valid for module list maintainers: Registration form with editing capabilities: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=7450_429fcab043f240c5&SUBMIT_pause99_add_mod_preview=1 Immediate (one click) registration: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=7450_429fcab043f240c5&SUBMIT_pause99_add_mod_insertit=1
Module submission Net::DNSBL::MultiDaemon
The following module was proposed for inclusion in the Module List: modid: Net::DNSBL::MultiDaemon DSLIP: Rdpfg description: Multiple DNSBL interrogator for MTA's userid: MIKER (Michael Robinton) chapterid: 16 (Server_and_Daemon_Utilities) communities: [EMAIL PROTECTED] similar: N/A enhances capability of BIND 9 rationale: 1) network daemon 2) used to interrogate multiple DNSBL's with a single query May be used standalone or as a plugin to a BIND 9 installation i.e. Net::DNSBL::MultiDaemon Integrates seamlessly with Mail::SpamCannibal enteredby: MIKER (Michael Robinton) enteredon: Sat Nov 8 00:16:32 2003 GMT The resulting entry would be: Net::DNSBL:: ::MultiDaemon Rdpfg Multiple DNSBL interrogator for MTA'sMIKER Thanks for registering, -- The PAUSE PS: The following links are only valid for module list maintainers: Registration form with editing capabilities: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=8450_4b94cf701789c685&SUBMIT_pause99_add_mod_preview=1 Immediate (one click) registration: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=8450_4b94cf701789c685&SUBMIT_pause99_add_mod_insertit=1
