Re: Classpath vs. .

According to Horstmann and Cornell (Core Java, 8th ed, p 161):

  The javac compiler always looks for files in the current directory, b=

  java virtual machine launcher only looks into the curetn directory if=

  directory is on the class path. [...] Buf if you have set the class p=

  forgot to include the "." directory, your programs will compile witho=

  error, but they won't run.

This isn't my experience.

  $ ls junk
  one.java two.java

  $ cat junk/one.java
  package junk;

  class one {
    void f() { two t = new two(); }
    }

  $ cat junk/two.java
  package junk;

  class two { }

  $ javac junk/one.java

  $

This is expected; the junk package directory is in the current directory.=

  $ rm junk/*class

  $ javac -classpath /tmp junk/one.java
  junk/one.java:4: cannot find symbol
  symbol : class two
  location: class junk.one
    void f() { two t = new two(); }
               ^
  junk/one.java:4: cannot find symbol
  symbol : class two
  location: class junk.one
    void f() { two t = new two(); }
                           ^
  2 errors

  $

I don't see how this can be interpreted as javac searching the current
directory. In particular

  $ javac -classpath /tmp:. junk/one.java

  $

The page Setting the class path
(http://java.sun.com/javase/6/docs/technotes/tools/solaris/classpath.html=

  Setting the CLASSPATH variable or using the -classpath command-line o=

  overrides that default, so if you want to include the current directo=

  the search path, you must include "." in the new settings.

but I can't find an exemption for javac.

The 8th ed. errata has nothing listed for the entry quoted above. What=

explanation for this divergence in behaviors?