Microsoft Proves Pronouns Patentable

from the that's-just-great dept

theodp writes “Five days after arguing that the Eolas browser plug-in patent should be invalidated as obvious, Microsoft pocketed a patent of its own for Computer programming language pronouns, which covers the use of ellipses, blanks, and ditto marks as substitutes for names in a computer programming language. Perhaps the USPTO was won over by the patent’s eloquent conclusion: ‘Eliminating names is a substantial benefit as programmers dislike creating names.’ “ Sometimes, you have to wonder if folks are just sitting around trying to come up with absolutely ridiculous ideas on what to patent – just to see if they can get away with it.


Rate this comment as insightful
Rate this comment as funny
You have rated this comment as insightful
You have rated this comment as funny
Flag this comment as abusive/trolling/spam
You have flagged this comment
The first word has already been claimed
The last word has already been claimed
Insightful Lightbulb icon Funny Laughing icon Abusive/trolling/spam Flag icon Insightful badge Lightbulb icon Funny badge Laughing icon Comments icon

Comments on “Microsoft Proves Pronouns Patentable”

Subscribe: RSS Leave a comment
6 Comments
mschaef (user link) says:

Re: Pronouns?

Paul Graham wrote about something like this in his book On Lisp: anaphoric macros. Basically, his macros allow the result of the controlling expression of an if…then…else or while loop to be easily accessed within the body of the statement.
Here’s a simple example:

(aif (assoc msg-id *compiler-message-table*)
??(cdr it)
??(error “Compiler message not found!” msg-id))

The statement assoc attempts to find a message in a message table. It returns false if the message wasn’t found and a tuple containing the message if it was found. Now, if it was found, the ‘it’ in the second line of code refers to the result of the assoc, thus avoiding the need to explicitly declare a variable to retain the result. (which, of course, the aif macro does internally)
Given that the technique predates the book, and the book was published in 1993 (http://www.paulgraham.com/onlisp.html), I think that this qualifies as prior art for a fair bit of the patent. It’s either sad that 1) Microsoft’s developers didn’t know about this or 2) Microsoft chose to ignore it, and not include the reference in the patent they chose to file anyway.
(BTW, the Lisp macro to implement anaphoric if is about four lines of code. Not many other languages can make that claim.)

Anonymous Coward says:

Example from the patent text


B) Pronoun processing program 650 can also be implemented as a parser extension of translator 610 using structure-based substitutions. In this case, explicit and anonymous pronouns are handled as a special case by the parser and the resulting parse tree is manipulated appropriately. Parser extensions can implement anonymous pronouns to the extent that a language grammar that includes them can be written unambiguously. Because they lack a semantic understanding of the program, parser extensions remain a form of substitution, but are more powerful than preprocessors. To illustrate, the following example can be implemented with a parser extension, but not with a preprocessor:

area=rectangle[i].width* $( ).height;

For this example, the use of the pronoun “$( )” refers to the previous left-hand side of a “.” operator (i.e., rectangle[i]).

Add Your Comment

Your email address will not be published. Required fields are marked *

Have a Techdirt Account? Sign in now. Want one? Register here

Comment Options:

Make this the or (get credits or sign in to see balance) what's this?

What's this?

Techdirt community members with Techdirt Credits can spotlight a comment as either the "First Word" or "Last Word" on a particular comment thread. Credits can be purchased at the Techdirt Insider Shop »

Follow Techdirt

Techdirt Daily Newsletter

Techdirt Deals
Techdirt Insider Discord
The latest chatter on the Techdirt Insider Discord channel...
Loading...