From: Perry Smith Date: 2012-08-03T23:14:40+09:00 Subject: [ruby-core:46964] Re: (Half-baked DRAFT) new `require' framework --Apple-Mail=_8F903F2F-C4EF-4C4B-9542-0F84A337BC39 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Aug 3, 2012, at 5:21 AM, Joshua Ballanco wrote: > On Tuesday, July 31, 2012 at 3:29 PM, SASADA Koichi wrote: >> (2) load script from location from other than `file system'. >> (example: require from zip archive, require over network, >> require files provided by gem efficiently using file location db) >=20 > I'll echo what Charles said in his response: file lookup and code = loading should be handled independently. I would even go so far as to = say that code loading could be made an independent API from require, = enabling the loading of code from memory or, say, from a network socket.=20= The configure / build code does a magic dance to basically load from a = string. So we have a use case for loading code from memory. Loading = from a socket sounds exciting too. --Apple-Mail=_8F903F2F-C4EF-4C4B-9542-0F84A337BC39 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii
On Aug 3, 2012, at 5:21 AM, Joshua Ballanco wrote:

On Tuesday, July 31, 2012 at 3:29 PM, SASADA Koichi wrote:
(2) load script from location from other than `file system'.
(example: require from zip archive, require over network,
require files provided by gem efficiently using file location db)

I'll echo what Charles said in his response: file lookup and code loading should be handled independently. I would even go so far as to say that code loading could be made an independent API from require, enabling the loading of code from memory or, say, from a network socket. 

The configure / build code does a magic dance to basically load from a string.  So we have a use case for loading code from memory.  Loading from a socket sounds exciting too.


--Apple-Mail=_8F903F2F-C4EF-4C4B-9542-0F84A337BC39--