Skip Menu |

This queue is for tickets about the Panda-XS CPAN distribution.

Report information
The Basics
Id: 106277
Status: resolved
Priority: 0/
Queue: Panda-XS
People
Owner: Nobody in particular
Requestors: mjgardner [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Thu Aug 06 19:28:23 2015 mjgardner [...] cpan.org - Ticket created
Subject: Why Panda:: namespace?
I don't understand why Panda-XS, Panda-Install, Panda-URI, etc., are all grouped into a Panda:: top-level namespace. They don't share any commonality other than some mutual dependencies and being mostly written by the same author. In most cases they reimplement other CPAN modules either with XS or with a different interface. Is it just a branding exercise to group them under Panda::? I'd prefer to see these use similar names as the modules they reimplement so they can be found near them when searching.
  Thu Jan 26 17:53:02 2017 syber.rus [...] gmail.com - Correspondence added
Because our company is Crazy Panda. All CPAN's namespaces are taken by a lot of modules most of which are shit. I didn't want to create yet another deep-nested module like Class::Accessor::Fast::XS, so i decided that all our modules goes under Panda:: All modules in Panda:: are extremely fast, and have C++ public interface if they are XS modules. Actually we have much more modules, for example extremely fast zero-copy frameworks and incremental parsers like HTTP Framework, Websocket framework, Panda::Event (very fast Any::Event replacement with C++ interface based by default on libuv), but they are not yet ready for CPAN (no docs, not all tests)
  Thu Jan 26 17:53:02 2017 The RT System itself - Status changed from 'new' to 'open'
  Thu Jan 26 17:53:02 2017 syber.rus [...] gmail.com - Status changed from 'open' to 'resolved'