Rockbox.org home
release
dev builds
extras
themes manual
wiki
device status forums
mailing lists
IRC bugs
patches
dev guide



Rockbox mail archive

Subject: RE: search a string

RE: search a string

From: John Wood <John.Wood_at_royalblue.com>
Date: Fri, 6 Sep 2002 11:40:46 -0400

A standard/complete malloc is a bad idea I agree. But having dynamic memory
allocation isn't. It's necessary in fact.
A temporary "scratch" area is a good idea. I think it should be implemented
as a stack so we avoid fragmentation (ie. you can only free space things in
a certain order, and what's remaining will always be used as the mpeg
buffer). That might get a little complex if you claim something that's
already being read by the mpeg decoder, but sometimes even waiting for it to
be released by the decoder wouldn't be too bad.

-----Original Message-----
From: George Styles [mailto:george_at_ripnet.co.uk]
Sent: Friday, September 06, 2002 11:22 AM
To: rockbox_at_cool.haxx.se
Subject: Re: search a string


I agree with (whoever) said that having complete malloc and so on is a bad
idea, as it adds too much overhead to an embedded system. They also said
that its standard practice in embedded systems to not have mallow

Why not compromise and have a fixed static memory buffer designated as a
scratch area, ie, can be used within a routine, but dont expect the contents
to be the same next time.

g


*************************************************************************
This message is intended only for the stated addressee(s)
and may be confidential. Access to this email by anyone
else is unauthorised. Any opinions expressed in this email
do not necessarily reflect the opinions of royalblue.
Any unauthorised disclosure, use or dissemination,
either whole or in part is prohibited,. If you are not the
intended recipient of this message, please notify
the sender immediately.
*************************************************************************
Received on 2002-09-06

Page template was last modified "Tue Sep 7 00:00:02 2021" The Rockbox Crew -- Privacy Policy