On Wed, 12 Mar 2003, Szakacsits Szabolcs wrote:
> On Tue, 11 Mar 2003, Russ Christensen wrote:
> > I would like to ask a question on why the API for dealing with
> > runlists is setup the way it is.
>
> Anton could answer, personally I don't agree with all the API's.
Why don't you give concerete comments about what in particular you don't
agree with and how you would like to see it instead?
> BTW, occasionally there are also different ways to do the same thing
> in the library [something I don't like all the time as well] and what
Yes, there are many ways to achieve the same thing. Each of them has its
own applications and its own set of advantages/disadvantages. I don't
believe in giving people one function and telling them to use it and if it
doesn't fit with their application they can go to hell. I prefer to give
functions specialised to applications and if two ways exist to get the
same result but say one is optimised for streaming and the other for
random access or say one is very fast but more complex to use and one is
very slow but very easy to use then yes, it is very well worth it having
those multiple ways. People can then pick the one function that fits their
application. Windows APIs in that respect are complete crap IMO because
they provide one function with ten-twenty parameters that does everything
including make coffee and using it is just a PITA every time...
> you're trying to do is different how ntfsresize achives this and if
> you continue on your way I would expect finding bugs in the library.
I wouldn't. He is doing it exactly the way the library uses the functions
internally and the bugs would have been found and squashed a long time
ago... All the ntfsprogs would be broken if the code Russ showed would
result in showing up bugs in the library... ntfs_mount() for a start would
show up the exact same bugs...
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cantab.net> (replace at with @)
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
|