Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
OpenHarmony
Third Party Harfbuzz
提交
910a33fe
T
Third Party Harfbuzz
项目概览
OpenHarmony
/
Third Party Harfbuzz
接近 2 年 前同步成功
通知
1
Star
18
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
T
Third Party Harfbuzz
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
提交
910a33fe
编写于
5月 14, 2010
作者:
B
Behdad Esfahbod
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Update buffer docs
上级
36b73c80
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
15 addition
and
14 deletion
+15
-14
src/hb-buffer-private.hh
src/hb-buffer-private.hh
+7
-6
src/hb-buffer.cc
src/hb-buffer.cc
+8
-8
未找到文件。
src/hb-buffer-private.hh
浏览文件 @
910a33fe
...
@@ -106,13 +106,14 @@ struct _hb_buffer_t {
...
@@ -106,13 +106,14 @@ struct _hb_buffer_t {
/* Buffer contents */
/* Buffer contents */
unsigned
int
allocated
;
unsigned
int
allocated
;
/* Length of allocated arrays */
hb_bool_t
have_output
;
/* whether we have an output buffer going on */
hb_bool_t
have_output
;
/* Whether we have an output buffer going on */
hb_bool_t
have_positions
;
/* whether we have positions */
hb_bool_t
have_positions
;
/* Whether we have positions */
unsigned
int
len
;
unsigned
int
out_len
;
unsigned
int
i
;
/* Cursor into ->info and ->pos arrays */
unsigned
int
i
;
unsigned
int
len
;
/* Length of ->info and ->pos arrays */
unsigned
int
out_len
;
/* Length of ->out array */
hb_internal_glyph_info_t
*
info
;
hb_internal_glyph_info_t
*
info
;
hb_internal_glyph_info_t
*
out_info
;
hb_internal_glyph_info_t
*
out_info
;
...
...
src/hb-buffer.cc
浏览文件 @
910a33fe
...
@@ -38,20 +38,20 @@ static hb_buffer_t _hb_buffer_nil = {
...
@@ -38,20 +38,20 @@ static hb_buffer_t _hb_buffer_nil = {
/* Here is how the buffer works internally:
/* Here is how the buffer works internally:
*
*
* There are two
string pointers: info and out_info. They
* There are two
info pointers: info and out_info. They always have
*
always have same allocated size, but different length and position
s.
*
the same allocated size, but different length
s.
*
*
* As an optimization, both info and out_info may point to the
* As an optimization, both info and out_info may point to the
* same piece of memory, which is owned by info. This remains the
* same piece of memory, which is owned by info. This remains the
* case as long as out_len doesn't exceed len at any time.
* case as long as out_len doesn't exceed len at any time.
* In that case, swap() is no-op and the glyph operations operate
mostly
* In that case, swap() is no-op and the glyph operations operate
* in-place.
*
mostly
in-place.
*
*
* As soon as out_info gets longer than info, out_info is moved over
* As soon as out_info gets longer than info, out_info is moved over
* to an alternate buffer (which we reuse the pos
itions
buffer for!), and its
* to an alternate buffer (which we reuse the pos buffer for!), and its
* current contents (out_len entries) are copied to the
alt buffer
.
* current contents (out_len entries) are copied to the
new place
.
* This should all remain transparent to the user. swap() then
switches
* This should all remain transparent to the user. swap() then
* info and out_info.
*
switches
info and out_info.
*/
*/
/* XXX err handling */
/* XXX err handling */
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录