io watchers
  -tailpoll -- how to do this?!
  [+-] notation to modify the event mask

screensaver watchers
  by priority?

rename watchvar to 'var', 'assign', or 'assignment'

croak should route through Carp!

documentation
  how to design new event types
  the mysteries of exception handling
  how to use $Event::API
  io events 'got' has both alpha & numeric encoding

Event::Watcher
  complete -priority => -nice migration (in a few weeks)
  remove support for leading dashes (by Oct 3)
  allow editing of reentrant?  only when not running?

There is currently no way to take advantage of pe_tmevent in a purely
perl implemented watcher.

clean up sleep()

export_fail hook to autoload

optimization
  update io event-mask without invalidating cache
  use fancy profiler tricks to figure out how to improve performance!

time
  CORE::time?
  alternate time encodings
  changing speed of time
  for year 2000 testing :-)

extra assertions for C API

one_event
  configuration of StarvePrio?
  since there is only one queue, could allow more queue priorities...?

accept "%f minutes" & "%f hours" for all time specifications?

---------------------------------------

From: nick@ni-s.u-net.com
Subject: Re: perl 5.004 compatible?
 
Joshua Pritikin <joshua.pritikin@db.com> writes:
>On Fri, 25 Sep 1998 gisle@aas.no wrote:
>> I think we should not do anything that prevents it from working on
>> perl5.004.
>
>I think my opinion is going to be unpopular.
 
Not with me:
 
Adding a non-CORE module to Tk's dependancies will make it harder to install,
so Tk would like Event::* in the core. It is not in the core of 5.004.
Also I suspect we need speed and space clean Event. If 5.005+'s features
assist that use them.
 
Finally it has been shown people only upgrade when the new version has  
features they need (or lacks bugs they don't need), Event could be such  
a feature.

