Seems to like that already happens, from perlfunc
...
- DESCRIPTION
- Perl Functions by Category
....
Functions for filehandles, files, or directories
-X, chdir, chmod, chown, chroot, fcntl, glob, ioctl, link, lstat, mkdir, open, opendir, readlink, rename, rmdir, stat, symlink, sysopen, umask, unlink, utime
- Portability
Perl was born in Unix and can therefore access all common Unix system calls. In non-Unix environments, the functionality of some Unix system calls may not be available, or details of the available functionality may differ slightly. The Perl functions affected by this are:
-X, binmode, chmod, chown, chroot, crypt, dbmclose, dbmopen, dump, endgrent, endhostent, endnetent, endprotoent, endpwent, endservent, exec, fcntl, flock, fork, getgrent, getgrgid, gethostent, getlogin, getnetbyaddr, getnetbyname, getnetent, getppid, getprgp, getpriority, getprotobynumber, getprotoent, getpwent, getpwnam, getpwuid, getservbyport, getservent, getsockopt, glob, ioctl, kill, link, lstat, msgctl, msgget, msgrcv, msgsnd, open, pipe, readlink, rename, select, semctl, semget, semop, setgrent, sethostent, setnetent, setpgrp, setpriority, setprotoent, setpwent, setservent, setsockopt, shmctl, shmget, shmread, shmwrite, socket, socketpair, stat, symlink, syscall, sysopen, system, times, truncate, umask, unlink, utime, wait, waitpid
For more information about the portability of these functions, see the perlport manpage and other available platform-specific documentation.
...
Now I didn't come from a unix background, in fact I wasn't very knowledgable at all, but I managed to find unlink by looking at perlfunc. | [reply] |
Unlinking (er, I mean deleting) a file can be harder than it looks. In the perl core tests, 1 while unlink $file is often used (to support filesystems that allow multiple versions of a file). This occasionally causes problems when a close() is left out, since at least one platform has the interesting tactic of working around not being able to delete an open file by having unlink() schedule the file for later deletion but return true (causing the 1 while unlink to endlessly loop).
If you are downvoting this for other than lack of interest, thanks for sending me a message or reply to let me know why so I can do better (or just stay quiet) next time.
| [reply]
[d/l]
[select] |
I don't know how much experience with the Unixoid computing world you have, but if you'd been there, you'd notice there is almost nothing in Perl that wasn't in a lesser tool before. We've all heard that Perl is derived from C, shell, awk and sed; until you've learned those tools to a significant degree you won't recognize just how much truth there is in that statement.
The number of things "chosen" amounts to very nearly zero.
As such, unlink and friends couldn't have been called any differently.
I believe that the documentation of the Unixoid assumptions in Perl called for for the folks on Windows actually needs to document a fair amount of additional concepts besides just which function names where used for Perl builtins.
(I'm twitching to keep myself from it, but cannot help commenting that the more I absorb Unix, the more Windows feels like the far overgrown quick & dirty hack of an 8080 OS it is. And I'm not even talking about the codebase (which has been done from scratch in NT anyway and would be fixable with an undue amount of effort), I'm talking about concepts. Unix, as a design, makes sense. And it's not even perfect - there's a lot to do better yet.)
Makeshifts last the longest.
| [reply] |