Oh, yeah. With my addendum to the blogpost explaining how to handle
legacy code, it's as far as I can tell complete and perfect.

'perfect' in the sense that there aren't any use cases that work
better now in legacy java compared to the proposal, not 'perfect' in
that its no longer up for discussion, or that it is the perfect
complexity/utility tradeoff :)

On Oct 24, 1:08 pm, "Viktor Klang" <[EMAIL PROTECTED]> wrote:
> Reinier,
>
> I think I will need to boil our discussion down to a blogpost of my own as I
> feel that some aspects were left out.
> I actually think some kind of proposal can be formed from our discussions.
>
> Cheers,
> Viktor
>
> On Thu, Oct 23, 2008 at 6:04 PM, Reinier Zwitserloot <[EMAIL PROTECTED]>wrote:
>
>
>
>
>
> > Nope, Fan's null support is incomplete, bordering on broken. At least,
> > if Stephen's blogpost is the extent of Fan's support for nullity.
>
> > I've reduced the extensive thread that Viktor and I have been having
> > about this in another thread here, to a blogpost, and I've mailed
> > Stephen for comments about it. Nullity just isn't this simple, folks.
> > Sorry.
>
> > Read more here:
> >http://www.zwitserloot.com/2008/10/23/non-null-in-static-languages/
>
> > On Oct 23, 10:20 am, BoD <[EMAIL PROTECTED]> wrote:
> > > I remember a few weeks ago there was a discussion here about
> > > not-nullability in Java, how to avoid NPEs, and people were discussing a
> > > way of forbid variables to hold null.
> > > Well it seems that they just did that in the Fan language : seehttp://
> >www.jroller.com/scolebourne/entry/life_in_the_fan_lane
>
> > > BoD
>
> --
> Viktor Klang
> Senior Systems Analyst
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "The 
Java Posse" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to