On Thursday, 12 July 2018 at 22:17:29 UTC, Luís Marques wrote:
On Thursday, 12 July 2018 at 21:51:18 UTC, aliak wrote:
Cool, is there on going work to sprucing up the D repl in the
dlang-community repo or is this a new attempt? Either way if
something is happening here then awesome!
Ah, that
On Friday, 13 July 2018 at 16:55:27 UTC, Seb wrote:
Did you try the Docker image?
No, I just ran it on my Ubuntu VM. Is it important that I try? I
was just providing feedback that it doesn't seem to run with LDC
either.
On Friday, 13 July 2018 at 16:20:03 UTC, Luís Marques wrote:
On Friday, 13 July 2018 at 06:22:41 UTC, Jacob Carlborg wrote:
On Friday, 13 July 2018 at 02:26:28 UTC, jmh530 wrote:
No Windows support.
For drepl:
"Works on any OS with full shared library support by DMD
(currently linux, OSX,
something called EasyJIT)
[3] https://gist.github.com/eldar/2294388
I just wanted to know what the REPL semantics were, not so much
actually use the REPL day to day. For my DHDL stuff I don't think
the LDC JIT particularly applies, it's more source code
translation stuff.
On Friday, 13 July 2018 at 06:22:41 UTC, Jacob Carlborg wrote:
On Friday, 13 July 2018 at 02:26:28 UTC, jmh530 wrote:
No Windows support.
For drepl:
"Works on any OS with full shared library support by DMD
(currently linux, OSX, and FreeBSD)."
For macOS that means using LDC.
It doesn't
On Thursday, 12 July 2018 at 22:17:29 UTC, Luís Marques wrote:
Ah, that explains why my clone of drepl didn't compile: it was
the Martin Novak's repo, not the D community one. Although on
macOS it still doesn't compile, because of the lack of
_rt_loadLibrary.
Have you considered using LDC
On Friday, 13 July 2018 at 02:26:28 UTC, jmh530 wrote:
No Windows support.
For drepl:
"Works on any OS with full shared library support by DMD
(currently linux, OSX, and FreeBSD)."
For macOS that means using LDC.
--
/Jacob Carlborg
On Thursday, 12 July 2018 at 22:17:29 UTC, Luís Marques wrote:
I actually never tried the existing REPLs, what are your issues
with them?
No Windows support.
For drepl:
"Works on any OS with full shared library support by DMD
(currently linux, OSX, and FreeBSD)."
On Thursday, 12 July 2018 at 22:24:19 UTC, Luís Marques wrote:
Right. Hopefully there aren't too many weird cases once that is
generalized to other corners of the language. I also never used
REPLs for major development, only for debugging and minor
tests, so I don't have experience with that
On Thursday, 12 July 2018 at 19:07:15 UTC, Luís Marques wrote:
Consider a D REPL session like this:
Unlike cling, drepl doesn't seem to support overloading:
Welcome to D REPL.
D> import std.stdio;
std
D> void bar(long) { writeln("long"); }
bar
D> void bar(int) { writeln("int"); }
bar
D>
On Thursday, 12 July 2018 at 22:04:39 UTC, jmh530 wrote:
I think the mental model of someone coming from a dynamic
language would be as if bar is dynamically re-compiled when the
foo(int x) is entered.
Right. Hopefully there aren't too many weird cases once that is
generalized to other
On Thursday, 12 July 2018 at 21:51:18 UTC, aliak wrote:
Cool, is there on going work to sprucing up the D repl in the
dlang-community repo or is this a new attempt? Either way if
something is happening here then awesome!
Ah, that explains why my clone of drepl didn't compile: it was
the
On Thursday, 12 July 2018 at 21:15:46 UTC, Luís Marques wrote:
On Thursday, 12 July 2018 at 20:33:04 UTC, jmh530 wrote:
On Thursday, 12 July 2018 at 19:07:15 UTC, Luís Marques wrote:
Most REPLs I've used are for languages with dynamic typing.
Perhaps take a look at a C REPL and see what it
On Thursday, 12 July 2018 at 21:15:46 UTC, Luís Marques wrote:
On Thursday, 12 July 2018 at 20:33:04 UTC, jmh530 wrote:
On Thursday, 12 July 2018 at 19:07:15 UTC, Luís Marques wrote:
Most REPLs I've used are for languages with dynamic typing.
Perhaps take a look at a C REPL and see what it
On Thursday, 12 July 2018 at 20:33:04 UTC, jmh530 wrote:
On Thursday, 12 July 2018 at 19:07:15 UTC, Luís Marques wrote:
Most REPLs I've used are for languages with dynamic typing.
Perhaps take a look at a C REPL and see what it does?
Well, cling calls the original function:
[cling]$ #import
On Thursday, 12 July 2018 at 19:07:15 UTC, Luís Marques wrote:
Consider a D REPL session like this:
void bar(long x) { writeln(x); }
void foo() { bar(42); }
42
void bar(int) {}
Assuming implementation complexity is not an issue, what do you
feel is the more natural semantics for a
On Thursday, 12 July 2018 at 19:07:15 UTC, Luís Marques wrote:
Assuming implementation complexity is not an issue, what do you
feel is the more natural semantics for a REPL? Should foo now
call bar(int), or should it still call bar(long)? (feel free to
generalize the issue)
BTW, this
Consider a D REPL session like this:
void bar(long x) { writeln(x); }
void foo() { bar(42); }
42
void bar(int) {}
Assuming implementation complexity is not an issue, what do you
feel is the more natural semantics for a REPL? Should foo now
call bar(int), or should it still call
18 matches
Mail list logo