input to the parser (was Re: Now, to try again...)

--c1z0ojygQhjo93O/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Nicholas Clark <[email protected]> wrote:

> Everyone is quiet.

Give us a chance.  ;)

> I'm assuming we're all sort of thinking that input is certainly
> (I will have failed to mention some things)
> * human readable programming language source (perl5, perl6, whatever else)
> * bytecode (which could be done as in perl5.6 with something like
>     use Byteloader;......)

I am unclear why the parser would take bytecode as input.  Wouldn't that be
direct input for the virtual machine?
 
> and the above can come from
>  * memory (C's zero terminated strings, blocks with lengths, other things
>    native to other languages
>  * files (by filename, file/socket handle, C FILE*, C++ istream, IO
>    system appropriate to the language you're embedding in)

That seems like only sources I can think of....

-- 
Bradley M. Kuhn  -  http://www.ebb.org/bkuhn

--c1z0ojygQhjo93O/
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6PPsl53XjJNtBs4cRAlW5AJ4jDPQKduKBexAlHLB4dFTaFb8SXACgtY7Q
wTxfC8ARbh1gGNZqMyvpnQc=
=ZjvP
-----END PGP SIGNATURE-----

--c1z0ojygQhjo93O/--