- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
Re: hacking the scala source
Tue, 2009-07-21, 10:57
In that case, could I volunteer my services to look at some of the issues with the interpreter on windows? Does anyone have an idea yet what the problem might be?
On Tue, Jul 21, 2009 at 10:55 AM, Kevin Wright <kev.lee.wright@googlemail.com> wrote:
On Tue, Jul 21, 2009 at 10:55 AM, Kevin Wright <kev.lee.wright@googlemail.com> wrote:
See how the interpreter does it...
Not a bad idea, it should already be hitting all the right high-level entry points without getting too far into the guts of the system :)
On Tue, Jul 21, 2009 at 10:53 AM, Dmitriy Shabanov <shabanovd@gmail.com> wrote:
On Tue, 2009-07-21 at 10:36 +0100, Kevin Wright wrote:
> I'm currently exploring the nsc source, trying to get a good
> understanding of how it works and ideally write a plugin or two
> (hopefully commit a few ideas and fixes back to scala core as well)
>
> Problem I've found is that the overview documentation available on
> scala-lang is still a little bit weak... until I've got some momentum
> behind me it's always a nightmare figuring out the best place to start
> tackling a large codebase. Someone needs to work with this stuff, get
> a good high-level overview, and write up their notes and experiences
> to go back on the website, so I'm nominating myself for the role :)
>
> Having said all that, if anybody could give me a few pointers on what
> the important bits are and maybe any risky areas that I should be
> aware of, it would be a great help!
>
>
Hi,
I interesting at scala compile @ interpreter overwriting to get language
dialect. If it possible to start from that point. ;)
I agree to start as nsc plugin. Hopefully, will be able to help and
share experience.
--
Cheers,
Dmitriy Shabanov
Tue, 2009-07-21, 15:17
#2
Re: hacking the scala source
If you want to look at the mvn scala:console target on windows please do so! I've been severely constrained in my ability to look into it.
On Tue, Jul 21, 2009 at 6:16 AM, Kevin Wright <kev.lee.wright@googlemail.com> wrote:
On Tue, Jul 21, 2009 at 6:16 AM, Kevin Wright <kev.lee.wright@googlemail.com> wrote:
Ooops, I was thinking of the maven plugin running scala:console on windows, of course the console itself works fine
*deep blush*
Of course, if there *are* any known issues on windows I can take a look. I'm pretty sure that the -cp argument does odd things when launching the interpreter from the command line (though haven't checked this on trunk yet).
On Tue, Jul 21, 2009 at 10:56 AM, Kevin Wright <kev.lee.wright@googlemail.com> wrote:In that case, could I volunteer my services to look at some of the issues with the interpreter on windows? Does anyone have an idea yet what the problem might be?
On Tue, Jul 21, 2009 at 10:55 AM, Kevin Wright <kev.lee.wright@googlemail.com> wrote:
See how the interpreter does it...
Not a bad idea, it should already be hitting all the right high-level entry points without getting too far into the guts of the system :)
On Tue, Jul 21, 2009 at 10:53 AM, Dmitriy Shabanov <shabanovd@gmail.com> wrote:
On Tue, 2009-07-21 at 10:36 +0100, Kevin Wright wrote:
> I'm currently exploring the nsc source, trying to get a good
> understanding of how it works and ideally write a plugin or two
> (hopefully commit a few ideas and fixes back to scala core as well)
>
> Problem I've found is that the overview documentation available on
> scala-lang is still a little bit weak... until I've got some momentum
> behind me it's always a nightmare figuring out the best place to start
> tackling a large codebase. Someone needs to work with this stuff, get
> a good high-level overview, and write up their notes and experiences
> to go back on the website, so I'm nominating myself for the role :)
>
> Having said all that, if anybody could give me a few pointers on what
> the important bits are and maybe any risky areas that I should be
> aware of, it would be a great help!
>
>
Hi,
I interesting at scala compile @ interpreter overwriting to get language
dialect. If it possible to start from that point. ;)
I agree to start as nsc plugin. Hopefully, will be able to help and
share experience.
--
Cheers,
Dmitriy Shabanov
Tue, 2009-07-21, 16:07
#3
Re: hacking the scala source
Josh,
What do you know about the problem? Are there other-language REPLs
that work from maven?
Ricky.
2009/7/21 Josh Suereth :
> If you want to look at the mvn scala:console target on windows please do
> so! I've been severely constrained in my ability to look into it.
>
> On Tue, Jul 21, 2009 at 6:16 AM, Kevin Wright
> wrote:
>>
>> Ooops, I was thinking of the maven plugin running scala:console on
>> windows, of course the console itself works fine
>> *deep blush*
>>
>> Of course, if there *are* any known issues on windows I can take a look.
>> I'm pretty sure that the -cp argument does odd things when launching the
>> interpreter from the command line (though haven't checked this on trunk
>> yet).
>>
>> On Tue, Jul 21, 2009 at 10:56 AM, Kevin Wright
>> wrote:
>>>
>>> In that case, could I volunteer my services to look at some of the issues
>>> with the interpreter on windows? Does anyone have an idea yet what the
>>> problem might be?
>>>
>>> On Tue, Jul 21, 2009 at 10:55 AM, Kevin Wright
>>> wrote:
>>>>
>>>> See how the interpreter does it...
>>>>
>>>> Not a bad idea, it should already be hitting all the right high-level
>>>> entry points without getting too far into the guts of the system :)
>>>>
>>>> On Tue, Jul 21, 2009 at 10:53 AM, Dmitriy Shabanov
>>>> wrote:
>>>>>
>>>>> On Tue, 2009-07-21 at 10:36 +0100, Kevin Wright wrote:
>>>>> > I'm currently exploring the nsc source, trying to get a good
>>>>> > understanding of how it works and ideally write a plugin or two
>>>>> > (hopefully commit a few ideas and fixes back to scala core as well)
>>>>> >
>>>>> > Problem I've found is that the overview documentation available on
>>>>> > scala-lang is still a little bit weak... until I've got some momentum
>>>>> > behind me it's always a nightmare figuring out the best place to
>>>>> > start
>>>>> > tackling a large codebase. Someone needs to work with this stuff,
>>>>> > get
>>>>> > a good high-level overview, and write up their notes and experiences
>>>>> > to go back on the website, so I'm nominating myself for the role :)
>>>>> >
>>>>> > Having said all that, if anybody could give me a few pointers on what
>>>>> > the important bits are and maybe any risky areas that I should be
>>>>> > aware of, it would be a great help!
>>>>> >
>>>>> >
>>>>>
>>>>> Hi,
>>>>>
>>>>> I interesting at scala compile @ interpreter overwriting to get
>>>>> language
>>>>> dialect. If it possible to start from that point. ;)
>>>>>
>>>>> I agree to start as nsc plugin. Hopefully, will be able to help and
>>>>> share experience.
>>>>>
>>>>> --
>>>>> Cheers,
>>>>>
>>>>> Dmitriy Shabanov
>>>>>
>>>>
>>>
>>
>
>
Tue, 2009-07-21, 16:17
#4
Re: hacking the scala source
Consider it forked :)
On Tue, Jul 21, 2009 at 3:09 PM, Josh Suereth <joshua.suereth@gmail.com> wrote:
On Tue, Jul 21, 2009 at 3:09 PM, Josh Suereth <joshua.suereth@gmail.com> wrote:
If you want to look at the mvn scala:console target on windows please do so! I've been severely constrained in my ability to look into it.
On Tue, Jul 21, 2009 at 6:16 AM, Kevin Wright <kev.lee.wright@googlemail.com> wrote:
Ooops, I was thinking of the maven plugin running scala:console on windows, of course the console itself works fine
*deep blush*
Of course, if there *are* any known issues on windows I can take a look. I'm pretty sure that the -cp argument does odd things when launching the interpreter from the command line (though haven't checked this on trunk yet).
On Tue, Jul 21, 2009 at 10:56 AM, Kevin Wright <kev.lee.wright@googlemail.com> wrote:In that case, could I volunteer my services to look at some of the issues with the interpreter on windows? Does anyone have an idea yet what the problem might be?
On Tue, Jul 21, 2009 at 10:55 AM, Kevin Wright <kev.lee.wright@googlemail.com> wrote:
See how the interpreter does it...
Not a bad idea, it should already be hitting all the right high-level entry points without getting too far into the guts of the system :)
On Tue, Jul 21, 2009 at 10:53 AM, Dmitriy Shabanov <shabanovd@gmail.com> wrote:
On Tue, 2009-07-21 at 10:36 +0100, Kevin Wright wrote:
> I'm currently exploring the nsc source, trying to get a good
> understanding of how it works and ideally write a plugin or two
> (hopefully commit a few ideas and fixes back to scala core as well)
>
> Problem I've found is that the overview documentation available on
> scala-lang is still a little bit weak... until I've got some momentum
> behind me it's always a nightmare figuring out the best place to start
> tackling a large codebase. Someone needs to work with this stuff, get
> a good high-level overview, and write up their notes and experiences
> to go back on the website, so I'm nominating myself for the role :)
>
> Having said all that, if anybody could give me a few pointers on what
> the important bits are and maybe any risky areas that I should be
> aware of, it would be a great help!
>
>
Hi,
I interesting at scala compile @ interpreter overwriting to get language
dialect. If it possible to start from that point. ;)
I agree to start as nsc plugin. Hopefully, will be able to help and
share experience.
--
Cheers,
Dmitriy Shabanov
Tue, 2009-07-21, 17:37
#5
Re: hacking the scala source
I believe it to be related to how Maven handles stdin/stdout.
On Tue, Jul 21, 2009 at 10:57 AM, Ricky Clarkson <ricky.clarkson@gmail.com> wrote:
On Tue, Jul 21, 2009 at 10:57 AM, Ricky Clarkson <ricky.clarkson@gmail.com> wrote:
Josh,
What do you know about the problem? Are there other-language REPLs
that work from maven?
Ricky.
2009/7/21 Josh Suereth <joshua.suereth@gmail.com>:
> If you want to look at the mvn scala:console target on windows please do
> so! I've been severely constrained in my ability to look into it.
>
> On Tue, Jul 21, 2009 at 6:16 AM, Kevin Wright
> <kev.lee.wright@googlemail.com> wrote:
>>
>> Ooops, I was thinking of the maven plugin running scala:console on
>> windows, of course the console itself works fine
>> *deep blush*
>>
>> Of course, if there *are* any known issues on windows I can take a look.
>> I'm pretty sure that the -cp argument does odd things when launching the
>> interpreter from the command line (though haven't checked this on trunk
>> yet).
>>
>> On Tue, Jul 21, 2009 at 10:56 AM, Kevin Wright
>> <kev.lee.wright@googlemail.com> wrote:
>>>
>>> In that case, could I volunteer my services to look at some of the issues
>>> with the interpreter on windows? Does anyone have an idea yet what the
>>> problem might be?
>>>
>>> On Tue, Jul 21, 2009 at 10:55 AM, Kevin Wright
>>> <kev.lee.wright@googlemail.com> wrote:
>>>>
>>>> See how the interpreter does it...
>>>>
>>>> Not a bad idea, it should already be hitting all the right high-level
>>>> entry points without getting too far into the guts of the system :)
>>>>
>>>> On Tue, Jul 21, 2009 at 10:53 AM, Dmitriy Shabanov <shabanovd@gmail.com>
>>>> wrote:
>>>>>
>>>>> On Tue, 2009-07-21 at 10:36 +0100, Kevin Wright wrote:
>>>>> > I'm currently exploring the nsc source, trying to get a good
>>>>> > understanding of how it works and ideally write a plugin or two
>>>>> > (hopefully commit a few ideas and fixes back to scala core as well)
>>>>> >
>>>>> > Problem I've found is that the overview documentation available on
>>>>> > scala-lang is still a little bit weak... until I've got some momentum
>>>>> > behind me it's always a nightmare figuring out the best place to
>>>>> > start
>>>>> > tackling a large codebase. Someone needs to work with this stuff,
>>>>> > get
>>>>> > a good high-level overview, and write up their notes and experiences
>>>>> > to go back on the website, so I'm nominating myself for the role :)
>>>>> >
>>>>> > Having said all that, if anybody could give me a few pointers on what
>>>>> > the important bits are and maybe any risky areas that I should be
>>>>> > aware of, it would be a great help!
>>>>> >
>>>>> >
>>>>>
>>>>> Hi,
>>>>>
>>>>> I interesting at scala compile @ interpreter overwriting to get
>>>>> language
>>>>> dialect. If it possible to start from that point. ;)
>>>>>
>>>>> I agree to start as nsc plugin. Hopefully, will be able to help and
>>>>> share experience.
>>>>>
>>>>> --
>>>>> Cheers,
>>>>>
>>>>> Dmitriy Shabanov
>>>>>
>>>>
>>>
>>
>
>
--
Ricky Clarkson
Java Programmer, AD Holdings
+44 1565 770804
Skype: ricky_clarkson
Google Talk: ricky.clarkson@gmail.com
Tue, 2009-07-21, 21:47
#6
Re: hacking the scala source
Doesn't look like maven, it's something to do with the way the java Process/ProcessBuilder binds piped streams against the forked process.I already tried hacking the plugin to inject a string that didn't come via the console and still got no response.
On Tue, Jul 21, 2009 at 5:34 PM, Josh Suereth <joshua.suereth@gmail.com> wrote:
On Tue, Jul 21, 2009 at 5:34 PM, Josh Suereth <joshua.suereth@gmail.com> wrote:
I believe it to be related to how Maven handles stdin/stdout.
On Tue, Jul 21, 2009 at 10:57 AM, Ricky Clarkson <ricky.clarkson@gmail.com> wrote:
Josh,
What do you know about the problem? Are there other-language REPLs
that work from maven?
Ricky.
2009/7/21 Josh Suereth <joshua.suereth@gmail.com>:
> If you want to look at the mvn scala:console target on windows please do
> so! I've been severely constrained in my ability to look into it.
>
> On Tue, Jul 21, 2009 at 6:16 AM, Kevin Wright
> <kev.lee.wright@googlemail.com> wrote:
>>
>> Ooops, I was thinking of the maven plugin running scala:console on
>> windows, of course the console itself works fine
>> *deep blush*
>>
>> Of course, if there *are* any known issues on windows I can take a look.
>> I'm pretty sure that the -cp argument does odd things when launching the
>> interpreter from the command line (though haven't checked this on trunk
>> yet).
>>
>> On Tue, Jul 21, 2009 at 10:56 AM, Kevin Wright
>> <kev.lee.wright@googlemail.com> wrote:
>>>
>>> In that case, could I volunteer my services to look at some of the issues
>>> with the interpreter on windows? Does anyone have an idea yet what the
>>> problem might be?
>>>
>>> On Tue, Jul 21, 2009 at 10:55 AM, Kevin Wright
>>> <kev.lee.wright@googlemail.com> wrote:
>>>>
>>>> See how the interpreter does it...
>>>>
>>>> Not a bad idea, it should already be hitting all the right high-level
>>>> entry points without getting too far into the guts of the system :)
>>>>
>>>> On Tue, Jul 21, 2009 at 10:53 AM, Dmitriy Shabanov <shabanovd@gmail.com>
>>>> wrote:
>>>>>
>>>>> On Tue, 2009-07-21 at 10:36 +0100, Kevin Wright wrote:
>>>>> > I'm currently exploring the nsc source, trying to get a good
>>>>> > understanding of how it works and ideally write a plugin or two
>>>>> > (hopefully commit a few ideas and fixes back to scala core as well)
>>>>> >
>>>>> > Problem I've found is that the overview documentation available on
>>>>> > scala-lang is still a little bit weak... until I've got some momentum
>>>>> > behind me it's always a nightmare figuring out the best place to
>>>>> > start
>>>>> > tackling a large codebase. Someone needs to work with this stuff,
>>>>> > get
>>>>> > a good high-level overview, and write up their notes and experiences
>>>>> > to go back on the website, so I'm nominating myself for the role :)
>>>>> >
>>>>> > Having said all that, if anybody could give me a few pointers on what
>>>>> > the important bits are and maybe any risky areas that I should be
>>>>> > aware of, it would be a great help!
>>>>> >
>>>>> >
>>>>>
>>>>> Hi,
>>>>>
>>>>> I interesting at scala compile @ interpreter overwriting to get
>>>>> language
>>>>> dialect. If it possible to start from that point. ;)
>>>>>
>>>>> I agree to start as nsc plugin. Hopefully, will be able to help and
>>>>> share experience.
>>>>>
>>>>> --
>>>>> Cheers,
>>>>>
>>>>> Dmitriy Shabanov
>>>>>
>>>>
>>>
>>
>
>
--
Ricky Clarkson
Java Programmer, AD Holdings
+44 1565 770804
Skype: ricky_clarkson
Google Talk: ricky.clarkson@gmail.com
*deep blush*
Of course, if there *are* any known issues on windows I can take a look. I'm pretty sure that the -cp argument does odd things when launching the interpreter from the command line (though haven't checked this on trunk yet).
On Tue, Jul 21, 2009 at 10:56 AM, Kevin Wright <kev.lee.wright@googlemail.com> wrote: