- x = a (mod p)
- x = b (mod q)
鍙互閲囩敤涓浗鍓╀綑瀹氱悊錛?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)
濡傛灉d 涓嶆暣闄?a - b, 鍒欐棤瑙? 鍚﹀垯
x = q * Eq * a + p * Ep * b ( mod pqd ) , 鍏朵腑 Eq * q + Ep * p = 1;
鍙互楠岀畻榪欎釜鏋勯犺В鏄傚悎涓婇潰涓や釜鏂圭▼鐨勩?br>
姣斿楠岀畻絎竴涓柟紼嬶細
棣栧厛鍙樺艦寰楀埌 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 )
涔熷彲浠ヨ瘉鏄巟 妯′笂 pqd 鍏鋒湁鍞竴瑙?br>
wangzhihao 2010-07-28 11:09 鍙戣〃璇勮
]]>wangzhihao 2010-07-19 22:02 鍙戣〃璇勮
]]>wangzhihao 2010-07-18 21:32 鍙戣〃璇勮
]]>| 棰樺彿 | 鎽樿 |
鎻愪氦嬈℃暟 / coding鑰楁椂 |
| 2313 | 妯℃澘鐨勫紛绔?鍏蜂綋浼樺寲 |
13 / --- |
| 2317 | 璧伴亾閾虹爾 |
3 / 60" |
| 2318 | 鐜【娉曞垽鐐瑰湪澶氳竟褰㈠唴錛屾悳绱㈡爲錛屾墍鏈夊洖璺?br> | --- / --- |
PKU
| 棰樺彿 | 鍒嗙被 | 娉ㄩ噴 | 閾炬帴 |
| 1012 | 閫掑綊 recursion |
joseph闂錛宩oseph鏄粡鍏哥殑閫掑綊闂 | |
| 1186 | 鍙屽悜鏋氫婦 |
鐜版灇涓懼墠涓鍗婏紝鍐嶄簩鍒嗘煡鎵懼悗涓鍗婃槸鍚︽湁瀵瑰簲鐨勫?br> | |
| 1285 | 緇勫悎 & 璁℃暟 |
鏈夐檺鍒剁殑鍙噸澶嶆帓鍒?nbsp; dp 錛坧ku 鐨?G++涓嶈瘑 unsigned long long 灝村艾錛?br> | |
| 1286 | burnside |
2154鐨勭畝鍖栫増 | |
| 1316 | 璐ㄥ洜鏁板垎瑙?nbsp; Prime- factor
|
鏈夌偣榪涘埗杞崲鐨勬劅瑙?/td> | :D |
| 1351 | 緇勫悎 & 璁℃暟 |
鏈夌浉閭婚棶棰樺彲閲嶅鐨勬帓鍒?nbsp; dfs | |
| 1430 |
stirling鏁?br> | 寰堣冨療瑙傚療鑳藉姏 |
|
| 1715 | 緇勫悎 & 璁℃暟 |
璇㈤棶絎琻浣嶄笂鏄摢涓暟錛屾瘮杈冨父瑙佺殑涓綾婚 | |
| 1718 | joseph |
璁＄畻鍊掓暟絎簩涓鏉鐨勪漢鏄皝 | |
| 1737 | 閫掑綊 recursion |
鍏跺疄涓嶆槸寰堝鏉?br> | |
| 1809 | 濂囧伓鎬?br> | 濂囧伓鎬?/td> | |
| 1811 | miller-rabin + pollard rho |
寰堥傚悎鍒濆榪欎袱縐嶇畻娉?/td> | |
| 1831 | 鏋氫婦 鏋勯?br> | 鏋氫婦鍑犻」灝忕殑錛屽啀鐢⊿= 2*P+2(p/2 + 1/2 = 1) 鍜?S = 2*P + 9(p/2 +銆錛戯紜1/3 + 1/6 = 1)鏋勯?br> | |
| 1845 | 縐у嚱鏁?/td> | 縐у嚱鏁?/td> | |
| 2034 | 鍙嶇礌鏁?nbsp; antiprime |
dfs | :D |
| 2142 | 瑙ｄ笉瀹氭柟紼?/td> | 瑙ｄ笉瀹氭暣鏁版柟紼媋x + by = c 鍏朵腑a錛宐錛宑 錛寈錛寉涓烘暣鏁?br> | |
| 2154 | burnside 嬈ф媺鏁?nbsp; 瑙傚療 |
鎯蟲硶涓嶇畻緇曞集錛屽彧瑕佺煡閬撹繖浜涚煡璇嗙偣瀹屽叏鑳借В鍑烘潵 | :D |
| 2282 | 鏁板瓧娓告垙 |
緇熻[a錛宐]涓?,1,2...9鐨勪釜鏁?br> | |
| 2429 | 璐ㄥ洜鏁板垎瑙?nbsp; pollard rho |
pollard rho | |
| 2689 | 绱犳暟 prime |
鍒瘋〃 |
:) |
| 2739 | 绱犳暟 prime |
鏆村姏 | |
| 2769 | 鍚屼綑 |
鍒瘋〃 | |
| 2891 | 鍚堝茍鍚屼綑鏂圭▼ |
鍚堝茍鍚屼綑鏂圭▼ | |
| 2917 | 璐ㄥ洜鏁?/td> | 鍒嗚В璐ㄥ洜鏁?/td> | |
| 2992 | 綰︽暟 divisor |
鍒嗚В榪炵畫鐨勬暟鐨勮川鍥犳暟 姘撮 |
|
| 3126 | 绱犳暟 prime | 鍏跺疄閲嶇偣涓嶆槸prime銆傘傘?bfs鍏抽敭 | |
| 3128 | 寰幆鑺? |
鎵捐寰?/td> | |
| 3132 | 绱犳暟 prime |
鍏跺疄閲嶇偣涓嶆槸prime銆傘傘?dp鍏抽敭 -_-! |
|
| 3252 | 鏁板瓧娓告垙 |
綆梉a,b]閲屾湁澶氬皯鏁扮殑浜岃繘鍒?姣?澶?/td> | |
| 3324 | 澶ф暟 +閽堝璇ラ鐩殑涓浜涗紭鍖?br> | mod 錛?^p-1錛夊彲浠ヤ紭鍖?/td> | |
| 3508 | 澶ф暟鍔犳硶 |
澶ф暟鍔犳硶 | |
| 3518 | 绱犳暟 prime |
浜屽垎 | |
| 3641 | 绱犳暟 prime |
miller-rabin 娉ㄦ剰 a^p%p=a 涓嶇瓑浠蜂笌 a^(p-1)%p=1 |
|
| 3725 | 鏁板瓧娓告垙 |
鍒嗗悇浣嶅崄浣嶇櫨浣嶃傘傘傜粺璁★紝 涔熷彲浠ラ氳繃浜屽垎鍋氾紝娉ㄦ剰涓嶈婧㈠嚭榪欓涓嶉『 |
wangzhihao 2010-06-23 23:19 鍙戣〃璇勮
]]>瑕佷簡瑙ｈ嚜宸辯殑闃熷弸錛岃鐔熸倝鐜板湪閭ｄ簺浜烘槸鐗涗漢錛屽鍏蟲敞鐗涗漢錛岃璐ゆ濋綈
wangzhihao 2009-09-26 20:29 鍙戣〃璇勮
]]>wangzhihao 2009-04-02 19:31 鍙戣〃璇勮
]]>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.
wangzhihao 2009-03-30 15:14 鍙戣〃璇勮
]]>Cubic-free numbers II
瑕佹眰[ L錛孯 )涓婄殑涓嶆槸Cubic鏁扮殑涓暟錛屽彂鐜版眰鍖洪棿涓婃湁澶氬皯Cubic鏁版洿娓呮櫚錛屾眰榪欑鍖洪棿闂鏈変竴縐嶆瘮杈冪粡鍏哥殑澶勭悊鎶宸э紝姹傚嚭[1錛孡)鍜孾1,R)
[L , R) = [1, R) - [1, L);
鎴戜滑鍙互鐢ㄥ鏂ユ潵姹傚尯闂碵1錛宬錛変笂鏈夊灝慍ubic鏁幫紝榪欓噷鍒瘋〃琛ㄧず瀹規枼灝卞緢鏂逛究浜?br>鍞竴娉ㄦ剰涓鐐癸紝灝辨槸鍏堟妸鍚湁i*i鐨勬暟鏍囪鎴愭棤鏁堬紝鍥犱負鎴戜滑鐨勫鏂ヤ笉浼氬幓鍒や竴涓泦鍚堣嚜宸卞拰鑷繁鐨勫叧緋伙紝鎴戜滑閮芥槸姣旇緝涓涓泦鍚堝拰鍏朵粬闆嗗悎鐨勫叧緋?br>
Coprimes
榪欎篃鏄竴閬撳鏂ラ錛屽埛琛?br>
wangzhihao 2009-03-25 14:35 鍙戣〃璇勮
]]>wangzhihao 2009-03-08 16:00 鍙戣〃璇勮
]]>