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
Hah! I have been fretting along these lines for days! | 503 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Hah! I have been fretting along these lines for days!
Authored by: Ian Al on Sunday, April 22 2012 @ 08:56 AM EDT
I need to cogitate more about what you tell me, but can I try the following generalisation on you?
The traditional computer language source file is compiled to an intermediate form of machine code and intermediate symbolic references. When all of the linked files are finally processed into an executable and saved in an executable file, of the elf or other format, the instructions for the processor that will be loaded into memory are all in machine code.

With object oriented languages, all of the core objects can be coded into machine code. However, most object oriented systems have that machine code in an interpreter program. At run time, the interpreter evaluates all the objects created by the program and attributes the properties to them on the basis of inheritance and composition.

Some object oriented platforms, like Java, do a partial evaluation and put an intermediate mix of binary (byte) code, and parameter attribution, but leave final parameter attribution to a later stage. This 'partial evaluation' is often referred to as 'compilation' but is more accurately considered a partial interpretation prior to run time. It is a mixture of machine code generation and parameter attribution, The resulting file, the 'class file' in Java, is referred to as an executable.

However, it cannot be executed as native machine code by the processor nor as 'byte code' on a virtual processor in software. It has to run through the final interpreter evaluation stage or have a subsequent 'installation phase' evaluation before running on a native or virtual processor.

This splitting of the phases of processing the program source code is just a more complex way of implementing the 'interfaces'. The 'interface' to the programmer is not functionally changed by this complex implementation and execution process.

---
Regards
Ian Al
Software Patents: It's the disclosed functions in the patent, stupid!

[ Reply to This | Parent | # ]

That is not what a Java Interface(Type) is, or how it works
Authored by: Anonymous on Sunday, April 22 2012 @ 09:36 AM EDT
I detailed this in an earlier post here here

[ 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 )