Yes, a pull request would be preferred. It makes it very easy to review the
code and then incorporate it into the master.
As for the command line argument, -X:Sandbox or something like that. I
think the name of the parameter is less of a concern until its all up and
working.
slide
On Mon, Mar 19
On Mon, Mar 19, 2012 at 2:26 PM, Cesar Mello wrote:
> Actually if you find interesting for me to pull this through a command line
> argument, do you have any suggestions on what argument should I create for
> it?
Something like -X:Sandbox (It has to be under -X: so that we don't
conflict with CPy
Actually if you find interesting for me to pull this through a command line
argument, do you have any suggestions on what argument should I create for
it?
Thanks
Best regards
Mello
On Mon, Mar 19, 2012 at 6:21 PM, Cesar Mello wrote:
> Hi Slide,
>
> You mean I should do a pull request when I'm
Hi Slide,
You mean I should do a pull request when I'm finished?
But I'm still just playing around. I've hard-coded a sandboxed appdomain
here just for testing the idea:
https://github.com/cmello/IronLanguages-main/commit/3241688e4917c70a6db4c1b671f42c4144e8bf96
But I get remoting exceptions a
Cesar,
I think this sounds like a pretty good idea for debugging stuff. Are you
familiar with how we work with patches should you get something going?
Thanks,
slide
On Mon, Mar 19, 2012 at 1:35 PM, Cesar Mello wrote:
> Hi,
>
> I would like to know if someone other than me would find useful to
Hi,
I would like to know if someone other than me would find useful to have a
command line argument for sandboxing the ipy console.
I'm trying to implement this but I'm not sure if it is worth. For me it
would make easier to debug and reproduce stuff.
Also I'm curious to know how many people are
