What a mess!

• The design makes no sense at all.

  Queues are (should be) reliable, ordered and efficient, sync-free buffers between producer and consumer threads.

  1. What point is there in having a queue that dies when it reaches the limit the programmer set?

     Now the programmer has to both remember what the limit is, and check it before every enqueue.

     Like having a dog and barking yourself. Completely pointless.

  2. And a queue that throw things away (silently or with a warning) is total corruption of the concept.

     The whole point of a self limiting queue is to provide a self-checking, buffer between producers and consumers that automatically restrains over active producers.

     Can you imagine using a supermarket checkout that random threw items of the current customer into a bin, whenever a new customer miscounted the belt limit and added their items to the end?

  3. (Inherited from the underlying module, but perpetuated.) A queue that allows inserts isn't a queue.

     The ability to insert and delete items into/from the middle of a queue totally violates the design contracts of a 'queue'.

     This is why I rejected patching or modifying Thread::Queue. Because the new owner rendered the module inefficient and corrupt when he added those facilities to the original authors correct and efficient implementation. For no good reason beyond 'making his mark'.

• Even if the design made sense, I would not use a module that is so badly and naively implemented.
  1. Where is the sense in allowing case-insensitive, 'string constant' configuration options?

     If configuration constants make sense, the module should provide proper constants.

  2. If there was any merit in allowing case-insensitive options

     the module should convert them to all upper or all lower on input so that from then on they can be compared directly against hard-coded strings with eq thus avoiding the not inconsequential costs of invoking the regex engine over and over to perform case-insensitive comparisons.

  3. Many other nativities.

In summary: a very bad design, horribly naively implemented. It typifies everything that is wrong with CPAN!