Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.forth > #24663

Re: RESIZE-FILE - mistakes ANS made

From Andrew Haley <andrew29@littlepinkcloud.invalid>
Subject Re: RESIZE-FILE - mistakes ANS made
Newsgroups comp.lang.forth
References <ksbh6p$8ug$1@speranza.aioe.org> <e314df9b-6da8-4cc7-adc9-a8e98a811ce4@googlegroups.com> <ksicue$4ih$1@speranza.aioe.org>
Message-ID <toednQNP_Y2vb3HMnZ2dnUVZ_vWdnZ2d@supernews.com> (permalink)
Date 2013-07-22 03:49 -0500

Show all headers | View raw


Ed <invalid@invalid.com> wrote:
> m.a.m.hendrix@tue.nl wrote:
>> On Friday, July 19, 2013 4:09:24 PM UTC+2, Ed wrote:
>> > 3. the position of the file-pointer should be  'ud'  because that's
>> >    the point at which one will begin writing new data.
>>
>> 4. The file-pointer should not change (assuming here that on some
>> systems it is more efficient to make room first, then write instead
>> of write and see what happens.)
> 
> Surely that's *inefficient* and contrary to the concept of 'random
> disk access'.
> 
> RESIZE-FILE should reflect what's most useful for applications.

It's like everything else in Forth, as was explained to me by
Elizabeth Rather some thirty or so years ago: we can't guarantee that
a word does exactly what your application needs, but we can guarantee
that we've thought about it.

I this case, OS behaviour isn't common, and in many uses it's not
necessary to move the file pointer.  So, in many cases it would be
pointless work.

> Should there be an OS which leaves the file-pointer at the wrong
> position, it's no problem for RESIZE-FILE to adjust it.

So do that, then.  It's your application.

Andrew.

Back to comp.lang.forth | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

RESIZE-FILE - mistakes ANS made "Ed" <invalid@invalid.com> - 2013-07-20 00:09 +1000
  Re: RESIZE-FILE - mistakes ANS made m.a.m.hendrix@tue.nl - 2013-07-19 07:55 -0700
    Re: RESIZE-FILE - mistakes ANS made Bernd Paysan <bernd.paysan@gmx.de> - 2013-07-19 22:34 +0200
    Re: RESIZE-FILE - mistakes ANS made "Ed" <invalid@invalid.com> - 2013-07-22 14:39 +1000
      Re: RESIZE-FILE - mistakes ANS made Alex McDonald <blog@rivadpm.com> - 2013-07-21 23:25 -0700
        Re: RESIZE-FILE - mistakes ANS made m.a.m.hendrix@tue.nl - 2013-07-22 01:21 -0700
          Re: RESIZE-FILE - mistakes ANS made Alex McDonald <blog@rivadpm.com> - 2013-07-22 15:00 -0700
          Re: RESIZE-FILE - mistakes ANS made "Ed" <invalid@invalid.com> - 2013-07-29 18:31 +1000
            Re: RESIZE-FILE - mistakes ANS made Andrew Haley <andrew29@littlepinkcloud.invalid> - 2013-07-29 03:36 -0500
              Re: RESIZE-FILE - mistakes ANS made "Ed" <invalid@invalid.com> - 2013-08-01 18:00 +1000
                Re: RESIZE-FILE - mistakes ANS made Andrew Haley <andrew29@littlepinkcloud.invalid> - 2013-08-01 03:33 -0500
      Re: RESIZE-FILE - mistakes ANS made m.a.m.hendrix@tue.nl - 2013-07-22 01:20 -0700
        Re: RESIZE-FILE - mistakes ANS made "Ed" <invalid@invalid.com> - 2013-07-24 17:56 +1000
      Re: RESIZE-FILE - mistakes ANS made Andrew Haley <andrew29@littlepinkcloud.invalid> - 2013-07-22 03:49 -0500
  Re: RESIZE-FILE - mistakes ANS made anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2013-07-22 11:40 +0000
    Re: RESIZE-FILE - mistakes ANS made "Ed" <invalid@invalid.com> - 2013-07-24 18:04 +1000

csiph-web