Thoughts about future releases, in no particular order.
Feel free to share your thoughts with me at  mob@cpan.org .

Possible TODOs:

    ___	wait     timeout
        waitpid  timeout
        waitall  timeout

		wait calls that block for only a limited time
         
    ___ fork { stdin => \@stdin }
    ___ fork { stdin => \$stdin }
    ___ fork { stdin => $stdin }

		pass standard input to the child in a scalar, a list
		reference, or a scalar reference at fork time.
                This seems more satisfactory for a  cmd  style fork that
                possibly can't wait for the parent to write to 
        	Forks::Super::CHILD_STDIN{$pid}.

		With sub style, this needs a file descriptor but maybe
		not an open filehandle?

        fork { stdout => \@output, stderr => \@error }

                when the child process completes, collect its stdout and stderr
                output into the specified arrays. This will conserve 
		filehandles in the parent. But it doesn't allow you to 
		read child output while the child is running.

		Could implement this in terms of a "collect output callback".

        fork { input_fh => [ 'X', 'Y', 'Z' ], output_fh => [ 'STDOUT', 'A' ] }

		open input and output filehandles in the child with the given 
		names, accessible in the parent at something like 
		$Forks::Super::CHILD_FH{$pid}{X}

        incorporate CPU load into system busy-ness calc (see 
		Parallel::ForkControl) (Parallel::ForkControl uses uptime(1) 
		as  a "cheap linux only hack"
		See also: Win32::Process::CpuUsage, Sys::CPU, Sys::CpuLoad).

	incorporate free memory into system busy-ness calc 
		(Parallel::ForkControl)	(Parallel::ForkControl says 
		"non functional")

    ___	implement child handles through IO::Pipe objects

    ___ facilities to suspend jobs when the system gets to busy
        and to resume them when the system gets less busy.
        I bet this will be hard to do with Win32.

    _x_ fork { cpu_affinity => $bitmask }

                <OLD POD>
                On supported systems with multiple cores, and after the 
		successful creating of the child process, attempt to set 
		the CPU affinity for the child process. $mask is typically 
		a bitmask with the lowest level bits indicating whether the 
		lowest numbered CPU's should be used by this process.
                </OLD POD>

                _X_ linux [where /bin/taskset is avail]
		_X_ MSWin32
		___ BSD
		_X_ Cygwin
		_X_ documented
	 	___ Solaris
		___ Irix
		___ OS X
		___ any others ?

    _x_ Fully support changing process priority in Windows. This can be
	done with Win32::API and SetThreadPriority method. Takes on values
	between -2 and 2, or between -7 and 6 "if the thread has the
	REALTIME_PRIORITY_CLASS base class", whatever that is. (Oh, looks
	like we can use GetPriorityClass to figure out what it is).
        (See http://msdn.microsoft.com/en-us/library/ms686277(VS.85).aspx).

	Support for launching tasks on remote hosts (maybe that's beyond
        the scope of this module) See Paralell::PVM?

    _x_ fork { retries => $ntries }

		like Proc::Fork. Call CORE::fork() several times if
		it's not creating child processes.
		_X_ implement
		___ test
		___ document

    ___	configure during build. discover the maximum number of simultaneous
	processes that can be spawned and set MAX_PROC, DEFAULT_MAX_PROC.
	Would also be good to know the max number of open filehandles
	and plan around it.

	Forks::Super::Uninterruptable package for "uninterruptable" versions
	of Perl system calls like  sleep , connect , select($$$$)

    ___ Make Forks::Super safe(r) for unsafe signals (pre 5.7.3, see perlipc).
	Can test with >5.7.3 and Perl::Unsafe::Signals

    ___	Make CONFIG{filehandles} meaningful

    ___	Defect to fix, $Forks::Super::MAX_PROC = "0"

    ___	Decompose source into manageable modules

		Forks::Super::OS, Forks::Super::OS::XXX
		Forks::Super::Filehandle
		Forks::Super::Timeout
		Forks::Super::Uninterruptable
		Forks::Super::Depend

    ___	kill_all($signal), kill($signal, @jobs)

	Deliver a signal to all jobs or to a list of jobs.

    ___ in bg_eval and bg_qx, set 
	$Forks::Super::LAST_JOB_ID, $Forks::Super::LAST_JOB to access
	job information of a job launched from bg_eval or bg_qx.
	Bash users will recognize the similarity of capturing the
	$! variable in a bash script to capture the PID of the
	last background process that was launched.

	From there you can get state information, exit status,
	run times, or all kinds of good information about the job.



