Peter van Hardenberg wrote:
On November 20, 2005 11:47 pm, Hans Reiser wrote:
Peter van Hardenberg wrote:
We have an implementation plan for the attribute plugin. We plan to base
it around the plugin.c so that it can be available for all files,
directory or otherwise.
Every file which has a pseudo will gain a new user-attributes pseudofile.
This pseudofile will essentially wrap a standard directory.
Usage examples please.
---------------------------------
Simple moves first:
$ echo "Matmos" >> track01.mp3/..@/artist
$ echo "A Chance to Cut is a Chance to Cure" >> track01.mp3/..@/album
$ grep Matmos track01.mp3/..@/*
artist: Matmos
---------------------------------
Some hypothetical pseudocode from a music player:
playcount = open('track01.mp3/..@/amarok/playcount').read;
playcount = playcount + 1;
open('track01.mp3/..@/amarok/playcount', 'w').write(playcount);
---------------------------------
PvH,
I am really worried about introducing this new concept of "attribute
directory" and new syntax. Maybe I am just missing the point (in which
case please explain), but is there anything you can do with this that
there is no way you could do without it.
Hans' favourite topic (quite rightly) is namespace unification, which
involves keeping the syntax as simple as possible, having only one type
of expression for one kind of logical structure. If you could possibly
do this without the "..@", do it without it.
So why not just do (to take your example):
$ echo "Matmos" >> track01.mp3/artist
Peter F
