Re: Namespace Math::Matrix::Banded

Hi David On Monday, 24.08.2020 17:17:30 David Christensen wrote: > On 2020-08-24 06:46, Lutz Gehlen wrote: [...] > > On Sunday, 23.08.2020 06:37:47 David Christensen wrote: > >> On 2020-08-23 02:40, Lutz Gehlen wrote: > > [...] > > > >>> I am worki

Re: Namespace Math::Matrix::Banded

Hi Neil, On Monday, 24.08.2020 10:06:10 Neil Bowers wrote: [...] > One thing to be aware of, is that if you’re releasing a > distribution Math-Matrix-Banded, then your distribution needs to > include a module Math::Matrix::Banded[*]. Thank you, I wasn't aware of that. > I like the model where yo

Re: Namespace Math::Matrix::Banded

Hi David, thank you for your advice. On Sunday, 23.08.2020 06:37:47 David Christensen wrote: > On 2020-08-23 02:40, Lutz Gehlen wrote: [...] > > I am working on a set of modules dealing with banded matrices > > (aka band matrices or band diagonal matrices). These are a > > c

Namespace Math::Matrix::Banded

Hi all, I am working on a set of modules dealing with banded matrices (aka band matrices or band diagonal matrices). These are a certain kind of sparse matrices where all entries are known to be 0 except close to the main diagonal. Obviously, this condition can be exploited for efficient storage a

Re: Make sure all the modules have the same version number in a distribution

Hi Gabor, On Tuesday, January 08, 2013 09:04:31 Gabor Szabo wrote: > I just wanted to update a distribution and ensure that all the > modules in a distribution have > version number and they are all the same. Please excuse this digression, but would you be so kind to explain why you find this de

Re: How to report missing external dependencies correctly?

Hello David, thanks a lot for your quick and helpful reply. On Tue, Jun 15, 2010 at 08:57:28PM -0400, David Golden wrote: > On Tue, Jun 15, 2010 at 8:37 PM, Lutz Gehlen wrote: > > My questions are: > > 1) Do you think that this is in general a good approach to solve my > >

How to report missing external dependencies correctly?

Hello everybody, I am developing the module SVG::Rasterize, which uses the Perl bindings of the Pango C library. I have got CPAN testers fail reports that I could track down to the following problem: The testing system had the right version of the Pango Perl module (>=1.220), but a too old version

Re: Usage of wantarray

On Wed, May 12, 2010 at 11:32:59AM -0700, Eric Wilhelm wrote: > That might be simple, but no builtins do this, which seems to say > something. If you're still working with lists, you expect them to > behave like lists, and not try to package themselves in a reference The following comment has

Re: Usage of wantarray

Hello everybody, thanks for all your comments. On Wed, May 12, 2010 at 11:49:09AM -0400, Hans Dieter Pearcey wrote: > relatively simple "return an array in list context, or an arrayref in scalar > context" often ends up irritating me more than it's worth (including when I > wrote the function that

Usage of wantarray

Hello everybody, recently, I read the following statement in a CPAN Ratings entry: "this package also uses wantarray (a transgression amongst interface sensibilities)." I also sometimes use wantarray and don't see anything bad about it if the behaviour is documented (which should also be the case

Re: When and how to throw exceptions?

Hi Ovid, On Wed, Apr 07, 2010 at 12:04:08AM -0700, Ovid wrote: > --- On Wed, 7/4/10, Lutz Gehlen wrote: > > What I need a central place for is the definition of the > > actual > > error messages. With my module Exception::EasyThrow, I can > > write at >

Re: When and how to throw exceptions?

Hi Aristotle, sorry for the delayed reply, I had some computer problems and then this topic slipped a bit out of my mind. On Friday 12 March 2010 23:33:40 Aristotle Pagaltzis wrote: > * Lutz Gehlen [2010-02-21 01:40]: > > 1) The first question deals with how to throw exceptions > &g

When and how to throw exceptions?

Hello everybody, I am writing this email to ask two general questions about throwing exceptions. Parts of them are not restricted to Perl and just reflect my general lack of knowledge about how to deal with exceptions in a professional way. So if you think "RTFM" when you read on, I am happy to

Re: Name space discussion Math::BestRotation

Hi Duke, On Friday 05 February 2010 09:49:30 Jonathan Leto wrote: > > 2) Math::GSL: At the beginning I intended to use Math::GSL as a > > back end for the matrix operations. However, I did not get it > > installed on my machine. The issue had already been reported. > > Now I am using Math::MatrixR

Re: Name space discussion Math::BestRotation

Hi Shawn, On Monday 01 February 2010 08:07:59 Shawn H Corey wrote: > Lutz Gehlen wrote: [...] > Is it a module or just a single algorithm? If it's a module, > Math::Vector may be better since it works with vectors. For a > single algorithm (perhaps with multiple subroutines

Re: Name space discussion Math::BestRotation

Hi Dana, On Monday 01 February 2010 02:18:28 Dana Hudes wrote: > I would stick the word Vector in the name. "Rotation" could apply > to geometric objects. Geometric objects are maybe not the biggest problem. At least each object with corners which shall be mapped onto an object with correspondi

Re: Name space discussion Math::BestRotation

Hi Shlomi, thank you for your encouraging comments On Sunday 31 January 2010 22:03:20 Shlomi Fish wrote: > Hi Lutz! > > On Sunday 31 Jan 2010 08:17:40 Lutz Gehlen wrote: [...] > > This is rather a "request for comments" so to > > speak. So if you have any comme

Name space discussion Math::BestRotation

Hello everybody, I have developed a module that computes the best rotation that maps a set of vectors onto another set of vectors. "Best rotation" means here that it minimizes the sum of the squared distances between each two corresponding vectors. The working title of the module is Math::BestR

Re: Name space: throwing exceptions easily

Hello Eric, On Sun, Jun 29, 2008, Eric Wilhelm wrote: > # from Lutz Gehlen > # on Saturday 28 June 2008 04:51: > >__PACKAGE__->mk_exception_functions > >    (messages => {foo => 'Error foo occurred.'}, > >    exception_class => 'Exception::Cl

Re: Name space: throwing exceptions easily

Hello Aristotle, thanks for your feedback. On Sun, Jun 29, 2008, Aristotle Pagaltzis wrote: > * Lutz Gehlen <[EMAIL PROTECTED]> [2008-06-28 13:55]: > > The module uses the package Exception::Class::EasyThrow > > but I don't know if this is really a good name. > >

Re: Name space: throwing exceptions easily

Hi sawyer x, thanks for your suggestion. On Sun, Jun 29, 2008, sawyer x wrote: > How about Exception::Easy ? The idea to put it out of the Exception::Class name space is definitely worth considering because my module can in fact deal with any class that implements a throw method and I am planni

Name space: throwing exceptions easily

Hello everybody, I am developing a module to make throwing Exception::Class objects easier. The goal is to make the code to throw an exception shorter and to make it possible to keep all error messages at some central place. The module works quite similarly to Class::Accessor and provides a fu