On Mon, 2020-05-11 at 02:28 -0400, javadesigner wrote: > empty is not the same as null in java. this is a java specific > discussion btw. >
Vraimente.
java.util.Map map = con.getTypeMap();
So, the variable "map" is now an empty map object.
No, it wasn’t (its since been modified in between your two posts - you should skim the whole thread). Feel free to read the source code if you don’t believe the OP.
Highly likely it contains hex zeroes. It could contain the string "empty" but that does not sound reasonable
This would be the English idiom “speaking out of one’s a**” :)
Maybe there is no memory address and memory is only allocated with the first "put".
System.out.println("map:"+map);
So, println accesses the memory occupied by the object and assuming it contains unprintable hex zeroes, it can either display "null", or convert to printable zeroes or ignore it and display nothing.
What output did you expect from "System.out.println("map:"+map);"?? That is the question.
Create an empty HashMap in Java and then print it out - that’s what we expected. Not “null” which only prints if the variable being printed is null.
David J.
David,
Apparently you were correct. Throwing a notImplemented exception would be better as this whole discussion is moot until being able to actually do something with the typemap is implemented.
