develooper Front page | perl.bootstrap | Postings from July 2000

Re: How to move forward (was: Why we're here)

Thread Previous | Thread Next
Uri Guttman
July 24, 2000 13:05
Re: How to move forward (was: Why we're here)
Message ID:
>>>>> "TB" == Tim Bunce <> writes:

  TB> I suggest the following process:

  TB> 1/ One or more people ("the editors") volunteer to collect suggestions
  TB> from others about what problems they believe the perl language has
  TB> *currently*.  *Without* any proposals for how to fix them. *Without* any
  TB> suggestions for new features. Just list them. Perhaps a title and one
  TB> paragraph max of description on each.

  TB> 2/ That person could then consolidate all the inputs. Merging all the
  TB> similar sections and producing a short summary of all the descriptions.

i second this. let's get moving on the top down stuff instead of all
this internals we are seeing. we need a proper/better/whatever spec to
work from.

i will volunteer for a group i call execution. 

the major groups i see (and some notes on each) are:


		op code dispatch loop, event handling, async I/O, safe
		signals, threads (perl and kernel), debugger access.


		simplify for perl to parse Perl, easier language
		extensions, etc.


		access to internals for debugging

	data structures

		dynamic replacing of hash implementation, pseudo hashes


		damian, of course, has some great ideas on this


		new xs and modules

	byte code

		back ends, optimizer, etc


		embedded, palm, minimal perl


		removing deprecated stuff, fewer perlvars, typeglobs,

i am sure there are a few others, but we should keep the number down to
under a dozen.


Uri Guttman  ---------  ----------
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page  -----------
The Best Search Engine on the Net  ----------

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About