java: String StringBuffer StringBuilder

最新推荐文章于 2021-03-10 11:13:27 发布

shuai_wen

最新推荐文章于 2021-03-10 11:13:27 发布

阅读量442

点赞数

分类专栏： android

本文链接：https://blog.csdn.net/u011279649/article/details/53114931

版权

android 专栏收录该内容

130 篇文章 9 订阅

订阅专栏

c语言中的字符串定义：以“\0”结尾

JAVA中的字符串：String不属于8种基本数据类型，String是一个对象。

在 java 语言中, 用来处理字符串的的类常用的有 3 个: String、StringBuffer、StringBuilder。

它们的异同点:

1) 都是 final 类, 都不允许被继承;

2) String 长度是不可变的, StringBuffer、StringBuilder 长度是可变的;

3) StringBuffer 是线程安全的, StringBuilder 不是线程安全的。

创建字符串的示例：

final String headers = new StringBuilder(512)
.append("Build: ").append(Build.FINGERPRINT).append("\n")
.append("Hardware: ").append(Build.BOARD).append("\n")
.append("Revision: ")
.append(SystemProperties.get("ro.revision", "")).append("\n")
.append("Bootloader: ").append(Build.BOOTLOADER).append("\n")
.append("Radio: ").append(Build.RADIO).append("\n")
.append("Kernel: ")
.append(FileUtils.readTextFile(new File("/proc/version"), 1024, "...\n"))
.append("\n").toString();

如何在c语言中使用java传入的String

　java中有本地方法，如：

public native String sayHello(Strings);

对应编译后生成的.h头文件中应该是：

JNIEXPORT jstring JNICALLJava_Test_sayHello(JNIEnv *, jobject,jstring);

如何在c语言中使用java传入的字符串s，也就是说如何使用jstring类型。那么在c语言实现中如何使用传入的字符串s？

我们知道java中的String，c语言中应该对应的是char*类型，也就是说我们在jni的c语言实现中如何把jstring类型转换成为char*即可。

方法是这样的：

在c文件中声明char* str，然后
str= (char*)(*env)->GetStringUTFChars(env, jstring,NULL);

这样就可以得到传入的字符串，过程如下：

JNIEXPORT jstring JNICALLJava_Test_sayHello
  (JNIEnv * env, jobject obj, jstring s)
{
   char * str;
  str=(char*)(*env)->GetStringUTFChars(env,s,NULL);
  printf("%s",str);

  (*env)->ReleaseStringUTFChars(env, s, str);

  ......
}

当然，java中有垃圾回收机制，二c语言没有，那么使用完该字符串之后该如何处理呢？字符串str使用完后，需要通知虚拟机平台相关代码无需再访问，方法是
(*env)->ReleaseStringUTFChars(env, jstring, str);

最后还要说一下，如果传入传出的字符串是中文，就又有问题了，我们需要手工进行uncode编码，否则就是乱码，当然如果程序设计合理，这里一般情况下尽量避免进行汉字的传递。

//! This is a string holding UTF-16 characters.
class String16

｝

//! This is a string holding UTF-8 characters. Does not allow the value more
// than 0x10FFFF, which is not valid unicode codepoint.
class String8
{

｝

来自java层的字符串，是通过该函数转化的，就是java层来的是UTF16

static String8 good_old_string(const String16& src)
{
    String8 name8;
    char ch8[2];
    ch8[1] = 0;
    for (unsigned j = 0; j < src.size(); j++) {
        char16_t ch = src[j];
        if (ch < 128) ch8[0] = (char)ch;
        name8.append(ch8);
    }
    return name8;
}

What is the difference between UTF-8 and UTF-16?

UTF-8 uses a minimum of 1 8-bit byte to encode character s. For the 128 7-bit characters of the ASCII character set, it is backward-compatible with ASCII: a roman-alphabet ASCII text encoded in UTF-8 will display normally on a system that does not understand UTF-8. Accented characters are not part of ASCII and so they will all be more or less garbled. Beyond 1 byte, UTF-8 may use 2, 3 or 4 bytes to encode the rest of the Unicode character set. Because of the way it uses the first byte of multi-byte sequences, UTF-8 uses 3 bytes for some characters that require only 2 bytes in UTF-16.

UTF-16 uses a minimum of 2 bytes/16 bits . This makes it in compatible with ASCII. Given an /A-Za-z/ text in UTF-16, a system that does not understand UTF-16 will make a mess of it (showing a null character before every single character).

A few examples:

"A" in ASCII is hex 0x41; in UTF-8 it is also 0x41; in UTF-16 it is 0x0041
"À" in Latin-1 is 0xC0; in UTF-8 it is 0xC3 0x80; in UTF-16 it is 0x00C0
The Tibetan letter ཨ in UTF-8 is 0xE0 0xBD 0xA8; it UTF-16 it is 0x0F68
This character*: http://www.fileformat.info/info/... in UTF-8 is 0xF0 0xA0 0x80 0x8B; in UTF-16 it is 0xD840 0xDC0B