Michael G Schwern <[EMAIL PROTECTED]> writes:
>
>But you're not. You're just exposing sbrk(), which is a gory detail. My
>sbrk man page describes sbrk as being used to find "the current location of
>the program break" which means nothing to me. Nor does "returns the current
>memory top".
>
>It'l
H.Merijn Brand <[EMAIL PROTECTED]> writes:
>
>Ahh, someone on /my/ side.
>
>I guess most of the discussion boils down to
>
>- sbrk () being unknown to people not familiar with unix
>- Devel::Internals being to wide. [ Gimme another namespace proposal ]
>- MemUsed interface to polymorphistic
>
>So
