Ok, I follow what you're saying. The expedient approach is to wrapper some of the js calls, the way I wrapper malloc, to simply exit upon null, and I think that would be fine for now, provided the runtime pool is pushed up to 64 meg. It just wouldn't come up very often. People download huge files, but that doesn't consume huge javascript space. Web pages come in a certain size, and usually don't include memory intensive js.
Later versions can, perhaps, be more graceful about these allocation errors, but I think size_t issues, better dom support, ajax, plugins (particularly flash), and imap, are all higher priority. For now, a version that never ever segfaults would be lovely. Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
