On Sep 8, 6:57 am, SpikyOrange wrote:
> get over that. For me it is as confusing and dangerous as when someone
> uses an if statement in Java without curly braces. I mean, c'mon, it's
> only a couple of braces ("it's only a return statement..."), but the
> danger of maintaining that code incorrec
I'm not sure what you mean. There are no annotations in JavaFX. The
language tries to prevent you from doing bad things, like nulling a
boolean. Preventing errors beforehand is one of the core philosophies
of JavaFX Script.
- Josh
On Sep 8, 2009, at 7:04 PM, Casper Bang wrote:
>
> Take al
Hi Tor,
> I posted a comment on the blog, but I don't see it there so I may have
> done something wrong.
Many thanks for your comments, I've added a link back to this forum
post for now - it might have been intermitted because someone else
managed to post a comment.
> 1. The return type of a fu
Um, unless I'm mistaken, there are no annotations in JavaFX.
Unless its undocumented, in the (as yet incomplete after nearly 12
months) language reference.
http://openjfx.java.sun.com/current-build/doc/reference/JavaFXReference.html
On Sep 9, 12:04 pm, Casper Bang wrote:
> Take all paths simul
Take all paths simultaneously, a la the qubit? ;) No for language
constructs that obviously wouldn't make sense which is why in C#
you'll get a compile error unless you cast bool? to bool. If that cast
is done on a bool? set to null, you'd get what amounts to a
ClassCastException in Java.
I wonder
while nullable booleans make sense when you are talking about data
storage I don't think they make sense in one of your general purpose
programming constructs. For example, if boolean could be null, what
does the following code mean?
var b:Boolean = null;
var t:Boolean = false;
if(b) {
Sneaky abuse of labels, eh?
I've had crazier ideas. Big problem with that is that you can use any
given label only once in any given method. That's a pretty big
negative to that plan.
Parser hack to allow annotating lone code blocks is probably the
easiest way out of the dilemma. It's not a big
Have you checked out Scala? They have several variations of Null,
null, nil, Nothing, None and perhaps more that I am unaware of. And in
C# there's language support for the notion of a Nullable, basically
automatic wrapper classes in the form of something like:
struct Nullable{
public bool ha
If anyone is interested - I've added a blog for week 3.
http://spikyorange.blogspot.com/
If anyone from the JavaPosse feels that it's in appropriate to post to
this group, I'll refrain from doing so - just let me know! So far it
has provided some interesting conversations so I would like to inv
These were great posts - thanks guys.
It's interesting that you mention databases in relation to nulls,
because this is where I've historically had to deal with null Booleans
and suchlike. Usually it's as you describe - the entries are nullable
and therefore I need to do something different in t
On Mon, Sep 7, 2009 at 1:08 PM, Fabrizio
Giudici wrote:
>
> I was looking at the @Synchronized annotation of Lombok - I've already
> said many times that I like the annotation way to enhance the language,
> so that's good. There's only an obvious problem, that we can't annotate
> a inner block of
In browsing the Java section at Barnes and Nobel I noticed some JavaFX
titles.
If anyone has read any of these and would care to post a mini-review/
recommendation, I'd be appreciative.
--RogerV
On Sep 6, 12:49 am, Rob Wilson wrote:
> If anyone is interested, I have posted my first impressions
There's _no_ guaranteed right answer for language evolution. The
meritocracy can get it wrong, and one can make mistakes in creating
the selection criterion for what 'merit' implies (such as listening
solely to loudmouths - though in practice some of the folks
complaining have been playing around
Boolean is really just an Enum that can be True and False isn't it?
I'm guessing a modern day version of Java would've implemented them as
such. Then it would be no problem representing a tri-state, quad-state
or whatever.
The problem with null is that we end up with so much testing which
obscures
Clumsy finger sent last e-mail too soon.
To finish my last sentence
I can see that maybe one need @Nullable Boolean to tell the JavaFX
compiler that this should not be a simple "boolean", but I cannot see
discarding a built in way of denoting true/false/null in one data item.
Jess Holle wr
I've always found the whole endless debate over "null" treatment that
I've seen here and elsewhere odd.
In databases most everything is nullable unless explicitly stated
otherwise -- and there's good reason for this. There are really good
use cases for true/false/null tri-state data -- and sim
It's also important to point out that the compiler rejects null for a
Boolean because null simply isn't a valid value for a boolean (in the
abstract mathematical sense of 'boolean'). Booleans can be true or
false. That's it. The compiler rejects anything else. The same for
Numbers. The co
Jan,
It is forth issue. We started as only Polish newsletter. All done by
volunteers supported by partners (who give us some money for hosting,
graphics and other stuff that we can't do by ourselves). The content
in this issue is written by only Polish authors, but I have got
already 2 articles f
I have to read it first to judge about the content, but I have to say it all
looks very well done !
I was looking for an English Java magazine some time ago. Who knows... I'll
certainly have a look. :-)
On Mon, Sep 7, 2009 at 14:29, Grzegorz Duda wrote:
>
> As always link is missing :)
>
> In ca
The monthly "Java News Brief" of Ociweb.com is excellent.
http://ociweb.com/jnb
On Tue, Sep 8, 2009 at 10:54, Derek Munneke wrote:
>
> Grzegorz Duda wrote:
> > Are you missing newsletters about Java as I did?
> >
> I appreciate this effort, but there must be some other Java newsletters
> other r
Grzegorz Duda wrote:
> Are you missing newsletters about Java as I did?
>
I appreciate this effort, but there must be some other Java newsletters
other read also.
Here are a few that hit my mail box that have a newsletter style:
1. Java Developer's Journal: http://java.sys-con.com/
2. T
Why is Java written in all caps? It is not an acronym, so shouldn't it
be correctly written as "Java"?
On Sep 7, 1:29 pm, Grzegorz Duda wrote:
> As always link is missing :)
>
> In case some of you want to check it out:http://javaexpress.pl/
>
> Regards,
> Grzegorz Duda
--~--~-~--~~-
22 matches
Mail list logo
