Skip to content

REPL packaging #1085

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
odersky opened this issue Feb 14, 2016 · 6 comments
Closed

REPL packaging #1085

odersky opened this issue Feb 14, 2016 · 6 comments

Comments

@odersky
Copy link
Contributor

odersky commented Feb 14, 2016

We should make a command (I suggest doti) to launch the Dotty REPL.

@smarter
Copy link
Member

smarter commented Feb 23, 2016

What about having a dotty command instead which behaves similarly to scala ? (Running dotty without arguments brings up the REPL, running dotty Foo runs Foo.class with the correct bootclasspath and classpath).

@smarter
Copy link
Member

smarter commented Mar 7, 2016

DOPPLER could be the DOtty Precise Program LinkER /cc @DarkDimius :)

@smarter
Copy link
Member

smarter commented Mar 8, 2016

On the subject of running the REPL, we should also make sure that it can be run from sbt using sbt console and https://github.com/smarter/dotty-bridge, this require reimplementing https://github.com/sbt/sbt/blob/0.13/compile/interface/src/main/scala/xsbt/ConsoleInterface.scala and in particular this method:

def run(args: Array[String], bootClasspathString: String, classpathString: String,
  initialCommands: String, cleanupCommands: String, loader: ClassLoader,
  bindNames: Array[String], bindValues: Array[Any], log: Logger): Unit

which gives a good overview of the kind of things that the REPL needs to support.

@retronym
Copy link
Member

retronym commented Mar 8, 2016

Note that for the purposes of interactively testing out the REPL, you can use runMain ReplClass with a few custom settings:

fork in run := true

connectInput in run := true

outputStrategy in run := Some(StdoutOutput)

addCommandAlias("repl",   "repl/compile:runMain repl.Main -usejavacp")

See the Scala SBT build for more details.

@DarkDimius
Copy link
Contributor

@retronym, thanks!

som-snytt added a commit to som-snytt/dotty that referenced this issue Mar 29, 2016
Introduce a "scripter" phase in the monolithic `Frontend`
for transforming snippets.

Apparently `<script>` is not a friendly package name, so
it must always be fixed.
som-snytt added a commit to som-snytt/dotty that referenced this issue Apr 2, 2016
Introduce a "scripter" phase in the monolithic `Frontend`
for transforming snippets.

Apparently `<script>` is not a friendly package name, so
it must always be fixed.
som-snytt added a commit to som-snytt/dotty that referenced this issue Apr 8, 2016
Introduce a "scripter" phase in the monolithic `Frontend`
for transforming snippets.

Apparently `<script>` is not a friendly package name, so
it must always be fixed.
som-snytt added a commit to som-snytt/dotty that referenced this issue Apr 28, 2016
Introduce a "scripter" phase in the monolithic `Frontend`
for transforming snippets.

Apparently `<script>` is not a friendly package name, so
it must always be fixed.
som-snytt added a commit to som-snytt/dotty that referenced this issue May 16, 2016
Introduce a "scripter" phase in the monolithic `Frontend`
for transforming snippets.

Apparently `<script>` is not a friendly package name, so
it must always be fixed.
@felixmulder
Copy link
Contributor

felixmulder commented Oct 11, 2016

We currently have dotr and dotc for this. So I'm closing this issue, it might also be good to reference this issue here: #1526

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants