Re^5: Nonblocking read server

I've been thinking about it, but it really needs a humongous test suite ( much more than the 50 or so test programs I have now ) and it needs automation of client/server test cases which now require visual validation, and "more silly excuses"x100 .

Comment on Re^5: Nonblocking read server

Replies are listed 'Best First'.
Re^6: Nonblocking read server by perl-diddler (Chaplain) on Aug 31, 2019 at 00:28 UTC
It's so sad, but those who are most conscientious are least likely to release code (and vice versa). I don't know of a good solution to that problem, as I hesitated for years before releasing anything and even then got lots of grief for stuff I'd used for years -- even when choosing a very unlikely to be wanted/used namespace for my first module -- I was given grief for taking up the entire 'P' namespace (like so many modules are named P::Something). Finally one of the detractors boiled down their dislike: it was too DWIM'y. My jaw dropped and I just shook my head. It was too much like what perl was supposed to be? Oi.	[reply]

Replies are listed 'Best First'.

Re^6: Nonblocking read server
by perl-diddler (Chaplain) on Aug 31, 2019 at 00:28 UTC

Finally one of the detractors boiled down their dislike: it was too DWIM'y. My jaw dropped and I just shook my head. It was too much like what perl was supposed to be? Oi.

[reply]