decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Hmmm. | 314 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Hmmm.
Authored by: PJ on Saturday, May 05 2012 @ 09:54 AM EDT
I don't know, but I don't get the impression the judge is so inclined, because if he was, he wouldn't need to dig so deep, unless he's just a very, very careful guy.

Meanwhile, I see a TechDirt article about the case, and the article shows one of the slides, the one showing rangeCheck. A comment caught my eye:

David Muir (profile), Apr 17th, 2012 @ 8:04pm

Those code snippets sure look a heck of a lot like the IBM VisualAge C++ library code for exception handling from several years before Java came out with theirs. Okay, the EXACT code would not have existed, but the variable and function names were almost identical... and in those snippets there's not much else that COULD be different. And I bet IBM derived theirs from something else too. Copyright in software code is a very tenuous concept. Dare I say "totally bogus concept"

[ Reply to This | Parent | # ]

  • Hmmm. - Authored by: BJ on Saturday, May 05 2012 @ 02:07 PM EDT
It's not hard to understand, look up a few posts
Authored by: Anonymous on Saturday, May 05 2012 @ 09:55 AM EDT

Some people like to 'puff' themselves up with a comprehensive knowledge and
understanding of arcane subject matters.

It is not at all complicated.
It is not at all hard to understand.

It is a concept.



[ Reply to This | Parent | # ]

Hmmm.
Authored by: Anonymous on Saturday, May 05 2012 @ 11:05 AM EDT
I've got 40 years of background in IT, fully understand
API's, inheritance, etc. With all the back and forth in
these posts even I am lost.

I think what would be helpful is if someone put up a diagram
(flowchart) of how inheritance works/doesn't work.

Sometimes a picture is worth a thousand words. I don't have
a java background or I would do this.

wjarvis

[ Reply to This | Parent | # ]

Hmmm.
Authored by: BitOBear on Sunday, May 06 2012 @ 07:09 PM EDT
No, they really aren't that hard and you don't need math or that much computer
science to understand.

What you need is a complete absence of lawyers with agendas embedded in the
information that they are trying to convey.

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )