>>>>> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
Allan> The third option which I'm still inclined to prefer (for its
Allan> simplicity) is to have each Inset provide writer specific
Allan> methods. Such a scheme wouldn't make it any harder for the
Allan> writer to keep a check of the output (to break lines at
Allan> appropriate points or insert extra spaces etc.). It would also
Allan> be possible to use an ostream syntax for the writers. Let's
Allan> call this Option3.
I tend to agree that this is the somplest solutions. If we want to
have all the output methods in the same place, we can always do what
mathed does: all the Write methods of the different insets are in the
same file.
Allan> Other comments: I like the iostream appearance of my scheme
Allan> with the overloaded operator<<. Unfortunately, I doubt we
Allan> could modify Lars' scheme to use overloaded operator<< unless
Allan> we changed it to being overloaded on inset types. I think my
Allan> scheme needs something better than the WriterStyles enum to
Allan> configure the Writer stream. Maybe something similar to the
Allan> ostream manipulators (setw() and the like).
I'd say that << is merely syntactic sugar. Do we really need that?
JMarc
