May the source be with you, but remember the KISS principle ;-)
Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and  bastardization of classic Unix

Dr.Nikolai Bezroukov's Devil's Advocate Commentary on "Thinking in Java" by Bruce Eckel.
Chapter 2

Disclaimer: I would like to stress that the role of devil's advocate is to be critical. At the same time I believe than Java has a bright future and that TIJ can be listed among ten best books on Java. That's why I am writing this Commentary. This Commentary is a work in progress. Currently it is incomplete, buggy, and may contains bad links. All views expressed in the Commentary are my own.

Chapter 2 Everything is Object

The chapter is devoted to explanation of data types in Java and contains the following subsections:

Logically we have two groups of topics: one group is connected with storage allocation, typing and visibility aspects in Java. The second is about programming style and imbedded documentation.

The key questions that should be answered in this chapter are storage allocation and visibility.  Although the author explain basic data types in Java very clearly, the questions of storage allocation and visibility should be explained in more detail.

There essentially three kinds of storage:

In C variables, arrays and structures can be static, automatic or heap-based. In Java the objects are always allocated on from the heap and keyword static is very misleading -- it's not about static storage it's about the number of allocations on heap. If member of a class is declared static, it means that that data allocated ones and the same memory is accessible from any instance of the class.

It's unclear from the text of the book how Java allocates simple (non object) variable -- in procedure stack or not.

The very important advantage of keeping as much as possible in heap is that exception handing and multithreading became much more simplified.  One should understand that in deeply nested exception, execution of catch statement can involve correct exit from all called procedures in the procedure stack. 

Java object variables are much like object pointers in C/C++.

Chapter 2 contain among other things a good overview of visibility (page 80) and static attribute. Static attribute in Java is not the same static as in Fortran, PL/1, C and other traditional languages. The memory is allocated from the heap on the first new operation -– the first instance of the object. As such it is subject to garbage collection. But at the same time all other instances use this already allocated storage. So it is kinf of common storage area for all instances of the class and in this sense probably can be better called common.

Java programming style

Chapter 2 also explain the elements of  programming style and creation of embedded documentation. Introduction to Javadoc is good and well placed, but coding style section is very superficial.

The main complain about Javadoc section is absence of references to literate programming movement.   Javadoc is a simplistic implementation of the idea of literate programming by D.Knuth. So the idea is more than 10 years old and looks somewhat archaic. Probably much better ( but more radical) and effective implementation of the same idea would be to use HTML as the standard representation of Java programs. Here Java designers were (unfortunately) very conservative and decided to stick to ASCII :-(.   I provided some information about literate programming movement (which was most popular in 1989-1994) in the link section of the Commentary.  Hope it would be useful. BTW the simplest platform for literary programming now seems to be MS Word 97 or other word processor with a powerful scripting language and ability to generate both HTML and plain text.

As for coding style I object to using a single operator after if, while, for, etc. IMHO there should always be a curvy braces, so that modification of the program became easier. 

Programs are somewhat easier to maintain if they have a consistent style, but its important not to go to far. Religious zeal here is definitely harmful, but a good pretty printer would be definitely beneficial.  As TIJ does not provide style guidelines for Java I will provide my own borrowed mainly from Programming in Java Style Guide

Useful links

Programming in Java Style Guide  -- this is short and nononcence guide that should be read and following. the content partially reproducred above


Literate programming movement

It's interesting to note than like famous Moliere's character Bruce Eckel practiced kind of literary programming in writing TIJ without knowing how it is called :-).



Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy


War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes


Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law


Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

Copyright © 1996-2021 by Softpanorama Society. was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to to buy a cup of coffee for authors of this site


The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019