使用JMeter测试套接字(Using JMeter to test a socket)

 两件事情： 
 
 1）Doxygen解析器在doNothing中不会“看到”“IN”（因为它在预处理阶段被移除），因此\ fn不应包含它： const char* doNothing(const char* s) 。 顺便说一句，这不是必要的：如果紧靠记录在案的实体之前，Doxygen会自动将评论关联起来。 
 
 2）我不知道__SXC_FUNCTION_ATTRIBUTE扩展到什么，但如果它类似于__MYLIB_FUNCTION_ATTRIBUTE，它可能会混淆Doxygen。 作为一种解决方法，您可以在Doxygen的配置文件的PREDEFINED部分中将这些宏定义为无，或者有条件地在源中定义它们，如下所示： 
 
#ifdef DOXYGEN
// Doxygen does not grok the normal definition of this
#define  __MYLIB_FUNCTION_ATTRIBUTE(...)
#else
#define __MYLIB_FUNCTION_ATTRIBUTE(...)    __attribute__(__VA_ARGS__)
#endif
 
 并将PREDEFINED = DOXYGEN放入配置文件中。 

Two things: 
 
1) The Doxygen parser does not "see" the "IN" in doNothing (since it is removed in the preprocessing phase), so the \fn should not include it: const char* doNothing(const char* s). BTW, this \fn is not necessary: Doxygen automatically associates the comment if it is immediately before the documented entity.
 
2) I don't know what __SXC_FUNCTION_ATTRIBUTE expands into but, if it is something similar to __MYLIB_FUNCTION_ATTRIBUTE, it probably confuses Doxygen. As a workaround, you could either define these macros to nothing in the PREDEFINED section of Doxygen's config file, or conditionally define them in the sources, like this:
 
#ifdef DOXYGEN
// Doxygen does not grok the normal definition of this
#define  __MYLIB_FUNCTION_ATTRIBUTE(...)
#else
#define __MYLIB_FUNCTION_ATTRIBUTE(...)    __attribute__(__VA_ARGS__)
#endif
 
and put PREDEFINED = DOXYGEN in your config file.