> >>>>Is there any way in DOS PAL 4.0 to delete an arbitrary file?
> >> EDITOR NEW FileName
> >> WINDOW CLOSE
> >What the #$!*(% are you trying to code?
> It is very clever way of taking advantage of the fact that EDITOR NEW
> will open up the given filename and will overwrite any existing file
> of the same name. And then closing an editor session without saving
> is same as getting rid of it.
> >You deserve a flame!!!
> ! ? :-)
It might be clever, however, the code that Mr. Aahz posted will not run. I
pointed this out in my last two follow-up posts. I suggest that you read
them. I note that the code you post here is different from the code that
was posted by Mr. Aahz in his follow-up to the question, and maybe it will
run, however, this does not release Mr. Aahz from the bad code that he
wrote, so my point of "What the #$!*(% are you trying to code?" still
stands, even though the code will work with your version of it.
I rest my case, and hope that in the future, all answers that are posted to
this group have been tested for bugs, because I hate to use code that
doesn't work and isn't documented, as your code doesn't have comments in it
either. Do you believe in putting comments in your code to help the user
of such code? Or are you just coding on the fly, without regards to the
user of your code. I believe that people who use my code should be able to
understand it as much as I do, and the only way to do this is by practicing
good coding standards.
I would invite you to read my post "Suggestions for FAQ - or Posts to this
Group", in which I detail the condition of the code that gets posted to
this group. If we are "pros" then why do we still not include comments in
our code? Surely we have learned to practice a habit such as this by now,
or are we all beginners?
Still hacking ...