realloc question

[Mark McIntyre]

And I objected to the manner in which you "offered your package as an
example".

If the day comes when the regulars here may not post links to example
code they've written, it'll be a sad one.

Stop being such a silly.
Mark McIntyre

 

[Chuck F.]

Dag-Erling Smørgrav wrote:

I think you need to go back and read the thread. The point
was the possible inefficiency that can arise from forcing
copying of existing data. I pointed out that some reallocs go
to lengths to avoid it, and offered my package as an example.

And I objected to the manner in which you "offered your package
as an example". In the context of the discussion, it seemed
that you were promoting your implementation as a superior
alternative to glibc's, and the basis for that comparison is
flawed.

Since nmalloc is tied to DJGPP and would require at least some
effort to port elsewhere [...]

Precisely; just as glibc is fairly strongly tied to Linux + gcc
(it also runs on Hurd, but with a different malloc()
implementation). It does however attempt to remain portable to
platforms which do not have the same facilities (mremap(2), in
this case) as Linux.

This is ridiculous. Previously I have found Scandinaves to be
sane, reasonable, and polite. There is always the exception that
proves the rule. Quisling was one. Goodbye. PLONK.

--
"If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson
More details at: <http://cfaj.freeshell.org/google/>

 

[Mark B]

Bullshit. Like many of us, Chuck posts links to examples of code that
he's written. If you don't like that, then move on, the5re's nothing
for you here.

Go back and read my entire post... then go f**k yourself.

Regards,
Mark

 

[Mark McIntyre]

Go back and read my entire post... then go f**k yourself.

Abusive idiot.

*plonk*
Mark McIntyre