News for hackers. Stuff that matters.

A comment on Scheme 9 interpreter ported to Plan 9 (again). Parent comment

Re:Scheme 9 interpreter ported to Plan 9 (again) by vezzy-fnord on Saturday July 04, 2015 @09:23AM (#9830067)
Which is the point. Files may be synthetic references to resources and not actual on-disk files, it's a general abstraction.
[ Parent | on HN ]
Re:Scheme 9 interpreter ported to Plan 9 (again) by agumonkey on Saturday July 04, 2015 @09:36AM (#9830098)
It's just a vocabulary thing, `file` is not that generic.
[ Parent | on HN ]
Re:Scheme 9 interpreter ported to Plan 9 (again) by vezzy-fnord on Saturday July 04, 2015 @09:41AM (#9830108)
Yes, it is. A file is just a representation of resources, nothing more. You can have files as a user convenience without even having a file system, but rather a persistent object store.
[ Parent | on HN ]
Re:Scheme 9 interpreter ported to Plan 9 (again) by typedweb on Saturday July 04, 2015 @12:29PM (#9830632)
A file is an object that supports the methods open(), read(), write(), and a few others. That's about a generic as you can get.
[ Parent | on HN ]
Re:Scheme 9 interpreter ported to Plan 9 (again) by agumonkey on Saturday July 04, 2015 @01:09PM (#9830768)
If I write <data> /dev/net/tcp can I read and get <data> back ?

Can I append <data> /dev/mouse ?

Sharing {open,read,write,close} interface, but with exception and different semantics leads to a weird flavour of genericity.

[ Parent | on HN ]