[Vm-dev] FilePlugin argument checking - primitiveFailed vs PrimErrBadArgument

[Alistair Grant]

Hi David,

Apologies for my slow response.


On 4 March 2018 at 21:09, David T. Lewis <lewis at mail.msen.com> wrote:
>
> On Sun, Mar 04, 2018 at 06:46:50PM +0000, Alistair Grant wrote:
>>
>> Hi David,
>>
>>
>> Following on from Tim's comments above, how much work do you think is
>> required to turn PosixDirectoryStreamPlugin and
>> PosixFileStatPlugin in to a FilePlugin replacement (I think merging
>> PosixFileStatPlugin and FileAttributesPlugin will be straightforward)?
>
>
> Hi Alistair,
>
> I don't really think that these plugins would provide a suitable path toward
> replacing FilePlugin. I see them more as small (and optional) add-on functions.
> They are also quite Unix specific, so a general solution would require a bit
> of thought regarding what abstractions to use.

OK.  I'll work at adding functionality to FileAttributesPlugin for now
and think about a FilePlugin re-write down the track after learning (a
lot) more about writing primitives.

Thanks!
Alistair




> Just as an example, file systems on Windows use a very different approach
> for keeping track of file access times. On Windows, it is creation time,
> last access time, and last write time, while on Unix (including OSX) it
> is last access time, last modification time, and last status change time.
> There are other fundamental differences too, so you can't really get away
> with applying Posix rules to other kinds of systems.
>
> Dave