Re^3: XML-Twig: Tree building and printing

What part is nonsense? When you print to a file, it doesn't automatically write to disk that instant. That would be inefficient. An example: you have a script that prints some log file to keep track of the script's progress. Unless you activate autoflush, you can't be certain that the log file represents the current status of the running script. In fact, sometimes the data destined for the log file might not be written at all until the script is completely finished executing.

Comment on Re^3: XML-Twig: Tree building and printing

Replies are listed 'Best First'.
Re^4: XML-Twig: Tree building and printing by Anonymous Monk on Jun 25, 2012 at 07:04 UTC
The whole thing is nonsense, flushing isn't the issue, building a second gigantic self-referential hash of hashes of hashes of hashes .... in memory is the problem There is no point in graft onto tree just print it	[reply]
Re^5: XML-Twig: Tree building and printing by frozenwithjoy (Priest) on Jun 25, 2012 at 07:08 UTC
Then why not try to actually explain this to the OP instead of just talking about how my suggestion in response to his/her question about flushing is nonsense?	[reply]
Re^6: XML-Twig: Tree building and printing by Anonymous Monk on Jun 25, 2012 at 07:17 UTC
Then why not try to actually explain this to the OP instead of just talking about how my suggestion in response to his/her question about flushing is nonsense? I can do both which is why I did. Take a look again, the OP didn't ask me to elaborate, you asked.	[reply]