]]>
]]>
]]>
]]>
//
聽(tīng)Pyin.cpp聽(tīng):聽(tīng)瀹氫箟鎺у埗鍙板簲鐢ㄧ▼搴忕殑鍏ュ彛鐐廣?br />
聽(tīng)2
//聽(tīng)3
聽(tīng)4
#include聽(tīng)
"
stdafx.h
"
聽(tīng)5
using
聽(tīng)
namespace
聽(tīng)std;聽(tīng)6
聽(tīng)7
char
聽(tīng)GetPYChar(
char
聽(tīng)
*
聽(tīng)c)聽(tīng)8
{聽(tīng)9
聽(tīng)聽(tīng)聽(tīng)聽(tīng)unsigned聽(tīng)
char
聽(tīng)
*
聽(tīng)array聽(tīng)
=
聽(tīng)
new
聽(tīng)unsigned聽(tīng)
char
[
2
];10
聽(tīng)聽(tīng)聽(tīng)聽(tīng)array[
0
]
=
c[
0
];11
聽(tīng)聽(tīng)聽(tīng)聽(tīng)array[
1
]
=
c[
1
];12
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
int
聽(tīng)i聽(tīng)
=
聽(tīng)(
short
)(array[
0
]聽(tīng)
-
聽(tīng)
'
\0
'
)聽(tīng)
*
聽(tīng)
256
聽(tīng)
+
聽(tīng)((
short
)(array[
1
]聽(tīng)
-
聽(tīng)
'
\0
'
));13
14
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xB0A1
)聽(tīng)
return
聽(tīng)
'
*
'
;15
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xB0C5
)聽(tīng)
return
聽(tīng)
'
a
'
;16
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xB2C1
)聽(tīng)
return
聽(tīng)
'
b
'
;17
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xB4EE
)聽(tīng)
return
聽(tīng)
'
c
'
;18
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xB6EA
)聽(tīng)
return
聽(tīng)
'
d
'
;19
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xB7A2
)聽(tīng)
return
聽(tīng)
'
e
'
;20
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xB8C1
)聽(tīng)
return
聽(tīng)
'
f
'
;21
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xB9FE
)聽(tīng)
return
聽(tīng)
'
g
'
;22
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xBBF7
)聽(tīng)
return
聽(tīng)
'
h
'
;23
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xBFA6
)聽(tīng)
return
聽(tīng)
'
g
'
;24
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xC0AC
)聽(tīng)
return
聽(tīng)
'
k
'
;25
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xC2E8
)聽(tīng)
return
聽(tīng)
'
l
'
;26
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xC4C3
)聽(tīng)
return
聽(tīng)
'
m
'
;27
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xC5B6
)聽(tīng)
return
聽(tīng)
'
n
'
;28
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xC5BE
)聽(tīng)
return
聽(tīng)
'
o
'
;29
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xC6DA
)聽(tīng)
return
聽(tīng)
'
p
'
;30
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xC8BB
)聽(tīng)
return
聽(tīng)
'
q
'
;31
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xC8F6
)聽(tīng)
return
聽(tīng)
'
r
'
;32
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xCBFA
)聽(tīng)
return
聽(tīng)
'
s
'
;33
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xCDDA
)聽(tīng)
return
聽(tīng)
'
t
'
;34
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xCEF4
)聽(tīng)
return
聽(tīng)
'
w
'
;35
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xD1B9
)聽(tīng)
return
聽(tīng)
'
x
'
;36
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xD4D1
)聽(tīng)
return
聽(tīng)
'
y
'
;37
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
if
聽(tīng)(聽(tīng)i聽(tīng)
<
聽(tīng)
0xD7FA
)聽(tīng)
return
聽(tīng)
'
z
'
;38
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
return
聽(tīng)
'
*
'
;39
}
40
41
int
聽(tīng)_tmain(
int
聽(tīng)argc,聽(tīng)_TCHAR
*
聽(tīng)argv[])42
{43
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
char
*
聽(tīng)szArray聽(tīng)
=
聽(tīng)
new
聽(tīng)
char
[
10
];44
聽(tīng)聽(tīng)聽(tīng)聽(tīng)strcpy(szArray,
"
鏈辯帇
"
);45
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
char
*
聽(tīng)charptr聽(tīng)
=
聽(tīng)szArray;46
聽(tīng)聽(tīng)聽(tīng)聽(tīng)cout
<<
szArray
<<
endl;47
聽(tīng)聽(tīng)聽(tīng)聽(tīng)48
聽(tīng)聽(tīng)聽(tīng)聽(tīng)cout
<<
sizeof
聽(tīng)szArray
<<
endl;49
聽(tīng)聽(tīng)聽(tīng)聽(tīng)cout
<<
GetPYChar(charptr)
<<
endl;50
聽(tīng)聽(tīng)聽(tīng)聽(tīng)cout
<<
GetPYChar(charptr
+
2
)
<<
endl;51
聽(tīng)聽(tīng)聽(tīng)聽(tīng)system(
"
PAUSE
"
);52
53
聽(tīng)聽(tīng)聽(tīng)聽(tīng)
return
聽(tīng)
0
;54
}
55
56
銆銆鑰佸悓瀛﹀仛灝忓皬鐨勭紪紼嬭璁★紝鐢?shù)璇濆忥L(fēng)爜鏈紝甯屾湜澧炲姞涓涓緭鍏ュ鍚嶆眽璇嫾闊抽瀛楁瘝鐨勬柟寮忓揩閫熸壘鍒版潯鐩紝涓嶇煡閬撳浣曞疄鐜般傛垜灝辨壘浜?jiǎn)涓涓嬶紝瑙夊緱鎸夌収榪欑鎬濊礬鏈綆鍗曘?br />銆銆
銆銆棣栧厛鍦ㄦ潯鐩殑鏁版嵁緇撴瀯涓鍔犱竴涓姩鎬佸瓧絎︿覆錛屽湪鐢熸垚鑺傜偣鐨勬椂鍊欏姩鎬佺殑鎶婂鍚嶇殑鎷奸煶鍑嗗濂姐傜瓑鍒扮敤榪欎釜鏂規(guī)硶鎼滅儲(chǔ)鏉＄洰鐨勬椂鍊欏彧闇瑕佸姣旀嫾闊崇儲(chǔ)寮曪紝榪斿洖絎﹀悎鏉′歡鐨勮妭鐐規(guī)寚閽堝氨鍙互浜?jiǎn)銆?img src ="http://m.shnenglu.com/Jedimaster/aggbug/15605.html" width = "1" height = "1" />
]]>
http://developer.nvidia.com/object/gpu-gems-3-call-for-participation.html
GPU Gems 3 Call for Participation
Following the success of GPU Gems and GPU Gems 2, NVIDIA has decided to produce a third GPU Gems volume to showcase the best new ideas and techniques for the latest programmable GPUs. We were honored that GPU Gems won the 2004 Game Developer Front Line Award and that GPU Gems 2 was a Finalist in the 2005 Game Developer Front Line Awards. What鈥檚 more, GPU Gems and GPU Gems 2 were the best-selling books聽(tīng)at the Game Developer Conference and SIGGRAPH in their respective years.
This latest GPU Gems will, like previous volumes, be hardbound and in full color. Tentatively titled GPU Gems 3, it will be edited by Hubert Nguyen, Manager of Developer Education at NVIDIA. Nguyen contributed to previous GPU Gems volumes and brings to this role vast experience in the field of computer graphics. Section editors include a team of expert NVIDIA engineers: Cyril Zeller, Evan Hart, Ignacio Casta帽o, Kevin Bjorke, Kevin Myers, and Nolan Goodnight.
NVIDIA is looking for innovative ideas from developers who are using GPUs in new ways to create stunning graphics and cutting-edge applications. GPU Gems 3 will present techniques and ideas that are broadly useful to GPU programmers and that can be integrated into their applications. And, it will continue the tradition of featuring chapters exploring non-graphics applications of the computational capabilities of GPU hardware (learn more at www.GPGPU.org). Because our goal is to provide a comprehensive set of authoritative and practical chapters, we strongly suggest submitting ideas about techniques that you have already developed and tested.
If you would like to contribute to the GPU Gems series, please read
the following submission guidelines. The deadline for proposal
submissions is Monday, December 11, 2006. If your proposal is accepted,
you will receive additional time to complete the chapter.
Guidelines for Chapter Proposal
Each chapter proposal should meet the following qualifications:
鈥⒙?strong>Subject. Your chapter can be about any topic related to applying GPUs in useful and compelling ways. For example, you may choose to write about a specific shader or technique for rendering an interesting effect, or you could write about a strategy for integrating shaders into a game engine. Or, you might discuss an interesting way to apply the GPU鈥檚 horsepower in a non-graphics area. The main requirement is that your subject has practical value for the community and that you are committed to writing a clear, concise, and informative chapter.聽(tīng)
鈥⒙?strong>Submission. Send an e-mail to articlesubmissions@nvidia.com with your proposed chapter title as the subject line, and a concise chapter description in the e-mail body (preferably no more than 300 words). To increase your chances of acceptance, we recommend that the description include screenshots or movies that demonstrate the technique in action. Ultimately, you must be able to provide a working program that demonstrates your technique. Complete source code is not necessarily required, though a self-contained example will be a plus.
鈥⒙?strong>Deadline. We will be working on an aggressive schedule, so you must submit your proposal by Monday, December 11, 2006.
Notifications will be sent out by the end of the year. If your proposal is accepted, we will contact you via e-mail and discuss our expectations for the full chapter, as well as the next steps in the process. To assist you in finalizing your chapter, we will create your figures and provide copyediting services.
Final聽(tīng)Chapter Information
鈥⒙?strong>Length. The final chapters should range from five to twenty pages of formatted book pages. This requirement accounts for figures, code samples, and page layout, so there would be approximately 200 to 300 words per page. In some cases, we may accept chapters that are shorter or longer than the suggested length, depending on the content. A chapter does not have to be long or complicated to be accepted. In fact, an idea that is simple and compelling is more likely to be accepted.
鈥⒙?strong>Rights. You must have the right to publish your work, code聽(tīng)and images (diagrams and screenshots).
We look forward to reading your submissions.鑱旀兂鍒頒腑鍥界殑鍥句功甯?jìng)鍦哄Q屽彧鏈夊徆鎭屼互錛屼粈涔堟椂鍊欐墠鏈夎繖鏍烽珮绱犺川鐨勫浘涔﹀嚭鐜幫紵鍦ㄥ浗澶栫湡濂姐?br />
]]>
璁ㄥ帉涓浗鐨勮繖浜涗釜鐮寸綉绔欙紝涓嬭澆婧愪唬鐮佺珶鐒惰繕瑕佽姳閽辯敵璇蜂粈涔堢牬VIP錛屾畩涓嶇煡sf.net涓ソ鐨勪唬鐮佸鐨勬槸銆?br />
榪欎釜鏄垜浠庡浗澶栫殑涓涓鍧涗腑鎷栧洖鏉ョ殑錛岀敱浜庤嚜宸辯殑紜洏瑁呬笉涓媁ow瀹㈡埛绔墍浠ヤ篃灝辨病鏈夋祴璇曡繃錛屾湁鏉′歡鐨勫彲浠ヨ瘯璇曠湅銆?br />
鎴戞墦綆楄姳浜涙椂闂寸敤C++閲嶆柊鍐欎竴閬嶏紝铏界劧璇村凡緇忔湁浜?jiǎn)绫讳技鐨凪angos錛屽疄鍦ㄤ笉鍠滄C# JAVA涔嬬被鐨勮櫄鎷熸満璇█銆?net浜轟笉瑕佽煩鍑烘潵鍜屾垜浜塁#涓嶆槸铏氭嫙鏈鴻蔣浠朵簯浜戯紝鎳掑緱鎼悊銆傜紪璇戝嚭鏉ョ殑浠ｇ爜寰堝皬錛岀▼搴忓惎鍔ㄩ熷害濂囨參鏃犳瘮錛岃繕蹇呴』瑕?net Frameworks鐨勬敮鎸侊紝楹葷儲(chǔ)銆?br />
鏈鏃╃殑鏄疻owEmu錛岃澶氬崟鏈虹増Wow闄勫甫鐨勪篃灝辨槸榪欎釜鎴戝氨涓嶅垪鍑哄湴鍧浜?jiǎn)锛孊T涓婂鐨勬槸銆?br />
鐒跺悗灝辨槸Wowwow錛屽彲鏄畠鐨勫唴鏍鎬唬鐮佹槸涓嶅叕寮鐨勶紝浣犲彲浠ョ湅鍒癲ecompiler浜戜簯
涓嬭澆鍦板潃
闄勪笂涓涓湁涓浜涗唬鐮佺殑Wowwow Alpha v8.3
涓嬭澆鍦板潃
鐩墠鎴戞鍦ㄥ垎鏋愮殑鏄疢angos錛岃佸發(fā)绔熺劧鍦╯f.net涓紝浠嬬粛鏄竴鐐規(guī)病鏈夋彁鍒癢orld of War錛屽彲鏄疄闄呬笂瀹冭繍琛岀殑灝辨槸瀹冦?br />鍘?a >榪欓噷鍚?br />
嬈㈣繋浜ゆ祦錛屽鏋滄?zhèn)ㄨ寰楀ソ璇峰洖澶嶆垜涓涓嬭阿璋㈠挴~~~
]]>