replicant-frameworks_native/libs/utils
2011-02-24 16:23:51 -08:00
..
tests
Android.mk
Asset.cpp
AssetDir.cpp
AssetManager.cpp
BackupData.cpp
BackupHelpers.cpp
BufferedTextOutput.cpp
CallStack.cpp
Debug.cpp
FileMap.cpp
Flattenable.cpp
Looper.cpp
misc.cpp
MODULE_LICENSE_APACHE2
NOTICE
ObbFile.cpp
Pool.cpp
PropertyMap.cpp
README
RefBase.cpp Fix some issues with RefBase debugging. 2011-02-23 22:21:41 -08:00
ResourceTypes.cpp am a1f5e82f: am a30063d8: am 25eb0464: Merge "Normalize output from aapt d" 2011-01-29 23:07:48 -08:00
SharedBuffer.cpp
Static.cpp
StopWatch.cpp
StreamingZipInflater.cpp
String8.cpp
String16.cpp
StringArray.cpp
SystemClock.cpp Clean up use of HAVE_ANDROID_OS 2011-02-16 10:56:32 -08:00
TextOutput.cpp
Threads.cpp Bug 3362814 Fix SMP race in access to mRequestExit 2011-02-23 17:49:59 -08:00
Timers.cpp
Tokenizer.cpp
Unicode.cpp
VectorImpl.cpp
ZipFileCRO.cpp
ZipFileRO.cpp
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.