replicant-frameworks_native/libs/utils
Kenny Root 615f5d64db Range checking for ResTable_map
Correct previous offset change and get ready for safe-iop.

Change-Id: Ib276c726f32b0711a72f47d3263eb21640e5a800
2010-06-08 12:51:49 -07:00
..
Android.mk Make static versions of libutils and libbinder. 2010-05-06 01:03:31 -07:00
Asset.cpp
AssetDir.cpp
AssetManager.cpp ZipUtilsRO rewrite based on Dalvik Zip rewrite 2010-05-12 05:07:48 -07:00
BackupData.cpp
BackupHelpers.cpp
BufferedTextOutput.cpp
CallStack.cpp
Debug.cpp
FileMap.cpp
Flattenable.cpp
misc.cpp
MODULE_LICENSE_APACHE2
NOTICE
README
RefBase.cpp
ResourceTypes.cpp Range checking for ResTable_map 2010-06-08 12:51:49 -07:00
SharedBuffer.cpp
Static.cpp
StopWatch.cpp
String8.cpp Make static versions of libutils and libbinder. 2010-05-06 01:03:31 -07:00
String16.cpp
StringArray.cpp
SystemClock.cpp
TextOutput.cpp
Threads.cpp
Timers.cpp
VectorImpl.cpp Revert "fix [2542425] memory leak during video recording" 2010-03-30 21:04:17 -07:00
ZipFileCRO.cpp ZipUtilsRO rewrite based on Dalvik Zip rewrite 2010-05-12 05:07:48 -07:00
ZipFileRO.cpp ZipUtilsRO rewrite based on Dalvik Zip rewrite 2010-05-12 05:07:48 -07:00
ZipUtils.cpp

Android Utility Function Library

If you need a feature that is native to Linux but not present on other
platforms, construct a platform-dependent implementation that shares
the Linux interface.  That way the actual device runs as "light" as
possible.

If that isn't feasible, create a system-independent interface and hide
the details.

The ultimate goal is *not* to create a super-duper platform abstraction
layer.  The goal is to provide an optimized solution for Linux with
reasonable implementations for other platforms.