Alexander Viro writes:
> Basically you propose to take the current system, replace it with
> something without clear memory management ("let it leak") and then
> try to fix the resulting mess.
> I would rather switch code that uses kdev_t to use of dynamically
> allocated structures. Subsystem-by-subsystem. Keeping decent
> memory management on every step.
> It's _way_ easier than trying to fix leaks and dangling pointers in
> the fuzzy code we'd get with your approach. Just look at the fun
> Richard has with devfs right now.
Leaks go away if you add a garbage collector. To get rid of the
dangling pointers, write this part of the kernel in Java or LISP.
There's an OS called emacs that was done this way, and even has
a LISP engine under the GPL. Grab that code maybe.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:19 EST