Witold Filipczyk <[EMAIL PROTECTED]> writes:

> When there is no more memory say sorry and exit.

That would be okay for noninteractive uses such as elinks -dump.
However I would hate to lose state because of running out of memory.
AFAIK, ui.sessions.snapshot does not save session cookies,
form data, and session-specific history.

> ELinks will be smaller, therefore faster.

I doubt the speed would change noticeably.
Better algorithms would be more important.
Perhaps also cache locality for allocations.

Which reminds me of bug 297.  Can we use libapr for memory pools?

Attachment: pgp5VeKzu2DDW.pgp
Description: PGP signature

_______________________________________________
elinks-dev mailing list
elinks-dev@linuxfromscratch.org
http://linuxfromscratch.org/mailman/listinfo/elinks-dev

Reply via email to