intellij idea wins - fatality

On Wed, Nov 23, 2011 at 4:10 PM, HamsterofDeath <h-star@gmx.de> wrote:

http://blog.jetbrains.com/scala/2011/11/14/evaluate-expression-feature-for-scala/

tried the same in eclipse just to be sure i don't bash it based on false
assumptions, but trying to evaluate "List(1,2,3,4)" in eclipse gives me
some error about anonymous class 1 not found, so i guess idea just won.

usually i just advertise idea when someone asks for the best ide around,
but in this case i'll make an exception :)

Sbt does a pretty good job of that too, no gui required.

sbt> eval List(1,2,3,4)
[info] ans: List[Int] = List(1, 2, 3, 4)
 

sbt can debug?

Am 23.11.2011 22:27, schrieb Doug Tangren:

CAJ2WPXh_N8wx8nevGzpBssgLQKR4oph_o8S7S3vbSnMRo+OPxA [at] mail [dot] gmail [dot] com" type="cite">


On Wed, Nov 23, 2011 at 4:10 PM, HamsterofDeath <h-star [at] gmx [dot] de" rel="nofollow">h-star@gmx.de> wrote:

http://blog.jetbrains.com/scala/2011/11/14/evaluate-expression-feature-for-scala/

tried the same in eclipse just to be sure i don't bash it based on false
assumptions, but trying to evaluate "List(1,2,3,4)" in eclipse gives me
some error about anonymous class 1 not found, so i guess idea just won.

usually i just advertise idea when someone asks for the best ide around,
but in this case i'll make an exception :)

Sbt does a pretty good job of that too, no gui required.

sbt> eval List(1,2,3,4)
[info] ans: List[Int] = List(1, 2, 3, 4)
 

On Wed, Nov 23, 2011 at 10:35 PM, HamsterofDeath <h-star@gmx.de> wrote:

sbt can debug?

I debug using SBT all the time
 

Am 23.11.2011 22:27, schrieb Doug Tangren:

On Wed, Nov 23, 2011 at 4:10 PM, HamsterofDeath <h-star@gmx.de> wrote:

http://blog.jetbrains.com/scala/2011/11/14/evaluate-expression-feature-for-scala/

tried the same in eclipse just to be sure i don't bash it based on false
assumptions, but trying to evaluate "List(1,2,3,4)" in eclipse gives me
some error about anonymous class 1 not found, so i guess idea just won.

usually i just advertise idea when someone asks for the best ide around,
but in this case i'll make an exception :)

Sbt does a pretty good job of that too, no gui required.

sbt> eval List(1,2,3,4)
[info] ans: List[Int] = List(1, 2, 3, 4)
 

--
Viktor Klang

Akka Tech LeadTypesafe - Enterprise-Grade Scala from the Experts

Twitter: @viktorklang

How do you debug using sbt (I am not a user myself)? By dropping into
a console with your project included (similar to mvn scala:console)?
I use a continuous compilation maven window to catch compiler errors.
I would like to start dropping into the REPL for debugging (currently
printlns or Eclipse).

Peace. Michael

2011/11/23 √iktor Ҡlang :
>
>
> On Wed, Nov 23, 2011 at 10:35 PM, HamsterofDeath wrote:
>>
>> sbt can debug?
>>
>
> I debug using SBT all the time
>
>>
>> Am 23.11.2011 22:27, schrieb Doug Tangren:
>>
>>
>> On Wed, Nov 23, 2011 at 4:10 PM, HamsterofDeath wrote:
>>>
>>>
>>> http://blog.jetbrains.com/scala/2011/11/14/evaluate-expression-feature-f...
>>>
>>> tried the same in eclipse just to be sure i don't bash it based on false
>>> assumptions, but trying to evaluate "List(1,2,3,4)" in eclipse gives me
>>> some error about anonymous class 1 not found, so i guess idea just won.
>>>
>>> usually i just advertise idea when someone asks for the best ide around,
>>> but in this case i'll make an exception :)
>>
>> Sbt does a pretty good job of that too, no gui required.
>>
>> sbt> eval List(1,2,3,4)
>> [info] ans: List[Int] = List(1, 2, 3, 4)
>>
>>
>
>
>
> --
> Viktor Klang
>
> Akka Tech Lead
> Typesafe - Enterprise-Grade Scala from the Experts
>
> Twitter: @viktorklang
>

2011/11/23 Michael Schmitz <michael@schmitztech.com>

How do you debug using sbt (I am not a user myself)?  By dropping into
a console with your project included (similar to mvn scala:console)?
I use a continuous compilation maven window to catch compiler errors.
I would like to start dropping into the REPL for debugging (currently
printlns or Eclipse).

I switch logging to DEBUG and then do: test-only my.buggything.test

Cheers,
√
 

Peace.  Michael


2011/11/23 √iktor Ҡlang <viktor.klang@gmail.com>:
>
>
> On Wed, Nov 23, 2011 at 10:35 PM, HamsterofDeath <h-star@gmx.de> wrote:
>>
>> sbt can debug?
>>
>
> I debug using SBT all the time
>
>>
>> Am 23.11.2011 22:27, schrieb Doug Tangren:
>>
>>
>> On Wed, Nov 23, 2011 at 4:10 PM, HamsterofDeath <h-star@gmx.de> wrote:
>>>
>>>
>>> http://blog.jetbrains.com/scala/2011/11/14/evaluate-expression-feature-for-scala/
>>>
>>> tried the same in eclipse just to be sure i don't bash it based on false
>>> assumptions, but trying to evaluate "List(1,2,3,4)" in eclipse gives me
>>> some error about anonymous class 1 not found, so i guess idea just won.
>>>
>>> usually i just advertise idea when someone asks for the best ide around,
>>> but in this case i'll make an exception :)
>>
>> Sbt does a pretty good job of that too, no gui required.
>>
>> sbt> eval List(1,2,3,4)
>> [info] ans: List[Int] = List(1, 2, 3, 4)
>>
>>
>
>
>
> --
> Viktor Klang
>
> Akka Tech Lead
> Typesafe - Enterprise-Grade Scala from the Experts
>
> Twitter: @viktorklang
>

--
Viktor Klang

Akka Tech LeadTypesafe - Enterprise-Grade Scala from the Experts

Twitter: @viktorklang

I have and sbt script that opens a debugging port and I attach to it from eclipse.   It's pretty amazing and survives recompiles.

On Nov 23, 2011 6:03 PM, "√iktor Ҡlang" <viktor.klang@gmail.com> wrote:

2011/11/23 Michael Schmitz <michael@schmitztech.com>

How do you debug using sbt (I am not a user myself)?  By dropping into
a console with your project included (similar to mvn scala:console)?
I use a continuous compilation maven window to catch compiler errors.
I would like to start dropping into the REPL for debugging (currently
printlns or Eclipse).

I switch logging to DEBUG and then do: test-only my.buggything.test

Cheers,
√
 

Peace.  Michael


2011/11/23 √iktor Ҡlang <viktor.klang@gmail.com>:
>
>
> On Wed, Nov 23, 2011 at 10:35 PM, HamsterofDeath <h-star@gmx.de> wrote:
>>
>> sbt can debug?
>>
>
> I debug using SBT all the time
>
>>
>> Am 23.11.2011 22:27, schrieb Doug Tangren:
>>
>>
>> On Wed, Nov 23, 2011 at 4:10 PM, HamsterofDeath <h-star@gmx.de> wrote:
>>>
>>>
>>> http://blog.jetbrains.com/scala/2011/11/14/evaluate-expression-feature-for-scala/
>>>
>>> tried the same in eclipse just to be sure i don't bash it based on false
>>> assumptions, but trying to evaluate "List(1,2,3,4)" in eclipse gives me
>>> some error about anonymous class 1 not found, so i guess idea just won.
>>>
>>> usually i just advertise idea when someone asks for the best ide around,
>>> but in this case i'll make an exception :)
>>
>> Sbt does a pretty good job of that too, no gui required.
>>
>> sbt> eval List(1,2,3,4)
>> [info] ans: List[Int] = List(1, 2, 3, 4)
>>
>>
>
>
>
> --
> Viktor Klang
>
> Akka Tech Lead
> Typesafe - Enterprise-Grade Scala from the Experts
>
> Twitter: @viktorklang
>

--
Viktor Klang

Akka Tech LeadTypesafe - Enterprise-Grade Scala from the Experts

Twitter: @viktorklang

2011/11/23 Josh Suereth <joshua.suereth@gmail.com>

I have and sbt script that opens a debugging port and I attach to it from eclipse.   It's pretty amazing and survives recompiles.

That is impressive. 
I was just joking gui's by the way guys. I doesn't matter what you use to write code so long as you enjoy writing code.
Happy Holidays friends.
- d

by debugging i meant:

1. set a breakpoint
2. vm stops there
3. look at variables and fields inside the debugger (how does that work without a gui?)
4. evaluate some expression in this context - which is the whole point of my first email
5. see the problem
6. fix it
7. happy happy joy joy


Am 24.11.2011 00:03, schrieb √iktor Ҡlang:

CANPzfU9UkDGua1p+niKc1kOkiGa_2pF0A_ouiA-41PgPaHWNew [at] mail [dot] gmail [dot] com" type="cite">

2011/11/23 Michael Schmitz <michael [at] schmitztech [dot] com" rel="nofollow">michael@schmitztech.com>

How do you debug using sbt (I am not a user myself)?  By dropping into
a console with your project included (similar to mvn scala:console)?
I use a continuous compilation maven window to catch compiler errors.
I would like to start dropping into the REPL for debugging (currently
printlns or Eclipse).

I switch logging to DEBUG and then do: test-only my.buggything.test

Cheers,
√
 

Peace.  Michael


2011/11/23 √iktor Ҡlang <viktor [dot] klang [at] gmail [dot] com" rel="nofollow">viktor.klang@gmail.com>:
>
>
> On Wed, Nov 23, 2011 at 10:35 PM, HamsterofDeath <h-star [at] gmx [dot] de" rel="nofollow">h-star@gmx.de> wrote:
>>
>> sbt can debug?
>>
>
> I debug using SBT all the time
>
>>
>> Am 23.11.2011 22:27, schrieb Doug Tangren:
>>
>>
>> On Wed, Nov 23, 2011 at 4:10 PM, HamsterofDeath <h-star [at] gmx [dot] de" rel="nofollow">h-star@gmx.de> wrote:
>>>
>>>
>>> http://blog.jetbrains.com/scala/2011/11/14/evaluate-expression-feature-for-scala/
>>>
>>> tried the same in eclipse just to be sure i don't bash it based on false
>>> assumptions, but trying to evaluate "List(1,2,3,4)" in eclipse gives me
>>> some error about anonymous class 1 not found, so i guess idea just won.
>>>
>>> usually i just advertise idea when someone asks for the best ide around,
>>> but in this case i'll make an exception :)
>>
>> Sbt does a pretty good job of that too, no gui required.
>>
>> sbt> eval List(1,2,3,4)
>> [info] ans: List[Int] = List(1, 2, 3, 4)
>>
>>
>
>
>
> --
> Viktor Klang
>
> Akka Tech Lead
> Typesafe - Enterprise-Grade Scala from the Experts
>
> Twitter: @viktorklang
>

--
Viktor Klang

Akka Tech Lead Typesafe - Enterprise-Grade Scala from the Experts

Twitter: @viktorklang

On Nov 24, 2011 7:12 AM, "HamsterofDeath" <h-star@gmx.de> wrote:
>
> by debugging i meant:
>
> 1. set a breakpoint
> 2. vm stops there
> 3. look at variables and fields inside the debugger (how does that work without a gui?)
> 4. evaluate some expression in this context - which is the whole point of my first email
> 5. see the problem
> 6. fix it
> 7. happy happy joy joy

I haven't done that since I was programming C back in 1998

>
>
> Am 24.11.2011 00:03, schrieb √iktor Ҡlang:
>>
>>
>>
>> 2011/11/23 Michael Schmitz <michael@schmitztech.com>
>>>
>>> How do you debug using sbt (I am not a user myself)?  By dropping into
>>> a console with your project included (similar to mvn scala:console)?
>>> I use a continuous compilation maven window to catch compiler errors.
>>> I would like to start dropping into the REPL for debugging (currently
>>> printlns or Eclipse).
>>
>>
>> I switch logging to DEBUG and then do: test-only my.buggything.test
>>
>> Cheers,
>> √
>>  
>>>
>>>
>>> Peace.  Michael
>>>
>>>
>>> 2011/11/23 √iktor Ҡlang <viktor.klang@gmail.com>:
>>> >
>>> >
>>> > On Wed, Nov 23, 2011 at 10:35 PM, HamsterofDeath <h-star@gmx.de> wrote:
>>> >>
>>> >> sbt can debug?
>>> >>
>>> >
>>> > I debug using SBT all the time
>>> >
>>> >>
>>> >> Am 23.11.2011 22:27, schrieb Doug Tangren:
>>> >>
>>> >>
>>> >> On Wed, Nov 23, 2011 at 4:10 PM, HamsterofDeath <h-star@gmx.de> wrote:
>>> >>>
>>> >>>
>>> >>> http://blog.jetbrains.com/scala/2011/11/14/evaluate-expression-feature-for-scala/
>>> >>>
>>> >>> tried the same in eclipse just to be sure i don't bash it based on false
>>> >>> assumptions, but trying to evaluate "List(1,2,3,4)" in eclipse gives me
>>> >>> some error about anonymous class 1 not found, so i guess idea just won.
>>> >>>
>>> >>> usually i just advertise idea when someone asks for the best ide around,
>>> >>> but in this case i'll make an exception :)
>>> >>
>>> >> Sbt does a pretty good job of that too, no gui required.
>>> >>
>>> >> sbt> eval List(1,2,3,4)
>>> >> [info] ans: List[Int] = List(1, 2, 3, 4)
>>> >>
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Viktor Klang
>>> >
>>> > Akka Tech Lead
>>> > Typesafe - Enterprise-Grade Scala from the Experts
>>> >
>>> > Twitter: @viktorklang
>>> >
>>
>>
>>
>>
>> --
>> Viktor Klang
>>
>> Akka Tech Lead
>> Typesafe - Enterprise-Grade Scala from the Experts
>>
>> Twitter: @viktorklang
>>
>

Eclipse can monitor and stop at the breakpoint when sbt debuging.
But I can not look at the variables.

how can you do that? is all your code covered by tests since 1998? lucky guy...

-------- Original-Nachricht --------
> Datum: Thu, 24 Nov 2011 08:20:06 +0100
> Von: "√iktor Ҡlang"
> An: HamsterofDeath
> CC: Michael Schmitz , scala-user@googlegroups.com
> Betreff: Re: [scala-user] intellij idea wins - fatality

> On Nov 24, 2011 7:12 AM, "HamsterofDeath" wrote:
> >
> > by debugging i meant:
> >
> > 1. set a breakpoint
> > 2. vm stops there
> > 3. look at variables and fields inside the debugger (how does that work
> without a gui?)
> > 4. evaluate some expression in this context - which is the whole point
> of
> my first email
> > 5. see the problem
> > 6. fix it
> > 7. happy happy joy joy
>
> I haven't done that since I was programming C back in 1998
>
> >
> >
> > Am 24.11.2011 00:03, schrieb √iktor Ҡlang:
> >>
> >>
> >>
> >> 2011/11/23 Michael Schmitz
> >>>
> >>> How do you debug using sbt (I am not a user myself)? By dropping into
> >>> a console with your project included (similar to mvn scala:console)?
> >>> I use a continuous compilation maven window to catch compiler errors.
> >>> I would like to start dropping into the REPL for debugging (currently
> >>> printlns or Eclipse).
> >>
> >>
> >> I switch logging to DEBUG and then do: test-only my.buggything.test
> >>
> >> Cheers,
> >> √
> >>
> >>>
> >>>
> >>> Peace. Michael
> >>>
> >>>
> >>> 2011/11/23 √iktor Ҡlang :
> >>> >
> >>> >
> >>> > On Wed, Nov 23, 2011 at 10:35 PM, HamsterofDeath
> wrote:
> >>> >>
> >>> >> sbt can debug?
> >>> >>
> >>> >
> >>> > I debug using SBT all the time
> >>> >
> >>> >>
> >>> >> Am 23.11.2011 22:27, schrieb Doug Tangren:
> >>> >>
> >>> >>
> >>> >> On Wed, Nov 23, 2011 at 4:10 PM, HamsterofDeath
> wrote:
> >>> >>>
> >>> >>>
> >>> >>>
> http://blog.jetbrains.com/scala/2011/11/14/evaluate-expression-feature-f...
> >>> >>>
> >>> >>> tried the same in eclipse just to be sure i don't bash it based on
> false
> >>> >>> assumptions, but trying to evaluate "List(1,2,3,4)" in eclipse
> gives me
> >>> >>> some error about anonymous class 1 not found, so i guess idea just
> won.
> >>> >>>
> >>> >>> usually i just advertise idea when someone asks for the best ide
> around,
> >>> >>> but in this case i'll make an exception :)
> >>> >>
> >>> >> Sbt does a pretty good job of that too, no gui required.
> >>> >>
> >>> >> sbt> eval List(1,2,3,4)
> >>> >> [info] ans: List[Int] = List(1, 2, 3, 4)
> >>> >>
> >>> >>
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Viktor Klang
> >>> >
> >>> > Akka Tech Lead
> >>> > Typesafe - Enterprise-Grade Scala from the Experts
> >>> >
> >>> > Twitter: @viktorklang
> >>> >
> >>
> >>
> >>
> >>
> >> --
> >> Viktor Klang
> >>
> >> Akka Tech Lead
> >> Typesafe - Enterprise-Grade Scala from the Experts
> >>
> >> Twitter: @viktorklang
> >>
> >

On Thu, Nov 24, 2011 at 9:44 AM, Dennis Haupt <h-star@gmx.de> wrote:

how can you do that?

I have good debug logging, and add extra verbose debug output at times. And use the typesystem and read the code.

is all your code covered by tests since 1998?

You mean that 100% test coverage somewhat proves your program correct and cannot ever fail at runtime?
 

lucky guy...

I'm fairly certain it's not luck ;)
 

-------- Original-Nachricht --------
> Datum: Thu, 24 Nov 2011 08:20:06 +0100
> Von: "√iktor Ҡlang" <viktor.klang@gmail.com>
> An: HamsterofDeath <h-star@gmx.de>
> CC: Michael Schmitz <michael@schmitztech.com>, scala-user@googlegroups.com
> Betreff: Re: [scala-user] intellij idea wins - fatality

> On Nov 24, 2011 7:12 AM, "HamsterofDeath" <h-star@gmx.de> wrote:
> >
> > by debugging i meant:
> >
> > 1. set a breakpoint
> > 2. vm stops there
> > 3. look at variables and fields inside the debugger (how does that work
> without a gui?)
> > 4. evaluate some expression in this context - which is the whole point
> of
> my first email
> > 5. see the problem
> > 6. fix it
> > 7. happy happy joy joy
>
> I haven't done that since I was programming C back in 1998
>
> >
> >
> > Am 24.11.2011 00:03, schrieb √iktor Ҡlang:
> >>
> >>
> >>
> >> 2011/11/23 Michael Schmitz <michael@schmitztech.com>
> >>>
> >>> How do you debug using sbt (I am not a user myself)?  By dropping into
> >>> a console with your project included (similar to mvn scala:console)?
> >>> I use a continuous compilation maven window to catch compiler errors.
> >>> I would like to start dropping into the REPL for debugging (currently
> >>> printlns or Eclipse).
> >>
> >>
> >> I switch logging to DEBUG and then do: test-only my.buggything.test
> >>
> >> Cheers,
> >> √
> >>
> >>>
> >>>
> >>> Peace.  Michael
> >>>
> >>>
> >>> 2011/11/23 √iktor Ҡlang <viktor.klang@gmail.com>:
> >>> >
> >>> >
> >>> > On Wed, Nov 23, 2011 at 10:35 PM, HamsterofDeath <h-star@gmx.de>
> wrote:
> >>> >>
> >>> >> sbt can debug?
> >>> >>
> >>> >
> >>> > I debug using SBT all the time
> >>> >
> >>> >>
> >>> >> Am 23.11.2011 22:27, schrieb Doug Tangren:
> >>> >>
> >>> >>
> >>> >> On Wed, Nov 23, 2011 at 4:10 PM, HamsterofDeath <h-star@gmx.de>
> wrote:
> >>> >>>
> >>> >>>
> >>> >>>
> http://blog.jetbrains.com/scala/2011/11/14/evaluate-expression-feature-for-scala/
> >>> >>>
> >>> >>> tried the same in eclipse just to be sure i don't bash it based on
> false
> >>> >>> assumptions, but trying to evaluate "List(1,2,3,4)" in eclipse
> gives me
> >>> >>> some error about anonymous class 1 not found, so i guess idea just
> won.
> >>> >>>
> >>> >>> usually i just advertise idea when someone asks for the best ide
> around,
> >>> >>> but in this case i'll make an exception :)
> >>> >>
> >>> >> Sbt does a pretty good job of that too, no gui required.
> >>> >>
> >>> >> sbt> eval List(1,2,3,4)
> >>> >> [info] ans: List[Int] = List(1, 2, 3, 4)
> >>> >>
> >>> >>
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Viktor Klang
> >>> >
> >>> > Akka Tech Lead
> >>> > Typesafe - Enterprise-Grade Scala from the Experts
> >>> >
> >>> > Twitter: @viktorklang
> >>> >
> >>
> >>
> >>
> >>
> >> --
> >> Viktor Klang
> >>
> >> Akka Tech Lead
> >> Typesafe - Enterprise-Grade Scala from the Experts
> >>
> >> Twitter: @viktorklang
> >>
> >

--
Viktor Klang

Akka Tech LeadTypesafe - Enterprise-Grade Scala from the Experts

Twitter: @viktorklang

On 24/11/2011 09:44, Dennis Haupt wrote:
> how can you do that? is all your code covered by tests since 1998? lucky guy...

And not working on a 10 years behemoth legacy code with 1 % test coverage, nearly
untestable except by mocking nearly the whole stack... :-)

On 24/11/2011 08:07, Xuefeng Wu wrote:

> Eclipse can monitor and stop at the breakpoint when sbt debuging.
> But I can not look at the variables.

Works fine in Netbeans + the Scala plugin. Even when the Scala code is
running inside a servlet container.

Debugging a small test is the most effective way to find bugs. (when no threading is involved)

High test coverage does not necessary indicate high code quality. But it does make the code resilient to changes over time.

Do I correctly understand your message that do not care about test coverage at all ?

-
Andrey


On Thursday, November 24, 2011 9:55:27 AM UTC+1, √iktor Klang wrote:

On Thu, Nov 24, 2011 at 9:44 AM, Dennis Haupt <h-s...@gmx.de> wrote:

how can you do that?

I have good debug logging, and add extra verbose debug output at times. And use the typesystem and read the code.

is all your code covered by tests since 1998?

You mean that 100% test coverage somewhat proves your program correct and cannot ever fail at runtime?
 

lucky guy...

I'm fairly certain it's not luck ;)
 

It's certainly a must have and already useful feature, but it's not
yet mature enough.
Besides the limitations listed in the blog post, there are quite a few
bugs
E.g. List(1,2) gives me List(1,2) = No such instance method:
'myclass.List' , "apply" method sometimes does not work.

Thanks, Oleg.

On Nov 24, 12:26 pm, Alan Burlison wrote:
> On 24/11/2011 08:07, Xuefeng Wu wrote:
>
> > Eclipse can monitor and stop at the breakpoint when sbt debuging.
> > But I can not look at the variables.
>
> Works fine in Netbeans + the Scala plugin.  Even when the Scala code is
> running inside a servlet container.
>
> --
> Alan Burlison
> --

On Thu, Nov 24, 2011 at 1:41 PM, Andrey Somov <trophybase@googlemail.com> wrote:

Debugging a small test is the most effective way to find bugs. (when no threading is involved)

Seems like a wonderful world. I usually have around 50 threads.
 

High test coverage does not necessary indicate high code quality. But it does make the code resilient to changes over time.

Do I correctly understand your message that do not care about test coverage at all ?

No, you completely misunderstood me. I definitely care about test coverage. I however care 0 about breakpoints.
 

-
Andrey


On Thursday, November 24, 2011 9:55:27 AM UTC+1, √iktor Klang wrote:

On Thu, Nov 24, 2011 at 9:44 AM, Dennis Haupt <h-s...@gmx.de> wrote:

how can you do that?

I have good debug logging, and add extra verbose debug output at times. And use the typesystem and read the code.

is all your code covered by tests since 1998?

You mean that 100% test coverage somewhat proves your program correct and cannot ever fail at runtime?
 

lucky guy...

I'm fairly certain it's not luck ;)
 

--
Viktor Klang

Akka Tech LeadTypesafe - Enterprise-Grade Scala from the Experts

Twitter: @viktorklang

works perfectly for me (i'm using the nightly builds of the plugin, they are surprisingly stable)

-------- Original-Nachricht --------
> Datum: Thu, 24 Nov 2011 04:47:13 -0800 (PST)
> Von: OlegYch
> An: scala-user
> Betreff: [scala-user] Re: intellij idea wins - fatality

> It's certainly a must have and already useful feature, but it's not
> yet mature enough.
> Besides the limitations listed in the blog post, there are quite a few
> bugs
> E.g. List(1,2) gives me List(1,2) = No such instance method:
> 'myclass.List' , "apply" method sometimes does not work.
>
> Thanks, Oleg.
>
> On Nov 24, 12:26 pm, Alan Burlison wrote:
> > On 24/11/2011 08:07, Xuefeng Wu wrote:
> >
> > > Eclipse can monitor and stop at the breakpoint when sbt debuging.
> > > But I can not look at the variables.
> >
> > Works fine in Netbeans + the Scala plugin.  Even when the Scala code is
> > running inside a servlet container.
> >
> > --
> > Alan Burlison
> > --

Hm.
I also use the nightlies (build 196 for instance).
Will try to come up with a reproducible bug report later.
Anyway "perfectly" is not the right word considering known limitations.
Just trying to not overexcite anyone...

Thanks, Oleg.

On Thu, 24 Nov 2011 16:16:54 +0300, Dennis Haupt wrote:

> works perfectly for me (i'm using the nightly builds of the plugin, they
> are surprisingly stable)
>
> -------- Original-Nachricht --------
>> Datum: Thu, 24 Nov 2011 04:47:13 -0800 (PST)
>> Von: OlegYch
>> An: scala-user
>> Betreff: [scala-user] Re: intellij idea wins - fatality
>
>> It's certainly a must have and already useful feature, but it's not
>> yet mature enough.
>> Besides the limitations listed in the blog post, there are quite a few
>> bugs
>> E.g. List(1,2) gives me List(1,2) = No such instance method:
>> 'myclass.List' , "apply" method sometimes does not work.
>>
>> Thanks, Oleg.
>>
>> On Nov 24, 12:26 pm, Alan Burlison wrote:
>> > On 24/11/2011 08:07, Xuefeng Wu wrote:
>> >
>> > > Eclipse can monitor and stop at the breakpoint when sbt debuging.
>> > > But I can not look at the variables.
>> >
>> > Works fine in Netbeans + the Scala plugin. Even when the Scala code
>> is
>> > running inside a servlet container.
>> >
>> > --
>> > Alan Burlison
>> > --

-------- Original-Nachricht --------
> Datum: Thu, 24 Nov 2011 14:03:41 +0100
> Von: "√iktor Ҡlang"
> An: scala-user@googlegroups.com
> Betreff: Re: [scala-user] intellij idea wins - fatality

> On Thu, Nov 24, 2011 at 1:41 PM, Andrey Somov
> wrote:
>
> > Debugging a small test is the most effective way to find bugs. (when no
> > threading is involved)
> >
>
> Seems like a wonderful world. I usually have around 50 threads.
>

we are living in mirror worlds of each other then. i have 1, in bad cases 2 threads - but about 5% test coverage and almost no logging. debugging code is the only powerful tool i have.

>
> >
> > High test coverage does not necessary indicate high code quality. But it
> > does make the code resilient to changes over time.
> >
> > Do I correctly understand your message that do not care about test
> > coverage at all ?
> >
>
> No, you completely misunderstood me. I definitely care about test
> coverage.
> I however care 0 about breakpoints.
>
>
> >
> > -
> > Andrey
> >
> >
> > On Thursday, November 24, 2011 9:55:27 AM UTC+1, √iktor Klang wrote:
> >
> >>
> >>
> >> On Thu, Nov 24, 2011 at 9:44 AM, Dennis Haupt wrote:
> >>
> >>> how can you do that?
> >>
> >>
> >> I have good debug logging, and add extra verbose debug output at times.
> >> And use the typesystem and read the code.
> >>
> >> is all your code covered by tests since 1998?
> >>
> >>
> >> You mean that 100% test coverage somewhat proves your program correct
> and
> >> cannot ever fail at runtime?
> >>
> >>
> >>> lucky guy...
> >>>
> >>
> >> I'm fairly certain it's not luck ;)
> >>
> >>
> >>
>
>

There's less and less people doing it that way, what, pampered by the latest Java IDE and all... One tends to forget that only good logging and critical thinking will save your a$$ in production...
With scala, hooking up a REPL session and inspecting state should help as well, if you can reproduce the problem I guess...

Thanks,Razvan
On 2011-11-24, at 3:55 AM, √iktor Ҡlang <viktor.klang@gmail.com> wrote:

On Thu, Nov 24, 2011 at 9:44 AM, Dennis Haupt <h-star@gmx.de> wrote:

how can you do that?

I have good debug logging, and add extra verbose debug output at times. And use the typesystem and read the code.

is all your code covered by tests since 1998?

You mean that 100% test coverage somewhat proves your program correct and cannot ever fail at runtime?
 

lucky guy...

I'm fairly certain it's not luck ;)
 

-------- Original-Nachricht --------
> Datum: Thu, 24 Nov 2011 08:20:06 +0100
> Von: "√iktor Ҡlang" <viktor.klang@gmail.com>
> An: HamsterofDeath <h-star@gmx.de>
> CC: Michael Schmitz <michael@schmitztech.com>, scala-user@googlegroups.com
> Betreff: Re: [scala-user] intellij idea wins - fatality

> On Nov 24, 2011 7:12 AM, "HamsterofDeath" <h-star@gmx.de> wrote:
> >
> > by debugging i meant:
> >
> > 1. set a breakpoint
> > 2. vm stops there
> > 3. look at variables and fields inside the debugger (how does that work
> without a gui?)
> > 4. evaluate some expression in this context - which is the whole point
> of
> my first email
> > 5. see the problem
> > 6. fix it
> > 7. happy happy joy joy
>
> I haven't done that since I was programming C back in 1998
>
> >
> >
> > Am 24.11.2011 00:03, schrieb √iktor Ҡlang:
> >>
> >>
> >>
> >> 2011/11/23 Michael Schmitz <michael@schmitztech.com>
> >>>
> >>> How do you debug using sbt (I am not a user myself)?  By dropping into
> >>> a console with your project included (similar to mvn scala:console)?
> >>> I use a continuous compilation maven window to catch compiler errors.
> >>> I would like to start dropping into the REPL for debugging (currently
> >>> printlns or Eclipse).
> >>
> >>
> >> I switch logging to DEBUG and then do: test-only my.buggything.test
> >>
> >> Cheers,
> >> √
> >>
> >>>
> >>>
> >>> Peace.  Michael
> >>>
> >>>
> >>> 2011/11/23 √iktor Ҡlang <viktor.klang@gmail.com>:
> >>> >
> >>> >
> >>> > On Wed, Nov 23, 2011 at 10:35 PM, HamsterofDeath <h-star@gmx.de>
> wrote:
> >>> >>
> >>> >> sbt can debug?
> >>> >>
> >>> >
> >>> > I debug using SBT all the time
> >>> >
> >>> >>
> >>> >> Am 23.11.2011 22:27, schrieb Doug Tangren:
> >>> >>
> >>> >>
> >>> >> On Wed, Nov 23, 2011 at 4:10 PM, HamsterofDeath <h-star@gmx.de>
> wrote:
> >>> >>>
> >>> >>>
> >>> >>>
> http://blog.jetbrains.com/scala/2011/11/14/evaluate-expression-feature-for-scala/
> >>> >>>
> >>> >>> tried the same in eclipse just to be sure i don't bash it based on
> false
> >>> >>> assumptions, but trying to evaluate "List(1,2,3,4)" in eclipse
> gives me
> >>> >>> some error about anonymous class 1 not found, so i guess idea just
> won.
> >>> >>>
> >>> >>> usually i just advertise idea when someone asks for the best ide
> around,
> >>> >>> but in this case i'll make an exception :)
> >>> >>
> >>> >> Sbt does a pretty good job of that too, no gui required.
> >>> >>
> >>> >> sbt> eval List(1,2,3,4)
> >>> >> [info] ans: List[Int] = List(1, 2, 3, 4)
> >>> >>
> >>> >>
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Viktor Klang
> >>> >
> >>> > Akka Tech Lead
> >>> > Typesafe - Enterprise-Grade Scala from the Experts
> >>> >
> >>> > Twitter: @viktorklang
> >>> >
> >>
> >>
> >>
> >>
> >> --
> >> Viktor Klang
> >>
> >> Akka Tech Lead
> >> Typesafe - Enterprise-Grade Scala from the Experts
> >>
> >> Twitter: @viktorklang
> >>
> >

--
Viktor Klang

Akka Tech LeadTypesafe - Enterprise-Grade Scala from the Experts

Twitter: @viktorklang

the given example works perfectly for me, not the complete feature ;)

-------- Original-Nachricht --------
> Datum: Thu, 24 Nov 2011 16:23:22 +0300
> Von: "Oleg Aleshko"
> An: scala-user@googlegroups.com, "Dennis Haupt"
> Betreff: Re: [scala-user] Re: intellij idea wins - fatality

> Hm.
> I also use the nightlies (build 196 for instance).
> Will try to come up with a reproducible bug report later.
> Anyway "perfectly" is not the right word considering known limitations.
> Just trying to not overexcite anyone...
>
> Thanks, Oleg.
>
> On Thu, 24 Nov 2011 16:16:54 +0300, Dennis Haupt wrote:
>
> > works perfectly for me (i'm using the nightly builds of the plugin, they
>
> > are surprisingly stable)
> >
> > -------- Original-Nachricht --------
> >> Datum: Thu, 24 Nov 2011 04:47:13 -0800 (PST)
> >> Von: OlegYch
> >> An: scala-user
> >> Betreff: [scala-user] Re: intellij idea wins - fatality
> >
> >> It's certainly a must have and already useful feature, but it's not
> >> yet mature enough.
> >> Besides the limitations listed in the blog post, there are quite a few
> >> bugs
> >> E.g. List(1,2) gives me List(1,2) = No such instance method:
> >> 'myclass.List' , "apply" method sometimes does not work.
> >>
> >> Thanks, Oleg.
> >>
> >> On Nov 24, 12:26 pm, Alan Burlison wrote:
> >> > On 24/11/2011 08:07, Xuefeng Wu wrote:
> >> >
> >> > > Eclipse can monitor and stop at the breakpoint when sbt debuging.
> >> > > But I can not look at the variables.
> >> >
> >> > Works fine in Netbeans + the Scala plugin. Even when the Scala code
> >> is
> >> > running inside a servlet container.
> >> >
> >> > --
> >> > Alan Burlison
> >> > --

On 24/11/2011 14:20, Dennis Haupt wrote:
> we are living in mirror worlds of each other then. i have 1, in bad cases 2 threads - but about 5% test coverage and almost no logging. debugging code is the only powerful tool i have.

I am in the same wold than you...
Now, some logs or even temporary System.out.println() can go a long way to debug some
threading issues, some GUI problems (particularly in the (re)paint section) or in complex
workflows...
Both approaches have their merits.

On 24/11/2011 07:12, HamsterofDeath wrote:
> by debugging i meant:
>
> 1. set a breakpoint
> 2. vm stops there
> 3. look at variables and fields inside the debugger (how does that work without a gui?)

There are some command line debuggers, particularly in the GCC world...
I used these a bit, a long time ago, but I definitely prefer GUIs.

> 4. evaluate some expression in this context - which is the whole point of my first email
> 5. see the problem
> 6. fix it
> 7. happy happy joy joy

Good point.
Debugging multi-threaded code is a pain however you do it so any kind of help that means you spend lesstime debugging is good.
I personally feel the MT debugging pain when working with a web app and having 8 separate threads halt on breakpoints. Bit of a pain...
2011/11/24 √iktor Ҡlang <viktor.klang@gmail.com>

On Thu, Nov 24, 2011 at 1:41 PM, Andrey Somov <trophybase@googlemail.com> wrote:

Debugging a small test is the most effective way to find bugs. (when no threading is involved)

Seems like a wonderful world. I usually have around 50 threads.
 

High test coverage does not necessary indicate high code quality. But it does make the code resilient to changes over time.

Do I correctly understand your message that do not care about test coverage at all ?

No, you completely misunderstood me. I definitely care about test coverage. I however care 0 about breakpoints.
 

-
Andrey


On Thursday, November 24, 2011 9:55:27 AM UTC+1, √iktor Klang wrote:

On Thu, Nov 24, 2011 at 9:44 AM, Dennis Haupt <h-s...@gmx.de> wrote:

how can you do that?

I have good debug logging, and add extra verbose debug output at times. And use the typesystem and read the code.

is all your code covered by tests since 1998?

You mean that 100% test coverage somewhat proves your program correct and cannot ever fail at runtime?
 

lucky guy...

I'm fairly certain it's not luck ;)
 

--
Viktor Klang

Akka Tech LeadTypesafe - Enterprise-Grade Scala from the Experts

Twitter: @viktorklang