On Sun, Jun 10, 2012 at 08:14:18PM -0400, bulk 88 wrote: > I am planning to release a event loop integration/async I/O/multi OS > threading "framework" module for Perl on Windows. It supports > delivering events into a dozen different event loops, around half of > which are existing perl modules (GTK, Wx, Perl/TK, Tkx/Tcl, > Win32::Gui, Win32::IPC, maybe more). It has nothing to do with > ithreads. It gets events from Win32 Thread Sync Objects, async kernel > I/O or non-perl multi threaded C libraries/random OS threads. It > obviously has to go in Win32::* namespace. Does anyone object to name > Win32::Async? Other words that I didn't like or rejected were > AsyncToolkit, AsyncTK, AnyEvent, UniIO, Threads, ThreadFusion.
I have a weak objection, simply because I tend to stick "::Async" as a suffix on module names to indicate IO::Async integration (Term::TermKey::Async, IPC::PerlSSH::Async, Tickit::Async, ...). If you could consider instead Win32::Events perhaps? Failing that I'm sure I can live with it ;) .oO( Though that would then raise the question of what -would- the Win32 + IO::Async module be called. That does sound like a fun and interesting thing to write based on this... ) -- Paul "LeoNerd" Evans leon...@leonerd.org.uk ICQ# 4135350 | Registered Linux# 179460 http://www.leonerd.org.uk/
signature.asc
Description: Digital signature
