鍏朵腑p, q浜掔礌銆?br> 鍙互閲囩敤涓浗鍓╀綑瀹氱悊錛?span style="background-color: yellow;">x = q * Eq * a + p * Ep * b (mod pq ) , 鍏朵腑 Eq * q + Ep * p = 1;
鑰屾ā涓嶄簰绱犵殑鎯呭喌錛屽嵈鏈夌被浼肩殑褰㈠紡錛?br>
x = a (mod pd)
x = b (mod qd)
鍏朵腑p, q浜掔礌, d > 1銆?br> 濡傛灉d 涓嶆暣闄?a - b, 鍒欐棤瑙? 鍚﹀垯 x = q * Eq * a + p * Ep * b ( mod pqd ) , 鍏朵腑 Eq * q + Ep * p = 1;
鍙互楠岀畻榪欎釜鏋勯犺В鏄傚悎涓婇潰涓や釜鏂圭▼鐨勩?br> 姣斿楠岀畻絎竴涓柟紼嬶細(xì) 棣栧厛鍙樺艦寰楀埌 x = (1 - Ep * p ) * a + Ep * p * b (mod pd); 鍙堟湁錛歺 = a + Ep * p *( b - a ) (mod pd); 鍙堟湁錛歞 | (b - a) 鎵浠?pd | p*(b - a) 鎵浠?x = a ( mod pd )
]]>Why XAML Needed?http://m.shnenglu.com/logics-space/archive/2009/03/30/78370.htmlwangzhihaowangzhihaoMon, 30 Mar 2009 07:14:00 GMThttp://m.shnenglu.com/logics-space/archive/2009/03/30/78370.htmlhttp://m.shnenglu.com/logics-space/comments/78370.htmlhttp://m.shnenglu.com/logics-space/archive/2009/03/30/78370.html#Feedback0http://m.shnenglu.com/logics-space/comments/commentRss/78370.htmlhttp://m.shnenglu.com/logics-space/services/trackbacks/78370.htmlWhy XAML Needed?
Since WPF applications can be developed entirely in code, you may ask a perfectly natural question – why do we need XAML in the first place? The reason can be traced back to the question of efficiently implementing complex, graphically rich applications. A long time ago, developers realized that the most efficient way to develop these kinds of applications was to separate the graphics portion from the underlying code. In this way, the designers could work on the graphics, while the developers could work on the code behind the graphics. Both parts could be designed and refined separately, without any versioning headaches.
Before WPF, it was impossible to separate the graphics content from the code. For example, when you work with Windows Forms, you define every form entirely in C# code or any other language. As you add controls to the UI and configure them, the program needs to adjust the code in corresponding form classes. If you want to decorate your forms, buttons, and other controls with graphics developed by designers, you must extract the graphic content and export it to a bitmap format. This approach works for simple applications; however, it is very limited for complex, dynamic applications. Plus, graphics in bitmap format can lose their quality when they get resized.
The XAML technology introduced in WPF resolves these issues. When you develop a WPF application in Visual Studio, the window you are creating isn’t translated into code. Instead, it is serialized into a set of XAML tags. When you run the application, these tags are used to generate the objects that compose the UI.
XAML isn’t a must in order to develop WPF applications. You can implement your WPF applications entirely in code. However, the windows and controls created in code will be locked into the Visual Studio environment and available only to programmers; there is no way to separate the graphics portion from the code.
In orther words, WPF doesn’t require XAML. However, XAML opens up world of possibilities for collaboration, because many design tools understand the XAML format.
]]>鍒瘋〃http://m.shnenglu.com/logics-space/archive/2009/03/25/77829.htmlwangzhihaowangzhihaoWed, 25 Mar 2009 06:35:00 GMThttp://m.shnenglu.com/logics-space/archive/2009/03/25/77829.htmlhttp://m.shnenglu.com/logics-space/comments/77829.htmlhttp://m.shnenglu.com/logics-space/archive/2009/03/25/77829.html#Feedback0http://m.shnenglu.com/logics-space/comments/commentRss/77829.htmlhttp://m.shnenglu.com/logics-space/services/trackbacks/77829.html Cubic-free numbers II
]]>eoj 2474 Star Warshttp://m.shnenglu.com/logics-space/archive/2009/03/08/75906.htmlwangzhihaowangzhihaoSun, 08 Mar 2009 08:00:00 GMThttp://m.shnenglu.com/logics-space/archive/2009/03/08/75906.htmlhttp://m.shnenglu.com/logics-space/comments/75906.htmlhttp://m.shnenglu.com/logics-space/archive/2009/03/08/75906.html#Feedback0http://m.shnenglu.com/logics-space/comments/commentRss/75906.htmlhttp://m.shnenglu.com/logics-space/services/trackbacks/75906.html闃呰鍏ㄦ枃