Setting package in Scala REPL
Is there a way in the Scala REPL to set the "active" package scope ? Say I have a package com.package
with class A
, I want to be able to type new A()
instead of new com.package.A()
without explicitly doing import com.package.A
. There might be a number of other classes in that package I'm interested into and I don't want to polute my REPL's global namespace by doing import com.package._
.
Even better, I'd like to define class A without typing its fully qualified name. Something like:
package com.package // do this once
class A
class B
val a = new A()
val b = new B()
I'm aware of the :paste -raw
command, but that would require me to type package com.package
for each block; I'm really looking for a stateful command to change the "current working package", if you will.
scala read-eval-print-loop
add a comment |
Is there a way in the Scala REPL to set the "active" package scope ? Say I have a package com.package
with class A
, I want to be able to type new A()
instead of new com.package.A()
without explicitly doing import com.package.A
. There might be a number of other classes in that package I'm interested into and I don't want to polute my REPL's global namespace by doing import com.package._
.
Even better, I'd like to define class A without typing its fully qualified name. Something like:
package com.package // do this once
class A
class B
val a = new A()
val b = new B()
I'm aware of the :paste -raw
command, but that would require me to type package com.package
for each block; I'm really looking for a stateful command to change the "current working package", if you will.
scala read-eval-print-loop
So, I guess stackoverflow.com/a/18510229/6309 wouldn't be helpful either?
– VonC
Aug 16 '14 at 19:37
1
there is currently no support for that because packages are actually used in the internals of the REPL (classes defined in the REPL don't actually live in the root package), but that would make an interesting feature request...
– gourlaysama
Aug 16 '14 at 19:41
@VonC: No, this would not allow me to define new classes without a fully qualified name, as per my question.
– gsimard
Aug 16 '14 at 19:45
Ditto @gourlaysama The use case is testing existing classes with package-private access.
– som-snytt
Aug 18 '14 at 15:20
Possible duplicate of How to use members with default (package) or private access level in REPL?
– Jacek Laskowski
Oct 14 '15 at 9:26
add a comment |
Is there a way in the Scala REPL to set the "active" package scope ? Say I have a package com.package
with class A
, I want to be able to type new A()
instead of new com.package.A()
without explicitly doing import com.package.A
. There might be a number of other classes in that package I'm interested into and I don't want to polute my REPL's global namespace by doing import com.package._
.
Even better, I'd like to define class A without typing its fully qualified name. Something like:
package com.package // do this once
class A
class B
val a = new A()
val b = new B()
I'm aware of the :paste -raw
command, but that would require me to type package com.package
for each block; I'm really looking for a stateful command to change the "current working package", if you will.
scala read-eval-print-loop
Is there a way in the Scala REPL to set the "active" package scope ? Say I have a package com.package
with class A
, I want to be able to type new A()
instead of new com.package.A()
without explicitly doing import com.package.A
. There might be a number of other classes in that package I'm interested into and I don't want to polute my REPL's global namespace by doing import com.package._
.
Even better, I'd like to define class A without typing its fully qualified name. Something like:
package com.package // do this once
class A
class B
val a = new A()
val b = new B()
I'm aware of the :paste -raw
command, but that would require me to type package com.package
for each block; I'm really looking for a stateful command to change the "current working package", if you will.
scala read-eval-print-loop
scala read-eval-print-loop
asked Aug 16 '14 at 19:30
gsimardgsimard
381422
381422
So, I guess stackoverflow.com/a/18510229/6309 wouldn't be helpful either?
– VonC
Aug 16 '14 at 19:37
1
there is currently no support for that because packages are actually used in the internals of the REPL (classes defined in the REPL don't actually live in the root package), but that would make an interesting feature request...
– gourlaysama
Aug 16 '14 at 19:41
@VonC: No, this would not allow me to define new classes without a fully qualified name, as per my question.
– gsimard
Aug 16 '14 at 19:45
Ditto @gourlaysama The use case is testing existing classes with package-private access.
– som-snytt
Aug 18 '14 at 15:20
Possible duplicate of How to use members with default (package) or private access level in REPL?
– Jacek Laskowski
Oct 14 '15 at 9:26
add a comment |
So, I guess stackoverflow.com/a/18510229/6309 wouldn't be helpful either?
– VonC
Aug 16 '14 at 19:37
1
there is currently no support for that because packages are actually used in the internals of the REPL (classes defined in the REPL don't actually live in the root package), but that would make an interesting feature request...
– gourlaysama
Aug 16 '14 at 19:41
@VonC: No, this would not allow me to define new classes without a fully qualified name, as per my question.
– gsimard
Aug 16 '14 at 19:45
Ditto @gourlaysama The use case is testing existing classes with package-private access.
– som-snytt
Aug 18 '14 at 15:20
Possible duplicate of How to use members with default (package) or private access level in REPL?
– Jacek Laskowski
Oct 14 '15 at 9:26
So, I guess stackoverflow.com/a/18510229/6309 wouldn't be helpful either?
– VonC
Aug 16 '14 at 19:37
So, I guess stackoverflow.com/a/18510229/6309 wouldn't be helpful either?
– VonC
Aug 16 '14 at 19:37
1
1
there is currently no support for that because packages are actually used in the internals of the REPL (classes defined in the REPL don't actually live in the root package), but that would make an interesting feature request...
– gourlaysama
Aug 16 '14 at 19:41
there is currently no support for that because packages are actually used in the internals of the REPL (classes defined in the REPL don't actually live in the root package), but that would make an interesting feature request...
– gourlaysama
Aug 16 '14 at 19:41
@VonC: No, this would not allow me to define new classes without a fully qualified name, as per my question.
– gsimard
Aug 16 '14 at 19:45
@VonC: No, this would not allow me to define new classes without a fully qualified name, as per my question.
– gsimard
Aug 16 '14 at 19:45
Ditto @gourlaysama The use case is testing existing classes with package-private access.
– som-snytt
Aug 18 '14 at 15:20
Ditto @gourlaysama The use case is testing existing classes with package-private access.
– som-snytt
Aug 18 '14 at 15:20
Possible duplicate of How to use members with default (package) or private access level in REPL?
– Jacek Laskowski
Oct 14 '15 at 9:26
Possible duplicate of How to use members with default (package) or private access level in REPL?
– Jacek Laskowski
Oct 14 '15 at 9:26
add a comment |
1 Answer
1
active
oldest
votes
Simply put, you cannot.
Each command in the scala REPL is wrapped into a newly generated package, as explained here.
Also, there was a ticket asking package { }
support in the REPL, but it was dismissed as :paste -raw
was considered enough for the purpose.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f25343217%2fsetting-package-in-scala-repl%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Simply put, you cannot.
Each command in the scala REPL is wrapped into a newly generated package, as explained here.
Also, there was a ticket asking package { }
support in the REPL, but it was dismissed as :paste -raw
was considered enough for the purpose.
add a comment |
Simply put, you cannot.
Each command in the scala REPL is wrapped into a newly generated package, as explained here.
Also, there was a ticket asking package { }
support in the REPL, but it was dismissed as :paste -raw
was considered enough for the purpose.
add a comment |
Simply put, you cannot.
Each command in the scala REPL is wrapped into a newly generated package, as explained here.
Also, there was a ticket asking package { }
support in the REPL, but it was dismissed as :paste -raw
was considered enough for the purpose.
Simply put, you cannot.
Each command in the scala REPL is wrapped into a newly generated package, as explained here.
Also, there was a ticket asking package { }
support in the REPL, but it was dismissed as :paste -raw
was considered enough for the purpose.
edited May 23 '17 at 12:10
Community♦
11
11
answered Aug 16 '14 at 19:45
Gabriele PetronellaGabriele Petronella
92.2k18181213
92.2k18181213
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f25343217%2fsetting-package-in-scala-repl%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
So, I guess stackoverflow.com/a/18510229/6309 wouldn't be helpful either?
– VonC
Aug 16 '14 at 19:37
1
there is currently no support for that because packages are actually used in the internals of the REPL (classes defined in the REPL don't actually live in the root package), but that would make an interesting feature request...
– gourlaysama
Aug 16 '14 at 19:41
@VonC: No, this would not allow me to define new classes without a fully qualified name, as per my question.
– gsimard
Aug 16 '14 at 19:45
Ditto @gourlaysama The use case is testing existing classes with package-private access.
– som-snytt
Aug 18 '14 at 15:20
Possible duplicate of How to use members with default (package) or private access level in REPL?
– Jacek Laskowski
Oct 14 '15 at 9:26