[jdom-interest] Always been there?

[Steven D. Keens]

I concur ... it is the programmer's job to call flush.

>-----Original Message-----
>From: jdom-interest-admin at jdom.org
>[mailto:jdom-interest-admin at jdom.org]On Behalf Of Joseph Bowbeer
>Sent: Thursday, April 05, 2001 02:12
>To: brett at newInstance.com
>Cc: jdom-interest at jdom.org
>Subject: [jdom-interest] Always been there?
>
>
>Generally, it's the programmer's job to call flush().  Though the Print*
>classes have options for flushing automatically  It's also the programmer's
>job to call writer.close() and that's supposed to flush() first.
>
>
>----- original message -----
>From: Brett McLaughlin
>Date: Thu, 5 Apr 2001 00:14:22 -0500
>
>Anyone know if I'm loony, or has this (what appears to me as a bug) always
>been there:
>
>This code outputs a file of 0 bytes:
>
>        Element root = new Element("properties");
>        Document doc = new Document(root);
>
>        // Output document to supplied filename
>        XMLOutputter outputter = new XMLOutputter("  ", true);
>        outputter.output(doc, writer);
>        /*writer.flush();*/
>
>This code works fine:
>
>        Element root = new Element("properties");
>        Document doc = new Document(root);
>
>        // Output document to supplied filename
>        XMLOutputter outputter = new XMLOutputter("  ", true);
>        outputter.output(doc, writer);
>        writer.flush();
>
>Since when has it been the programmer's job to do a flush() on their own?
>Seems sort of weird... In this case, the Writer wraps an
>OutputStreamWriter,
>but that shouldn't matter, right?
>
>-Brett
>
>
>_______________________________________________
>To control your jdom-interest membership:
>http://lists.denveronline.net/mailman/options/jdom-interest/youradd
r at yourhost.com