Internet °ü·Ã ÀÚ·á

HomePage Backward Forward Post Reply List
Delete Modify
  Á¦¸ñ   [JAVA] JDC Tech Tips No. 12 1998/07/24 (08:16)
À̸§ ±èÈ¿¿ø
¹øÈ£ 19
Á¶È¸ 639
º»¹® Subject:
         JDC Tech Tips No. 12
    Date:
         Wed, 22 Jul 1998 05:42:47 GMT
    From:
         JDCTechTips@sun.com
Reply-To:
         JDCTechTips@javasoft.com
      To:
         JDCTechTips@sun.com




-WELCOME- to the Java(sm) Developer Connection(sm) Tech Tips.  This issue
covers stream tokenizing and division by zero.  The JDC Team-


            J  D  C    T E  C  H   T  I  P  S
            
            TIPS, TECHNIQUES, AND SAMPLE CODE
                 *  Stream Tokenizing
                 *  Division by Zero


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
T I P S ,  T E C H N I Q U E S ,  A N D  S A M P L E  C O D E

STREAM TOKENIZING.  In JDC Tech Tips No.  11, an example of string
tokenization was presented, using the class java.util.StringTokenizer.

To access the JDC Tech Tips No. 11, use the following address:

http://developer.javasoft.com/developer/technicalArticles/TechTips/


There's also another way to do tokenization, using
java.io.StreamTokenizer.  StreamTokenizer operates on input streams rather
than strings, and each byte in the input stream is regarded as a character
in the range '\u0000' through '\u00FF'.

StreamTokenizer is lower level than StringTokenizer, but offers more
control over the tokenization process.  The class uses an internal table to
control how tokens are parsed, and this syntax table can be modified to
change the parsing rules.  Here's an example of how StreamTokenizer works:

       import java.io.*;
       import java.util.*;
       
       public class streamtoken {
               public static void main(String args[])
               {
                       if (args.length == 0) {
                               System.err.println("missing input filename");
                               System.exit(1);
                       }
       
                       Hashtable wordlist = new Hashtable();
       
                       try {
                               FileReader fr = new FileReader(args[0]);
                               BufferedReader br = new BufferedReader(fr);
       
                               StreamTokenizer st = new StreamTokenizer(br);
                               //StreamTokenizer st =
                               //    new StreamTokenizer(new StringReader(
                               //    "this is a test"));
                               st.resetSyntax();
                               st.wordChars('A', 'Z');
                               st.wordChars('a', 'z');
                               int type;
                               Object dummy = new Object();
                               while ((type = st.nextToken()) !=
                                   StreamTokenizer.TT_EOF) {
                                       if (type == StreamTokenizer.TT_WORD)
                                               wordlist.put(st.sval, dummy);
                               }
                               br.close();
                       }
                       catch (IOException e) {
                               System.err.println(e);
                       }
       
                       Enumeration enum = wordlist.keys();
                       while (enum.hasMoreElements())
                               System.out.println(enum.nextElement());
               }
       }

In this example, a StreamTokenizer is created on top of a FileReader /
BufferedReader pair that represents a text file. Note that a
StreamTokenizer can also be made to read from a String by using
StringReader as illustrated in the commented-out code shown above
(StringBufferInputStream also works, although this class has been
deprecated).

The method resetSyntax is used to clear the internal syntax table, so that
StreamTokenizer forgets any rules that it knows about parsing tokens.  Then
wordChars is used to declare that only upper and lower case letters should
be considered to form words.  That is, the only tokens that StreamTokenizer
recognizes are sequences of upper and lower case letters.

nextToken is called repeatedly to retrieve words, and each resulting
word is found in the public instance variable "st.sval". The words are
inserted into a Hashtable, and at the end of processing the contents of
the table are displayed, using an Enumeration as illustrated in JDC Tech
Tips No. 11. So the action of this program is to find all the
unique words in a text file and display them.

StreamTokenizer also has special facilities for parsing numbers,
quoted strings, and comments. It's a useful alternative to
StringTokenizer, and is especially applicable if you are tokenizing
input streams, or wish to exercise finer control over the tokenization
process.

DIVISION BY ZERO.  Suppose you have a Java language program in which the
following expression appears:

       1.0 / 0.0

What happens?  Does this usage cause an exception to be thrown?  Is the
result undefined?

In the Java programming language, integral division by zero results in an
ArithmeticException.  But for floating-point, no exception is thrown (in
C++ the result of division by zero is undefined).  The result of 1.0 / 0.0
is positive infinity, indicated by the constant Double.POSITIVE_INFINITY
(which, in fact, is defined by performing this division).

This example illustrates an important point, which is that Java language
floating-point arithmetic operates according to a well-defined standard,
known as IEEE 754.

Another related idea is that of NaN (not a number), used to represent the
results of certain arithmetic operations such as the following:

       0.0 / 0.0

There is also a "Double.NaN" constant defined, which is analogous to the
constant Double.POSITIVE_INFINITY.  NaN is interesting in that it has the
following property:

       NaN != NaN

In other words, NaN is unequal to itself, and this fact is used to
implement methods such as Double.isNaN.

To tie down these ideas a little better, here is an example that uses
negative infinity, positive infinity, and NaN:

       public class number {
               public static void main(String args[])
               {
                       long neg_inf_bits =
                           Double.doubleToLongBits(-1.0 / 0.0);
                       long pos_inf_bits =
                           Double.doubleToLongBits(1.0 / 0.0);
                       long nan_bits =
                           Double.doubleToLongBits(0.0 / 0.0);
       
                       System.out.println(Long.toHexString(neg_inf_bits));
                       System.out.println(Long.toHexString(pos_inf_bits));
                       System.out.println(Long.toHexString(nan_bits));
               }
       }

The output of the program is the following:

       fff0000000000000
       7ff0000000000000
       7ff8000000000000

These numbers are the hexadecimal 64-bit values that represent negative
infinity, positive infinity, and NaN respectively.  In other words,
particular bit patterns for a double value indicate specific special values
such as NaN.

Finally, knowing how floating-point arithmetic behaves is quite important
in particular applications, and the Java language specification goes to
some lengths to tie down behavior in this area.


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-- NOTE --

The names on the JDC mailing list are used for internal Sun
Microsystems(tm) purposes only.  To remove your name from the list, see
SUBSCRIBE/UNSUBSCRIBE below.

-- FEEDBACK --

Comments? Send your feedback on the JDC Tech Tips to:

JDCTechTips@Sun.com

-- SUBSCRIBE/UNSUBSCRIBE --

This mailing is sent to you because you elected to receive JDC Email when
you registered as a JDC member.  To unsubscribe from JDC Email, go to the
following address and enter the email address you wish to remove from the
mailing list:

http://developer.java.sun.com/unsubscribe.html

-- ARCHIVES --

You'll find the JDC Tech Tips archives at:

http://developer.javasoft.com/developer/javaInDepth/TechTips/index.html

-- COPYRIGHT --

Copyright 1998 Sun Microsystems, Inc. All rights reserved.
901 San Antonio Road, Palo Alto, California 94303 USA.

This document is protected by copyright.  For more information, see:

http://developer.javasoft.com/developer/copyright.html

The JDC Tech Tips are written by Glen McCluskey.

JDC Tech Tips No. 12
July 21, 1998

HomePage Backward Forward Post Reply List
1998 by swindler