A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-June/066366.html below:

[Python-Dev] doc for new restricted execution design for Python

[Python-Dev] doc for new restricted execution design for Python [Python-Dev] doc for new restricted execution design for PythonBrett Cannon brett at python.org
Thu Jun 22 15:46:29 CEST 2006
On 6/22/06, Gerhard Häring <gh at ghaering.de> wrote:
>
> Brett Cannon wrote:
> > I have been working on a design doc for restricted execution of Python
> > [...]
>
> All the rest of the API made sense to me, but I couldn't understand why
>
> PyXXX_MemoryFree
>
> is needed. How could memory usage possibly fall below 0?


It can't in real life, but people could call MemoryFree() too many times.
Plus you need some way to lower the amount when memory is freed.  No need to
penalize a script that does a bunch of malloc/free calls compared to one
that just does a bunch of malloc calls.

-Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/python-dev/attachments/20060622/c0efc91b/attachment.htm 
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4