Dan Sugalski <[EMAIL PROTECTED]> writes: > >*) It makes optionalizing (now there's a good word... :) the functions >easier for platforms that just don't have 'em. Like, say, the Palm, or >embedded gadgets. (Most teddy bears aren't likely to come with a network >stack...) Most everything will have a network stack if you believe the hype. When a Palm "is" a WAP Phone it will have one, and while Teddy Bears may not I am sure Furbie-II will... -- Nick Ing-Simmons
- RFC 146 (v1) Remove socket functions from core Perl6 RFC Librarian
- Re: RFC 146 (v1) Remove socket functions from cor... Jarkko Hietaniemi
- Re: RFC 146 (v1) Remove socket functions from cor... Tom Christiansen
- Re: RFC 146 (v1) Remove socket functions from... Dan Sugalski
- Re: RFC 146 (v1) Remove socket functions ... Tom Christiansen
- Re: RFC 146 (v1) Remove socket functi... Nathan Torkington
- Re: RFC 146 (v1) Remove socket f... David L. Nicol
- Splitting core functions int... Alan Burlison
- Re: Splitting core funct... Grant M.
- Re: RFC 146 (v1) Remove socket functi... Dan Sugalski
- Re: RFC 146 (v1) Remove socket f... Nick Ing-Simmons
- Re: RFC 146 (v1) Remove sock... Dan Sugalski
- Re: WAP-enabled cellular... Joshua N Pritikin
- Re: RFC 146 (v1) Remove socket functions from cor... Michael Maraist
- Re: RFC 146 (v1) Remove socket functions from... Tom Christiansen
- Re: RFC 146 (v1) Remove socket functions ... Bradley M. Kuhn
- Re: RFC 146 (v1) Remove socket functi... Tom Christiansen
- Re: RFC 146 (v1) Remove socket functions from... Stephen P. Potter
- Re: RFC 146 (v1) Remove socket functions ... Tom Christiansen
- Re: RFC 146 (v1) Remove socket functi... Dan Sugalski
- Re: RFC 146 (v1) Remove socket f... Nathan Torkington