拯救你的字符串:发给Bjarne的信,大家来帮我评价一下

 

Dear Dr  Bjarne:
                          I'm a student from China. And I have some new ideas about some usual problems,  which I want to share with you.

                          I have to apologize for my poor English and some grammar errors which may existing in my following contents.

The attachment is the source code, can be directly compiled and run in all the compiler and system I own.


Begin:
string str = str1 + str2 + str3 + str4;
str = str1 + str2 + str3 + str4 + str;
Large number of temp objects are constructed and destructed in the expressions above, isn't it? Oh no, I can not afford it.
Using "+="? Good idea but bad style, in my opinion.
When binary operator are used in the expression-list like above, it's a grammar tree, in fact. But under control of complier, it generates "fruit" every "season". The temp fruits cost us a lot. Why not generate the final  fruit when "=", in another word, when needed ?
I've designed two methods, like following:
str =  seed<string>() + str1 + str2 + str3 + str4 + str;
or 
str =  seeder(str1 ) + str2 + str3 + str4 + str;
//The source and test codes are in the attachment.

Brief introduction:
It's very quick, and only  1 temp object generates when operator "=". The " seed" is used to build the tree all by ourselves and stop the tree fruit ! When the final fruit is needed, "+=" operator is used to faster the process.
It's helped by  expression-template theory, but not only.
What I focus on is the  interface.
It's non-invasive,easy to use, isn't it? I think it's very important in most projects in industry.
I'd prefer the 2nd way, but my friends remind me that some projects' codes in fact are generated by  macros, so the 1st method comes as addition. The 1st method just need correction at the beginning, so it's easier to used with some complicated macros.
It's generic-type, and does not need c++ 0x support (For portable reason and potential complier's bug, c++ 0x grammar is not allowed to used in most projects).
Because template can not be used for "generic-operator", I just provide operator "+". The interface can be used with some other binary operator if some proper template functions overload are implement and  meet some other  Restrain.


Restrain: Here I use  string and operator "+" as an example to describe the restrain of the type when we want to use the method above on the type. There are two types of  restraingrammar  restrain and  semantics restrain
The type  string must :
1. Having constructor with no argument. ( grammar  restrain)
2. Having constructor with  string argument. ( grammar  restrain)
3. Having "+=" operator with the same argument of all the related "+" operator overload. And the return type of operator "+" must be  string.  ( grammar  restrain)
(eg.
string& string::operator+= ( const string& str );     string operator+ (const string& lhs, const string& rhs);
string& string::operator+= ( const char* s );         string operator+ (const char* lhs, const string& rhs);
string& string::operator+= ( char c );                string operator+ (char lhs, const string& rhs);
)
4. str = str1  is  equivalent to  (str = (string() += str1) )  ( semantics restrain)
5. str1 = str1 + str2  is  equivalent to  str1 += str2  ( semantics restrain)
6. str1 + str2 + str3 + ...  is  equivalent to str1 + (str2 + str3 + ...) , it's not needed if you do not want to accelerate the process between the last "( )".  ( semantics restrain)
" equivalent to" here does not means operator "==". Operator "==" is not needed.
Compiling error comes if  grammar  restrain is not meet, while  semantics restrain error may lead to both compiling error and  run-time error!
Well down!

Test
The following codes are for test. It has tested all I can imagine. The codes can be found in the attachment. The macro TEST_TIME in line 6 can be changed if the test runs too fast :

    string str1 = "1234567890";
    string str2 = "12345678901234567890";
    string str3 = "123456789012345678901234567890";
//raw:       
str = "12345678901234567890" + str2 + string("123456789012345678901234567890") + str1 + str2 + str3 + (str1 + str2 + ' '+ (str +=' ') ) ;
//optimized: 
str = seed<string>( ) + "12345678901234567890" + str2 + string("123456789012345678901234567890") + str1 + str2 + str3 +  (seed<string>( ) + str1 + str2 + ' '+ (str +=' ') ) ;
str = "12345678901234567890" + any_seeder(str2) + string("123456789012345678901234567890") + str1 + str2 + str3 +  (any_seeder(str1) + str2 + ' ' + (str +=' ') ) ;
// One other seed is needed in the last "( )", or else the expression in the "( )" can not be optimized. It's because the sub-tree is planted before the main branch so the first seed can not affect its growth!
//Seed needs to know the "fruit" type to help the tree to generate implicit-cast function, so the template function "any_seeder" must wrap on object of final result type , like above.
result:
In my windows PC, 40% time reduce can be found on MSVC 6 compiler. Intel compiler v11 will increase the number high up to 60%.
In public Linux or Unix server, TEST_TIME has to be 10 times or more because the server is too fast. And the advantage is not obvious while the reduced time is less than 20%. I think it's because the main costs come from the huge times of memory require and release, and memory fragment increased soon. So the advantage is not as obvious as the test on PC.
The difference between the two method is less than 1% in all systems.
Conclusion
It's effectivelight-weighted non-invasive, portable(In the attachment codes , I've try my best on MSVC 6 compiler ) and easy to use, with the only weakness of potential  run-time error if semantics need is not meet What's more, I need your opinion and advice. If better method existed, I need your share. If others have invented it before me, thank you for telling me. 
Thank you for sparing your time.
附件的代码见下:
 

 

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 5
    评论
号处理领域,DOA(Direction of Arrival)估计是一项关键技术,主要用于确定多个号源到达接收阵列的方向。本文将详细探讨三种ESPRIT(Estimation of Signal Parameters via Rotational Invariance Techniques)算法在DOA估计中的实现,以及它们在MATLAB环境中的具体应用。 ESPRIT算法是由Paul Kailath等人于1986年提出的,其核心思想是利用阵列数据的旋转不变性来估计号源的角度。这种算法相比传统的 MUSIC(Multiple Signal Classification)算法具有较低的计算复杂度,且无需进行特征值分解,因此在实际应用中颇具优势。 1. 普通ESPRIT算法 普通ESPRIT算法分为两个主要步骤:构造等效旋转不变系统和估计角度。通过空间平移(如延时)构建两个子阵列,使得它们之间的关系具有旋转不变性。然后,通过对子阵列数据进行最小二乘拟合,可以得到号源的角频率估计,进一步转换为DOA估计。 2. 常规ESPRIT算法实现 在描述中提到的`common_esprit_method1.m`和`common_esprit_method2.m`是两种不同的普通ESPRIT算法实现。它们可能在实现细节上略有差异,比如选择子阵列的方式、参数估计的策略等。MATLAB代码通常会包含预处理步骤(如数据归一化)、子阵列构造、旋转不变性矩阵的建立、最小二乘估计等部分。通过运行这两个文件,可以比较它们在估计精度和计算效率上的异同。 3. TLS_ESPRIT算法 TLS(Total Least Squares)ESPRIT是对普通ESPRIT的优化,它考虑了数据噪声的影响,提高了估计的稳健性。在TLS_ESPRIT算法中,不假设数据噪声是高斯白噪声,而是采用总最小二乘准则来拟合数据。这使得算法在噪声环境下表现更优。`TLS_esprit.m`文件应该包含了TLS_ESPRIT算法的完整实现,包括TLS估计的步骤和旋转不变性矩阵的改进处理。 在实际应用中,选择合适的ESPRIT变体取决于系统条件,例如噪声水平、号质量以及计算资源。通过MATLAB实现,研究者和工程师可以方便地比较不同算法的效果,并根据需要进行调整和优化。同时,这些代码也为教学和学习DOA估计提供了一个直观的平台,有助于深入理解ESPRIT算法的工作原理。
评论 5
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值