replicant-frameworks_native/libs/utils
Kenny Root 196e320734 Excise code from Unicode.cpp that was dead
Remove some utility functions for discovering character data
that ICU probably took over a while ago.

Change-Id: I97abe4de2f51eb2bf48679941258bc501184c3dc
2010-02-12 13:01:16 -08:00
..
Android.mk
Asset.cpp Fix issue #2048263: More debugging information 2009-08-11 18:56:41 -07:00
AssetDir.cpp
AssetManager.cpp
BackupData.cpp Turn off most of the backup-related debug logging 2009-09-30 17:07:37 -07:00
BackupHelpers.cpp
BufferedTextOutput.cpp
CallStack.cpp
CharacterData.h Excise code from Unicode.cpp that was dead 2010-02-12 13:01:16 -08:00
Debug.cpp
FileMap.cpp
misc.cpp
MODULE_LICENSE_APACHE2
NOTICE
README
RefBase.cpp
ResourceTypes.cpp Add string resource type inspection 2009-12-10 14:22:08 -08:00
SharedBuffer.cpp
Static.cpp
StopWatch.cpp
String8.cpp Optional use of UTF-8 strings in resource bundles 2009-12-07 15:14:15 -08:00
String16.cpp Optional use of UTF-8 strings in resource bundles 2009-12-07 15:14:15 -08:00
StringArray.cpp
SystemClock.cpp
TextOutput.cpp
Threads.cpp Maybe really fix windows build. 2009-12-08 19:45:59 -08:00
Timers.cpp
Unicode.cpp Excise code from Unicode.cpp that was dead 2010-02-12 13:01:16 -08:00
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.