[EMAIL PROTECTED] wrote:
This will be done AFTER the children are removed, just to check if the
folder is really empty before deleting it.
I think the indention was to check if any other process created a file
within the folder structure - and thus to avoid a error message during
recursive delet
> This will be done AFTER the children are removed, just to check if the
> folder is really empty before deleting it.
> I think the indention was to check if any other process created a file
> within the folder structure - and thus to avoid a error message during
> recursive delete.
Not really
[EMAIL PROTECTED] wrote:
So the call to file.getChildren().length != 0 is already made during delete
for every folder.
This will be done AFTER the children are removed, just to check if the
folder is really empty before deleting it.
I think the indention was to check if any other process create
FileObject.delete() calls FileObject.delete(Selectors.SELECT_SELF)
So all the juice is in delete(FileSelector)
There we find section
>>> SNIP
// If the file is a folder, make sure all its children have been deleted
if (file.type == FileType.FOLDER && file.getChildren().length != 0)
{
// TODO
USING EXTERNAL EDITOR
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
If I delete a FileObject I don't get any information about
whether that FileObject was actually deleted or not.
If file is FOLDER with children or IMAGINARY nothing is
deleted but there is no way to know that.
Actually you can query the file type and know for
sure in case of IMAGINARY but in case o
