From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,24a59fbc07128ff8 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-05-09 15:04:47 PST Path: newsfeed.google.com!newsfeed.stanford.edu!sn-xit-01!sn-post-01!supernews.com!corp.supernews.com!not-for-mail From: Fraser Wilson Newsgroups: comp.lang.ada Subject: Re: rename missing in Text_IO Date: 09 May 2001 15:04:45 -0700 Organization: Posted via Supernews, http://www.supernews.com Message-ID: Sender: fraser@slider References: <9cvdav$8q61@news.cis.okstate.edu> <9da0p9$7hu2@news.cis.okstate.edu> X-Newsreader: Gnus v5.5/XEmacs 20.4 - "Emerald" X-Complaints-To: newsabuse@supernews.com Xref: newsfeed.google.com comp.lang.ada:7409 Date: 2001-05-09T15:04:45-07:00 List-Id: charleshixson@earthling.net (Charles Hixson) writes: > But if what we are considering is what an Ada Library Package > should look like, then there's no reason to copy the low level > features of an operating system. And the semantics of the mv > command is generally superior. A program should not need to > know the details of the disk layout. The problem is that a rename or move on the same disk is significantly cheaper than one that crosses disks. It's also a much safer operation. I think the implementation detail line is quite fuzzy here. More generally, the destination might not even be a disk filesystem; it could be a remote ftp site or /proc on Linux. Does a move/rename even make sense in those cases? Fraser.