sherry cuenco

+ Follow
since May 07, 2003
Merit badge: grant badges
For More
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 sherry cuenco

Originally posted by Mohit Goyal:
K&B pg 355
the fig for step 3 shud show the object with the value "def" on the heap
although no object is reffering to it.

String s = "abc";
String s2 = s;
s = s.concat("def");

I agree with Mohit. It seems "def" is missing on the Fig6-1 (as well as "Rules" missing on Fig6-2,Fig6-3) since it is also another String object created.
[ December 02, 2003: Message edited by: sherry cuenco ]
Constructors are not inherited but...
if the super constructors are automatically invoked by the system, everytime a new instance of a class is created, it's like saying the super constructors are "inherited" by the constructor.

Invoked super constructor A
Invoked super constructor B
Invoked super constructor C

So, the way I view it, the super constructors of the constructor are "inherited" by the constructor because they are automatically invoked by the system everytime an instance is created.
Please correct me on this. Thanks!
20 years ago

Woohoo Just passed OOP-4 Lookup
Onto the servlets it is then....

Congrats on bagging another moose
20 years ago
Thanks Marilyn and Pauline.

So if you're doing your java or javac from C:myStuff\javaStuff it will look for classes in C:myStuff\javaStuff (along with any other places listed in the classpath).

Let's say C:\myStuff\javaStuff is in the classpath.
If I create new subfolders and store my classes there:
I was expecting the compiler would automatically detect the classes stored in these new subfolders. Since it did not, I had to add them individually in my classpath. I thought maybe adding a '.' would do the trick
20 years ago

Originally posted by John Hembree:
I think Pauline hit it right on the head.

You definitely need the ;.; in your classpath.

Why is ;.; needed in the classpath? Is there any significance where it is positioned?
[ September 07, 2003: Message edited by: sherry cuenco ]
20 years ago
Congratulations! Enjoy your OOPs.
20 years ago
Thanks everyone. That was one kind of a ride.
Wait till I see the next
20 years ago
20 years ago
Congrats to both of you!
20 years ago
Iterfaces are implicitly abstract. In your example, you're declaring an interface inside a class.
Static modifier can be applied to instance variables and methods. These variables and methods belong to the class and not the instance of the class. So, if that class (with static members in it), is instantiated many many times, the static variable is shared by all the instances. They share only one copy.
Static modifier when applied to interface? Interface methods cannot be static, only public and abstract. Interface variables are declared public, static and final.
Hope this helps
[ August 07, 2003: Message edited by: sherry cuenco ]
20 years ago
Sometimes, it is appropriate to catch exceptions occured within a method and there are also situations where it is better not to catch the exception and let a method further up the call stack handle it. In this case, the throws clause is the choice for the job.
You'll have to make a special order at National Bookstore. Fill up their special order form and they'll give you a quotation.
I think there are three objects created.
1 "Hi everyone"
2 "3" // Java converts int 3 to a String
3 "Hi everyone3"