.h文件中的大表! [英] Big tables in .h file!

查看:66
本文介绍了.h文件中的大表!的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您好,大师。


http://cvs.gnome.org/viewcvs/libunicode/msft/cp932.h?rev=1.2&view=markup"


我偶然发现了一件有趣的事情。如果您点击此链接,您将看到位于H

文件中的巨大翻译表(从ascii到unicode)。现在。众所周知(至少在我看来),这样的表格更好地存储在C文件中,对吗?因此,如果包含双b / b
,那么糟糕的事情就不会发生......


我真的相信那些侏儒家伙,我很有信心他们真的很聪明,而且这个背后还有一些想法。


请给我一个提示!!

谢谢

Hello, gurus.

http://cvs.gnome.org/viewcvs/libunicode/msft/cp932.h?rev=1.2&view=markup"

I''ve stumbled upon an interesting thing. If you follow this link, you
will see huge translation tables (from ascii to unicode) located in H
file. Now. It is well known (at least to me), that such tables are
better to be stored in C file, right? So that in case of double
inclusion, bad things won''t happen...

I really trust those gnome guys, I''m sure they''re really smart, and
there was some thought behind this.

Please, give me a hint!!

Thanks

推荐答案

Zhekkaaécrit:
Zhekka a écrit :
http://cvs.gnome .org / viewcvs / libunicode / msft / cp932.h?rev = 1.2& view = markup"

我偶然发现了一件有趣的事情。如果您点击此链接,您将看到位于H
文件中的巨大翻译表(从ascii到unicode)。
http://cvs.gnome.org/viewcvs/libunicode/msft/cp932.h?rev=1.2&view=markup"

I''ve stumbled upon an interesting thing. If you follow this link, you
will see huge translation tables (from ascii to unicode) located in H
file.




绝对无意义。编写代码生成器的人应该使用
蜂蜜和火蚁...


-

A +


Emmanuel Delahaye



Absolute nonsense. The guy who has written the code generator desserves
honey and fire ants...

--
A+

Emmanuel Delahaye


Emmanuel Delahaye< em *** @ YOURBRAnoos.fr>写道:
Emmanuel Delahaye <em***@YOURBRAnoos.fr> writes:
Zhekka icrit:
Zhekka a icrit :
http://cvs.gnome.org/viewcvs/libunicode/msft/cp932.h?rev=1.2& ; view = markup"
我偶然发现了一件有趣的事情。如果您点击此链接,您将看到位于H
文件中的巨大翻译表(从ascii到unicode)。
http://cvs.gnome.org/viewcvs/libunicode/msft/cp932.h?rev=1.2&view=markup"
I''ve stumbled upon an interesting thing. If you follow this link, you
will see huge translation tables (from ascii to unicode) located in H
file.



绝对无意义。编写代码生成器的人应该使用蜂蜜和火蚁......



Absolute nonsense. The guy who has written the code generator desserves
honey and fire ants...




我想这个.h文件只包含在一个.c文件中文件。

也就是说,它不是真正的标题,它只是一个生成的表

包含在一些源文件中。我通常会使用.inc

扩展名来避免让人感到困惑。

-

在我的Egotistical Opinion中,大多数人'C程序应该向下缩进六英尺,然后用泥土覆盖。 - Blair P. Houghton



I imagine that this .h file is included in only one .c file.
That is, it''s not really a header, it''s just a generated table
for including in some source file. I usually use a .inc
extension for such code to avoid confusing people.
--
"In My Egotistical Opinion, most people''s C programs should be indented six
feet downward and covered with dirt." -- Blair P. Houghton


Zhekka写道:
你好,大师。

http:// cvs。 gnome.org/viewcvs/libunicode/msft/cp932.h?rev=1.2&view=markup"

我偶然发现了一件有趣的事情。如果您点击此链接,您将看到位于H
文件中的巨大翻译表(从ascii到unicode)。现在。众所周知(至少在我看来),这样的表格更好地存储在C文件中,对吗?因此,如果包含双重内容,那么糟糕的事情就不会发生......

我真的相信那些侏儒们,我相信他们真的很聪明,而且
这背后有一些想法。

请给我一个提示!!
Hello, gurus.

http://cvs.gnome.org/viewcvs/libunicode/msft/cp932.h?rev=1.2&view=markup"

I''ve stumbled upon an interesting thing. If you follow this link, you
will see huge translation tables (from ascii to unicode) located in H
file. Now. It is well known (at least to me), that such tables are
better to be stored in C file, right? So that in case of double
inclusion, bad things won''t happen...

I really trust those gnome guys, I''m sure they''re really smart, and
there was some thought behind this.

Please, give me a hint!!




见包含警卫 ?


#ifndef MSFT_CP932_H

#define MSFT_CP932_H

....

#endif / * MSFT_CP932_H * /


这些可以防止双重包含:)


再见。



see the "inclusion guards"?

#ifndef MSFT_CP932_H
#define MSFT_CP932_H
....
#endif /* MSFT_CP932_H */

these prevent double inclusion :)

bye.


这篇关于.h文件中的大表!的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆