replicant-frameworks_native/libs/utils
Android (Google) Code Review 00ea06792b am de72697b: Merge change 4524 into donut
Merge commit 'de72697b771d33738c5f9d6c28087504e0796622'

* commit 'de72697b771d33738c5f9d6c28087504e0796622':
  FileRestoreHelper and RestoreHelperDispatcher work.
2009-06-17 21:49:21 -07:00
..
Android.mk get rid of LogSocket which wasn't even implemented (enabled) 2009-06-05 15:11:23 -07:00
Asset.cpp
AssetDir.cpp
AssetManager.cpp
BackupData.cpp FileRestoreHelper and RestoreHelperDispatcher work. 2009-06-17 16:20:55 -07:00
BackupHelpers.cpp checkpoint BackupDatAInput / RestoreHelper 2009-06-16 18:46:50 -07:00
BufferedTextOutput.cpp
CallStack.cpp
CharacterData.h
Debug.cpp
FileMap.cpp
futex_synchro.c
misc.cpp
MODULE_LICENSE_APACHE2
NOTICE
README
RefBase.cpp
ResourceTypes.cpp
SharedBuffer.cpp
Static.cpp
StopWatch.cpp
String8.cpp
String16.cpp
StringArray.cpp rename string_array.h to StringArray.h and move the implementation from the header file to a new cpp file. 2009-06-05 01:26:23 -07:00
SystemClock.cpp
TextOutput.cpp
Threads.cpp
Timers.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.