Skip Menu |

This queue is for tickets about the Text-NSP CPAN distribution.

Report information
The Basics
Id: 15862
Status: resolved
Priority: 0/
Queue: Text-NSP

People
Owner: Nobody in particular
Requestors: grousse [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Incorrect packaging practices
The distribution use top-level namespaces for all its measurement packages. This is a bad practice, whereas it could easily keep them under its own Text::NSP namespace. For instance, leftFisher should rather be Text::NSP::leftFisher. As a side effect, it would make installation procedure easier: just putting all pm files in a lib/ subdirectory ensure MakeMaker correctely process them. Also, those are modules, not executable, so I don't see the need to scan PATH for them. Installation procedure is supposed to correctly install them in @INC, where 'use' directive will automatically find them at compile time, which is more efficient than 'requires' directive at execution time.
From: tpederse
Thank you for reporting this. This has been resolved as of version 0.91, where measures are now stored in a hierarchical fashion. We have also stopped putting the measures in the PATH, they are now in PERL5LIB, where they should have been from the start. On Wed Nov 16 09:11:58 2005, GROUSSE wrote: Show quoted text
> The distribution use top-level namespaces for all its measurement > packages. This is a bad practice, whereas it could easily keep
them Show quoted text
> under its own Text::NSP namespace. For instance, leftFisher should > rather be Text::NSP::leftFisher. As a side effect, it would make > installation procedure easier: just putting all pm files in a lib/ > subdirectory ensure MakeMaker correctely process them. > > Also, those are modules, not executable, so I don't see the need to > scan PATH for them. Installation procedure is supposed to
correctly Show quoted text
> install them in @INC, where 'use' directive will automatically
find Show quoted text
> them at compile time, which is more efficient than 'requires' > directive at execution time.