Hey guys, I heard back from the author... What he wants to do for now is use the following:
Data::RRD::SharedModule Data::RRD::Piped I have pasted his comment below: >> I will talk this over with the author and see what he has to say - >thanks >> for your help and input! > the reason for it to be two modules is, that the piped module works even when you do not manage to compile the shared perl object ... having both in one is sort of pointless ... as for the name, this is fine ... we can have a 3 part name ... cheers tobi Duncan McGreggor writes: >I will talk this over with the author and see what he has to say - thanks >for your help and input! > >[EMAIL PROTECTED] writes: >In article <[EMAIL PROTECTED]>, Perl Authors >Upload Server <[EMAIL PROTECTED]> wrote: > >> The following module was proposed for inclusion in the Module List: >> >> modid: Data::RRDs >> DSLIP: Rdhfg >> description: Access rrdtool as a shared module > >what is a shared module? > >a better name is > > Data::RRD::SharedModule > >however, you already have another Data::RDD module proposed. >i think you might want to combine both of these approaches >in a single module named Data::RDD. > >-- >brian d foy (one of many PAUSE admins), http://pause.perl.org >please send all messages back to [EMAIL PROTECTED] >
