You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Sim IJskes - QCG <si...@qcg.nl> on 2010/12/19 10:47:11 UTC
Re: Space/outrigger suggestions (consolidation)
On 12/19/2010 03:41 AM, Wade Chandler wrote:
>> Just to verify, we are talking about generics for a situation like this are
>> we?
>>
>> public<T extends Entry> T get( T entry )
>> {
>> return (T) new Entry();
>> }
>>
>>
>>
>
> Yes, the other issue Peter is talking about can occur now as we are talking
> about someones Entry implementation where they may use generics in one of their
> fields.
Ok, but the construct of the above has not been discussed until
conclusion. Shall we consolidate this first, and then move on to other
issues?
Gr. Sim
Re: Space/outrigger suggestions (consolidation)
Posted by Sim IJskes - QCG <si...@qcg.nl>.
On 12/19/2010 04:57 PM, Wade Chandler wrote:
>> Ok, but the construct of the above has not been discussed until
>> conclusion. Shall we consolidate this first, and then move on to other
>> issues?
>
>
> I'm not sure what you mean here exactly. I think that is pretty much as
> simplified as possible for that method. Other than that, It believe each method
> in the spaces API needs to have generics applied as well as possible. I think
> sending you a patch is possibly the best way to do that as you mentioned in
> another email unless there is something you believe we need to go over here. I
> just don't completely understand the question; apologies.
It was not aimed at you personally. I thought the issue was an
interesting one, saw the discussion move away and tried to focus it
back, so we could formulate a conclusion. Glad to see you are still on
the subject.
Gr. Sim
Re: Space/outrigger suggestions (consolidation)
Posted by Wade Chandler <hw...@yahoo.com>.
----- Original Message ----
> From: Sim IJskes - QCG <si...@qcg.nl>
> To: river-dev@incubator.apache.org
> Sent: Sun, December 19, 2010 4:47:11 AM
> Subject: Re: Space/outrigger suggestions (consolidation)
>
> On 12/19/2010 03:41 AM, Wade Chandler wrote:
> >> Just to verify, we are talking about generics for a situation like this
>are
> >> we?
> >>
> >> public<T extends Entry> T get( T entry )
> >> {
> >> return (T) new Entry();
> >> }
> >>
> >>
> >>
> >
> > Yes, the other issue Peter is talking about can occur now as we are
talking
> > about someones Entry implementation where they may use generics in one of
>their
> > fields.
>
> Ok, but the construct of the above has not been discussed until
> conclusion. Shall we consolidate this first, and then move on to other
> issues?
I'm not sure what you mean here exactly. I think that is pretty much as
simplified as possible for that method. Other than that, It believe each method
in the spaces API needs to have generics applied as well as possible. I think
sending you a patch is possibly the best way to do that as you mentioned in
another email unless there is something you believe we need to go over here. I
just don't completely understand the question; apologies.
I'll hook up with Jeff, throw something together, and everyone can check it out.
Then I believe we can talk about consensus etc. Considering the conversation and
the different issues, I don't think we'll reach that point until we have some
impl to poke around in.
Thanks,
Wade
==================
Wade Chandler
Software Engineer and Developer
NetBeans Dream Team Member and Contributor
http://wiki.netbeans.org/wiki/view/NetBeansDreamTeam
http://www.netbeans.org