null and void
adjective
- (idiomatic, law) invalid, cancelled, unenforceable
Since they are both seperately mentioned on contracts and the like, they are probably two different things, but to me they seem the same.
legalese - What's the difference between "null" and "void" in legal language? - English Language & Usage Stack Exchange
android - java.lang.Void vs void vs Null - Stack Overflow
c - What's the difference between a null pointer and a void pointer? - Stack Overflow
Difference in NULL and VOID Data Structure
Videos
I don't remember how I learned this, and I can't find a reference just now, but the peculiar custom of redundancy in our legal documents dates back to medieval England. The Norman conquest of 1066 put a French-speaking king and nobility in charge of an English-speaking people. The English courts at the time were extremely sensitive to detail and would throw out a petition for something as minor as a misspelling, so getting every detail right was crucial. Thus, lawyers developed a habit of incorporating English synonyms for key French words (or it might have been the reverse; memory fails me on that detail). This is how we get phrases like null and void and cease and desist. Since American law (except in the state of Louisiana) is based on English common law, the U.S. inherited this custom. Over time, I suspect the legal professional largely forgot exactly why it was building all this redundancy into its documents and "decided" it was as a general matter of belt-and-suspenders caution.
EDIT: I finally found a reference of sorts at Wikipedia:
David Crystal (2004) explains a stylistic influence upon English legal language. During the Medieval period lawyers used a mixture of Latin, French and English. To avoid ambiguity lawyers often offered pairs of words from different languages. Sometimes there was little ambiguity to resolve and the pairs merely gave greater emphasis, becoming a stylistic habit. This is a feature of legal style that continues to the present day. Examples of mixed language doublets are: "breaking and entering" (English/French), "fit and proper" (English/French), "lands and tenements" (English/French), "will and testament" (English/Latin). Examples of English-only doublets are: "let and hindrance", "have and hold."
Curious to learn more about Ms. Hess' answer, I undertook a little more research* today...
The history begins, as with so many curiosities in the English language, with the Norman invasion in 1066. At that time, English was the language of the ordinary people, and the law. At first, William the Conqueror interfered little with use of English in official documents, primarily to bolster his claim to the throne, as it was before his reign strongly associated with the crown and kingly continuity. As time went on, however, and as more and more Normans gained positions of prominence in the English court, and were elevated to the nobility, French came to be the spoken language of the upper-class, and Latin, the imported written language of the learned, eventually came to completely replace Old English in legal documents. This continued for some 250 odd years.
By 1275, we find the first statutes written in French, and by 1310 French had overtaken Latin as the language of law. Well, not exactly overtaken; important Latin legal terms, terms of art, were being sprinkled in French language, where needed. We have inherited these terms up to the present day; this is where our civil law gets important concepts like mens rea, habeaus corpus, writs of mandamus, and a million other terms. Still, Law French was the language that lawyers communicated with each other in, and lawyers continued to develop their the profession with it, creating ever new terms of art when trying, pleading, and judging cases. Things continued in this way for a 100 more years.
Curiously, just as French was just reaching its supremacy as official written language of the Law, it was dying out as a spoken language among the nobility. Increasingly, they were speaking a bastardized pidgin of English and French called Anglo-Norman, and by 1400, Anglo-Norman had nearly died out even amongst the royal household in favor of English. Henry V broke things off completely with his Norman heritage after famously going to war with France in the Hundreds Years' War. English, with modifications, had now become the language of all the English people.
Well, mostly. Law French was still the obscure, technical language of the legal profession, and it was contributing many terms of art of its own, particularly in property law: this is where property law jargon like estoppel, estate, and esquire come from. However, even the lawyers eventually lost control of a tongue they didn't speak, and legalese became a complex argot of Law Latin and Law French terms swimming in a sea of ordinary English.
A conundrum. By 1362, we have evidence that the courts were becoming recognizant of this troublesome state of affairs, as a Statute of Pleading was enacted "condemning French as 'much unknown in said Realm'" and requiring that "all pleas be 'pleaded, shewed, defended, answered, and debated, and judged in the English tongue.'" Ironically enough, the Statute itself was written in Law French, and it was not till 200 years later, when the vocabulary of Law French had shrunk to about 1000 words, that English became the dominant language of the law.
Still, all those terms of art couldn't be simply abandoned. So lawyers of the day simply did the next best thing: they imported synonyms acknowledged as "English" to accompany those technical terms, to give the "synonyms" independent legal weight in documents, and eventually, the combination of the two became phrases with inertia of their own. Such as:
breaking and entering
fit and proper
will and testament
free and clear
acknowledge and confess
law and order
to have and to hold(English terms are italicized.)
"But Billare!" "Isn't your answer supposed to be talking about null and void?" "And, if I'm not mistaken, doesn't null come from the Latin nullus, meaning 'not any, none,' and doesn't void come from the Latin vocivus, meaning 'unoccupied, vacant'"? "Where's the Old English term there?!"
Ah, yes. The punchline. Null and void became a phrase of their own because the two synonyms from Latin were imported at different times into "ordinary" English. I quote from David Melinkoff's The Language of Law:
Early in the reign of Elizabeth I, null – with a long life as a negative in law French and in Latin – became an English synonym for the law's use of void. Another hundred years, and null and void were a team, null taking the place of other explanatory nothingness (no value, no effect) that had often accompanied void. The combination stuck despite frowns in and out of the law.
So it follows the same rule. Null and void is a semantically redundant phrase because it was formed as a compromised term of art, and has continued in this way for a long, long time.
*: All acknowledgments and quotes go to this most excellent book, Legal Language, by a certain Peter Tiersma, where I found basically most of this research. Do read it if you're interested in more.
The most common use of Void is for reflection, but that is not the only place where it may be used.
void is a keyword that means that a function does not result a value.
java.lang.Void is a reference type, then the following is valid:
Void nil = null;
(so far it is not interesting...)
As a result type (a function with a return value of type Void) it means that the function *always * return null (it cannot return anything other than null, because Void has no instances).
Void function(int a, int b) {
//do something
return null;
}
Why would I like a function that always returns null?
Before the invention of generics, I didn't have an use case for Void.
With generics, there are some interesting cases. For instance, a Future<T> is a holder for the result of an asynchronous operation performed by other thread. Future.get will return the operation value (of type T), and will block until the computation is performed.
But... what if there is nothing to return? Simple: use a Future<Void>. For instance, in Google App Engine the Asyncronous Datastore Service delete operation returns a Future<Void>. When get() is invoked on that future, null is returned after the deletion is complete. One could write a similar example with Callables.
Another use case is a Map without values, i.e. a Map<T,Void>. Such a map behaves like a Set<T>, then it may be useful when there is no equivalent implementation of Set (for instance, there is no WeakHashSet, then one could use a WeakHashMap<T,Void>).
You have an extra comma in your code.
myAsyncTask.execute((Void),null);
//^extra comma right here
Also, there is no need to cast null to Void, because (1) Void has no instances and thus there is no Void object, and (2) casting null to anything is rather useless because null is a valid value for any Object data type.
Code should probably just be:
myAsyncTask.execute(null);
Null pointer is a special reserved value of a pointer. A pointer of any type has such a reserved value. Formally, each specific pointer type (int *, char * etc.) has its own dedicated null-pointer value. Conceptually, when a pointer has that null value it is not pointing anywhere.
Void pointer is a specific pointer type - void * - a pointer that points to some data location in storage, which doesn't have any specific type.
So, once again, null pointer is a value, while void pointer is a type. These concepts are totally different and non-comparable. That essentially means that your question, as stated, is not exactly valid. It is like asking, for example, "What is the difference between a triangle and a car?".
They are two different concepts: "void pointer" is a type (void *). "null pointer" is a pointer that has a value of zero (NULL). Example:
void *pointer = NULL;
That's a NULL void pointer.