Stuart Ash

Ranch Hand
+ Follow
since Oct 07, 2005
Merit badge: grant badges
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Stuart Ash

A null-pointing String reference when asked to cough up its String value with the + op, returns the literal 'null'. When any method is invoked though, there has to be a valid object to the ref.

Originally posted by marc weber:
The code you've posted has:

  • One misplaced brace.
  • One missing brace.
  • One extra parenthesis.
  • A misspelled class name (twice).
  • A call to a method that doesn't exist.

  • And NOT posted in the code block.

    Originally posted by Arun Kumarr:

    I would split it as paras(may be parasites shortened) - kave (may be from kava, a alcoholic drink) - deka(10) - tria 3) - phobia(fear). How do I decipher it,

    Is it fear of Drinking kava becuase 13 parasites will attack you?

    Okay Ash, what the hell is, paraskavedekatriaphobes?

    [ April 15, 2007: Message edited by: Arun Kumarr ]

    I thought the context made it clear?
    17 years ago

    Originally posted by marc weber:

    Well, that's easier to explain than the studded leather underwear. Oh, wait... Those are dry clean only.

    17 years ago

    Originally posted by Ilja Preuss:
    There is no string primitive.

    You might confuse it with String literals, which are objects, too.


    System.out.println("I'm an Object!".length());

    Hey, I didn't mean there was one! But the autoboxing feature seems to give a certain transparency to the use of primitives and their wrappers, it's as though something like that already existing with strings.
    17 years ago
    So how many of you are paraskavedekatriaphobes??
    17 years ago
    After reading the discussion about autoboxing in this thread, I got to thinking that what the Javagods have come up with as autoboxing can be considered to have kind-of existed even earlier, with the String class.

    Here is the "alternate theory":

    is essentially a wrapper class for a primitive type called string.


    This perspective might help people trying to grapple with the intricacies of autoboxing (such as the one discussed in that thread) in light of known existing behavior - that of String.

    17 years ago
    Most of the developers said so!

    You can look for arguments on the web about the developer community's reaction to the introduction of generics into Java.

    Sorry no time to look up some links for you, but when there's google there is ...
    That seems to be a good way of doing it. I hope I don't find it too tedious to spawn another thread in an adjacent forum and the forum software we use makes it quite easy (lazy me )

    This is a general programming concept. Most simply:

    A compile-time error is a problem found at compile time.

    A runtime error is anything that goes wrong at runtime -- in Java, runtime errors are usually indicated/communicated via exceptions (Throwable and family).

    Originally posted by Chandra Bhatt:
    Why do you people hate my question posted above?, No reply yet!!!


    Try replacing oranges with mangoes, you might get someone to answer
    Overriding is an object-oriented feature and is connected with class families and polymorphism. Static members are theoretically outside the bounds of pure OO. Read up on this and you will see light!
    What makes you think this shouldnt work? That might help us find an answer.