Much better indeed, but maybe there is still some redundancy left with
the `setup-collects'
option?
http://docs.racket-lang.org/pkg/metadata.html
Laurent
On Tue, Jun 25, 2013 at 11:08 PM, Matthias Felleisen
matth...@ccs.neu.eduwrote:
+1
On Jun 25, 2013, at 4:27 PM, Sam Tobin-Hochstadt
(looks like I'm misunderstanding this option. Forget about it.)
On Wed, Jun 26, 2013 at 10:30 AM, Laurent laurent.ors...@gmail.com wrote:
Much better indeed, but maybe there is still some redundancy left with the
`setup-collects' option?
http://docs.racket-lang.org/pkg/metadata.html
(BTW, there's a file/private/octree-quantize which should move to
where file/gif is.)
An hour ago, Robby Findler wrote:
The sandbox, IMO, is a nice standalone library the does not need to
be in the core. (Ditto for errortrace.)
I like the definition of the core as minimum stuff to get pkgs
On Wed, Jun 26, 2013 at 6:36 AM, Eli Barzilay e...@barzilay.org wrote:
An hour ago, Robby Findler wrote:
The sandbox, IMO, is a nice standalone library the does not need to
be in the core. (Ditto for errortrace.)
I like the definition of the core as minimum stuff to get pkgs
running and we
In general I agree with Robby on the definition of the core as minimum stuff
to get pkgs running and we should be picky about what goes in. BUT, as a
small addendum, I think the idea of sandboxing is so fundamental, I'd rather
see the idea (not necessarily the current implementation) become a
What does being so fundamental have to do with being in the core vs being
in a package? We should not confuse putting things in packages with making
them second-class concepts. We can put racket/sandbox in a package without
necessarily making it any less fundamental to Racket.
Carl Eastlund
On
Fundamental to me is Robby's necessary to install packages. One day we may
wish to offer sandboxing for the installation of packages.
On Jun 26, 2013, at 8:51 AM, Carl Eastlund wrote:
What does being so fundamental have to do with being in the core vs being
in a package? We should
Lots of things that are fundamental in the sense I think you mean are not
in the core: documentation, types, eventspaces.
The building blocks of sandboxing, such as custodians and security guards
and inspectors, are in the core.
Sam
On Jun 26, 2013 8:47 AM, Matthias Felleisen
On Tue, Jun 25, 2013 at 4:32 PM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote:
While moving some files around between packages, I realized that there
are a number of things that could be moved out of the core and into
packages. Here's a partial list of things that I think are not needed
at all
I'm still stuck on the traverse-block problems I posted about a week ago,
but hopefully this is a simpler question to answer than my one from last
week.
I keep getting an error traverse-block-block: no block computed for
traverse-block, and am trying to understand how to interpret this. Does
it
On 06/26/2013 02:32 PM, Sam Tobin-Hochstadt wrote:
[...]
Things that didn't move:
* `mzlib/compile`: This is used in one place in the compiler, and
should probably be handled differently. Matthew, any suggestions?
* `mzlib/unit200`. This is loaded into a new namespace in which code
is
I can move mzlib/contract after you get done with other stuff.
Robby
On Wednesday, June 26, 2013, Sam Tobin-Hochstadt wrote:
On Tue, Jun 25, 2013 at 4:32 PM, Sam Tobin-Hochstadt
sa...@ccs.neu.edujavascript:;
wrote:
While moving some files around between packages, I realized that there
12 matches
Mail list logo
