Rational Developer for Power Systems Software

Class CLWriter

  extended by com.ibm.etools.iseries.remotebuild.CLWriter

public class CLWriter
extends Object

Writes commands and strings to another writer. Splits them using CL continuation rules. Adds line numbers and date modified fields if requested in the constructor.

Field Summary
static String Copyright
Constructor Summary
CLWriter(Writer writer)
          Constructor for CLWriter.
CLWriter(Writer writer, int dataLength, boolean hasPrefix)
          Constructor for CLWriter.
Method Summary
 void close()
          Closes this writer.
 void write(CLCommand command)
 void write(String s)
          Write a string to the writer.
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail


public static final String Copyright
See Also:
Constant Field Values
Constructor Detail


public CLWriter(Writer writer)
Constructor for CLWriter. Assumes a data length of 80 with a 12 character prefix used for line number and date fields. Automatically adds end-of-line characters to each command or string.


public CLWriter(Writer writer,
                int dataLength,
                boolean hasPrefix)
Constructor for CLWriter. User specfies the data length and whether a prefix is needed or not.

Method Detail


public void write(CLCommand command)


public void write(String s)
Write a string to the writer. Chunking it according to CL rules. The "-" continuation convention for CL is used so that if strings are split their lengths are correctly preserved.


public void close()
Closes this writer.

Rational Developer for Power Systems Software

Copyright 2011 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.