Re: StackTraceElement question

2012-10-08 Thread Vitaly Davidovich
2 at 10:25 PM, Christos Zoulas >wrote: > > > On Oct 8, 11:07pm, [email protected] (David Holmes) wrote: > > -- Subject: Re: StackTraceElement question > > > > | > There is also the problem of having a class hierarchy like: > > | > > > | > c

Re: StackTraceElement question

2012-10-08 Thread Krystal Mok
On Mon, Oct 8, 2012 at 10:25 PM, Christos Zoulas wrote: > On Oct 8, 11:07pm, [email protected] (David Holmes) wrote: > -- Subject: Re: StackTraceElement question > > | > There is also the problem of having a class hierarchy like: > | > > | > class A extends cl

Re: StackTraceElement question

2012-10-08 Thread Remi Forax
the class should not be serialized. cheers, RĂ©mi On 10/08/2012 03:07 PM, David Holmes wrote: On 8/10/2012 9:48 PM, [email protected] wrote: On Oct 8, 7:33pm, [email protected] (Krystal Mok) wrote: -- Subject: Re: StackTraceElement question |> Can't you just do Class.forName

Re: StackTraceElement question

2012-10-08 Thread Christos Zoulas
On Oct 8, 11:07pm, [email protected] (David Holmes) wrote: -- Subject: Re: StackTraceElement question | > There is also the problem of having a class hierarchy like: | > | > class A extends class I | > class B extends class I | > | > and then trying to figure out if it

Re: StackTraceElement question

2012-10-08 Thread David Holmes
On 8/10/2012 11:07 PM, David Holmes wrote: On 8/10/2012 9:48 PM, [email protected] wrote: On Oct 8, 7:33pm, [email protected] (Krystal Mok) wrote: -- Subject: Re: StackTraceElement question |> Can't you just do Class.forName(getClassName()) and then find the |> encl

Re: StackTraceElement question

2012-10-08 Thread David Holmes
On 8/10/2012 9:48 PM, [email protected] wrote: On Oct 8, 7:33pm, [email protected] (Krystal Mok) wrote: -- Subject: Re: StackTraceElement question |> Can't you just do Class.forName(getClassName()) and then find the |> enclosing class? |> |> There could be poten

Re: StackTraceElement question

2012-10-08 Thread Christos Zoulas
On Oct 8, 7:33pm, [email protected] (Krystal Mok) wrote: -- Subject: Re: StackTraceElement question | > Can't you just do Class.forName(getClassName()) and then find the | > enclosing class? | > | > There could be potential class loader issues to | use Class.forName(getCla

Re: StackTraceElement question

2012-10-08 Thread Krystal Mok
On Mon, Oct 8, 2012 at 7:27 AM, David Holmes wrote: > On Sat, Oct 6, 2012 at 3:04 AM, Christos Zoulas >> wrote: >> >> Hi, >>> >>> I don't know if this belongs to this list, but if it does not, >>> please point me to where it does. I think that it would be nice if >>> StackTraceElement which curr

Re: StackTraceElement question

2012-10-07 Thread David Holmes
On Sat, Oct 6, 2012 at 3:04 AM, Christos Zoulas wrote: Hi, I don't know if this belongs to this list, but if it does not, please point me to where it does. I think that it would be nice if StackTraceElement which currently contains: boolean equals(Object obj) String getClas

Re: StackTraceElement question

2012-10-07 Thread Alan Bateman
On 06/10/2012 15:58, Krystal Mok wrote: : Is there any reason to store the name instead of the Class? Is it possible to fix this in a future version of the jdk? thanks christos I think this would require a bit of analysis as to the issues that might turn up. For example, would it allow access

Re: StackTraceElement question

2012-10-06 Thread Krystal Mok
Hi, I believe this discussion belongs to core-libs-dev list better. cc'd. - Kris On Sat, Oct 6, 2012 at 3:04 AM, Christos Zoulas wrote: > Hi, > > I don't know if this belongs to this list, but if it does not, > please point me to where it does. I think that it would be nice if > StackTraceElem