phplanguagelevel

1. php與asp.net的區別

1. PHP, Hypertext Preprocessor, 動態網頁開發語言。
PHP，Hypertext Preprocessor，最初在95年問世（那時以前叫Personal Home Page）。PHP最初是製作動態網頁的伺服器端腳本語言，但

現在PHP已經可以作為command line運行有GUI的standalone的程序。現在是PHP Group在開發和管理PHP的規則，功能等。但PHP大都用在

dynamic webpage scripting上，好象沒聽過誰用它開發desktop application。

PHP使用率是製作動態網頁的幾種語言（JSP，ASP，ASP.NET, ColdFusion, Ruby, SHTML）中最高的。因為PHP在95年已經問世至今，以有

相當數量的開發者。我們熟知的國際權威網路全書Wikipedia有90%用PHP寫的，而且國外流行多年的「校內網」FaceBook 也全部用PHP寫

的，同時Yahoo, Sony官方，Pepsi百事官方這些網站都是用PHP的。根據維基網路（Wikipedia）的說法，PHP被超過20,000,000的網站所

用，被超過1,000,000的網頁伺服器所用。目前到2008五月，PHP最新版本為5.2.6。

PHP不僅使用率高，而且能兼容各類平台。它可以在大多數網頁伺服器上運行（如：MS IIS，Apache），大多數操作系統上運行（如：

Windows, UNIX, linux）。而且PHP支持很大多數牌子的資料庫：MySQL, Informix, Oracle, Sybase, Solid, PostgreSQL, Gerneric

ODBC等。

結構方面，雖比JSP，ASP.NET差點，PHP也有很多Framework可用。微軟的ASP.NET結構是出名的，JSP的MVC結構也很厲害，所以開發大網

站ASP.NET，JSP都很快。而PHP Group也為此付出很大努力，來開發自己特有的結構適應不同類型的大網站的需求。常見的PHP的

Framework有：CakePHP, PRADO, Symfony, Zend等。

另外LAMP結構，是PHP最常用的開發模式，即是配合Linux, Apache, MySQL, PHP，合稱LAMP。

2. ASP（Active Server Pages）, ASP.NET 兩個分別是 動態網頁開發語言，動態網頁開發語言和結構
(1) 關於ASP的淘汰
ASP, Active Server Pages已經過時了, 但因為其出現的早，96年就有了，所以現在有些中小網站還用（但，使用最多最廣的是PHP，最

初於95年現世。ASP是微軟第一代動態網頁開發語言，只能在Windows系統 + MS IIS伺服器平台下運行。

Wikipedia, Facebook, 網路等都用PHP，PHP學習的簡單度和ASP差不多；JSP稍微難點，JSP用的一般都是銀行，購物等安全性較高的網站

，Google也用JSP）。但隨著開發者的各種需求，ASP以後可以被ASP.NET取代，因為微軟停止對其的一切技術維護與功能更新。ASP.NET是

革新版本的ASP（注意是「革新版本」，而非「改進版本」），或者說是完全新一代的Dynamic Web Scripting。

ASP代表著傳統的dynamic web scripting，與ASP.NET沒什麼關系，學了確實也沒用。因為ASP不象CGI（Common Gateway Interface），

CGI是動態網站製作的始祖，所有ASP，JSP，PHP什麼的都根據CGI演化而來，而且ASP，PHP，JSP都包含了些 CGI的東西；而ASP卻沒有被

衍生出任何新技術，ASP.NET也不算基於ASP，只能說ASP.NET開發理念，library，功能完全是基於.NET的其它組件。

其實PHP，JSP，ASP明白其中一種，其它的都很容易學會了。如果非要學學傳統的dynamic web scripting，那就學學PHP吧，不比ASP難，

但比ASP功能多，穩定性好，PHP5運行速度也比ASP快很多（JSP稍難因為要學點 java）。學了PHP或JSP什麼的，對學ASP.NET有好處，而

且還可以直接用PHP，JSP進行開發。去google差差英文資源，有評價PHP 最好的，有評價JSP最好的，還從沒有聽誰說過ASP最好。

ASP.NET畢竟在.NET中，所以ASP.NET還是有相當地位的。

(2). 關於ASP.NET的優勢
ASP.NET是微軟.NET Framework的一部分。伴隨.NET 1.0在2002的問世，ASP.NET也出現在動態網頁開發語言的家族中（與

PHP,JSP,ColdFusion, Ruby, SHTML等並行了）。

功能上，ASP.NET比ASP有更強大的library, 更好的穩定性。 ASP.NET可以使用.NET Framework中所有組件（也就是說.NET能實現的，

ASP.NET一樣能實現），功能上顯然強大於傳統功能單調的ASP。最強的技術支持Web Service, 而且有.NET的所有library做後盾。而且

ASP.NET 在.NET 3.5中還有微軟專門為AJAX開發的功能--ASP.NET AJAX。

結構上，傳統的ASP把所有代碼混為一團，簡單的用<%%>把HTML和VBScript（或JScript）分開，實現動態輸出 HTML。因為ASP.NET模仿

JSP的MVC網頁結構，微軟為ASP.NET開發了自己的Code-Behind結構，將 presentation（文件拓展名：.aspx）和business logic(文件拓

展名：.cs或.vb等)分離。同時Code-Behind模式也實現了讓ASP.NET開發者用.NET中最普通Winform的開發模式來開發網站，方便非網頁開

發者製作動態網站。所以ASP.NET更容易維護，比ASP更適合於Enterprise Level 的大網站開發。

由於ASP.NET比JSP，PHP等更接近於.NET Winform的開發。如Tree View, Datagrid View（即高級Table）等高級UI，都可以直接用

ASP.NET中的Web Control來實現，這比傳統的使用JavaScript + XTHML + CSS的DHTML開發方式簡單不少，也更好維護。同時ASP.NET開發

這可以定義自己的User Control，製作自己特別的一種UI（如網站LOGO，版權等部分），而且此User Control可以被存為.ascx文件，方

便讓每一頁(.aspx)來使用。

運行速度上，ASP.NET模仿了JSP的預編譯機制(Pre-Compile)。使編譯好的代碼(MSIL語言)在網頁伺服器上運行。這樣比傳統的ASP，傳統

PHP（PHP4以前版本）更快，因為傳統的ASP是直接運行開發者寫的Script，相當於每運行一次，就得編譯一次那麼慢。 ASP.NET可以用

VB, C#, J#等所有.NET Framework的語言開發.(但其實每種語言做的東西都一樣... 就象山東話, 東北話, 寫出來都是中文:)

不過ASP.NET對出學者可能有點難. 因為它其實在模擬desktop application development，即Winforms開發的模式, 不象傳統的JSP,

PHP, ASP這樣容易明白。傳統的Dynamic Server Scripting, 象PHP 5, 這是現在最簡單的, 最有效的了。（ 那個JSP也不難. 如果有錢

還可以考慮下Adobe ColdFusion。）

ASP.NET的新潮的Dynamic Server Scripting, 在其帶動下SUN也推出自己的JavaServer Faces (其實是拓展JSP，但JSF無法取代JSP), 和

ASP.NET很象, 也有很多Web Control（JTable, JTree），同時JSF也曾強了對WEB SERVCIE的支持, 也很適合ENTERPRISE LEVEL 的網站。

(3). ASP與ASP.NET的優劣總結：
-- ASP已經被微軟停止更新；ASP.NET卻在.NET（1.0, 2.0, 3.0, 3.5）中突飛猛進；
-- ASP在96年出現，並沒有引領一個潮流，PHP，ColdFusion都出現於95年，引領了整個潮流；ASP.NET引領新的動態網站開發潮流，SUN

的JSF（JavaServer Faces）就是與ASP.NET極其相似；
-- ASP大多被用在是中小網站；PHP被Wikipedia, Facebook, 網路所用，JSP被GOOGLE所用；
-- ASP不支持Web Service; ASP.NET支持Web Service。要是了解.NET中的Web Service在大組織系統中的重要性，就能立桿見影的看出差

距
-- ASP開發AJAX比較麻煩；而ASP.NET專門用AJAX控制項，更方便。要是了解Web 2.0，那麼AJAX是什麼地位，就不用我說了吧。
-- ASP.NET模仿JSP，是pre-compile的；ASP不compile，直接運行Script的速度顯然沒有compile之後的快。
-- ASP.NET的唯一缺點，就是開發用的IDE--Visual Studio Professional比較貴（express版免費的功能太少）；ASP的唯一優點是，其

學起來最簡單，跟PHP一樣簡單，比JSP簡單，更比ASP.NET簡單幾倍。

3. .NET Framework
.NET Framework的概念就大了。.NET Framework是微軟開發的一種軟體開發技術。主要用來開發MS Windows系統上的各類軟體。.NET主要

包含一個龐大的library（解決常見編程問題）和一個virtual machine（管理程序的運行）。可以說Windows是微軟的命根：），所

以.NET就是微軟佔領軟體市場的關鍵。

.NET Framework的library叫做BCL, Base Class Library，包含了在各種領域的大范圍的編程需要，如user interface用戶界面，data

access數據接入，database connectivity, cryptography, web application development網站開發，numeric algorithms數學計算，

network communications網路交流等。開發者利用各種BSL來構成自己的代碼，進而開發出多樣的應用程序。

.NET寫出的程序在CLR, Common Language Runtime上運行。CLR是一個application virtual machine來幫助運行開發者寫的程序。CLR提

供很多重要功能，如：security安全，memory management內存管理，exception handling錯誤控制。

BSL，CLR構成了強大的.NET Framework。

.NET Framework主要安裝在Windows Server 2008, Windows Vista。小版本的.NET Framework還安裝在Windows Mobile系統上。但是家用

Windows XP等系統一樣可以安裝.NET Framework來運行用.NET寫的程序。

平時在學校學習，通常學習.NET中的三個主要技術：Winforms（桌面應用程序開發，就是平時普通程序如QQ，Skype可以用它，但其實QQ

用C,C++寫的）, ASP.NET（網頁，平時在IE，FireFox上看的網頁可以用它）, ADO.NET（接入資料庫，處理相關數據）。但.NET不是一種

語言。寫.NET程序可以用任何.NET支持的語言，如：C#, VB.NET, J#等等。明白其中一種就可以了。

.NET概念挺大，東西也非常非常多。與之相似的技術有SUN的Java技術(分三個技術部分Java SE, Java EE, Java ME)。

2. php源碼高手請進!!!!

1、安裝php運行環境
2、安裝資料庫
3、將網站目錄指向網站源碼所在的文件夾

詳細步驟如下：
＝＝＝＝＝＝＝＝＝＝＝
＝＝＝＝＝＝＝＝＝＝＝
＝＝＝＝＝＝＝＝＝＝＝
Windows 2000/XP/2003 下 IIS+PHP+MySQL+Zend Optimizer+GD庫+phpMyAdmin安裝配置
關鍵詞：Windows IIS下配置支持PHP+MYSQL
Apache下支持PHP的配置方法比較簡單，這里就不寫了
一般WIN主機推薦PHP環境組合：PHP4.4.x+MySQL4.0.x，故以下關於PHP4.4.x+MySQL4.0.x組合的安裝以藍色文字顯示，如果你只需要安裝PHP4.4.x+MySQL4.0.x的組合只看藍色文字的相關內容即可
當然喜歡體驗的或者WIN2003系統也可體驗嘗試最新的版本，推薦組合PHP5.1.x+MYSQL5.0.x/MySQL4.1.x
一、軟體准備：以下均為截止2006-1-20的最新正式版本，下載地址也均長期有效
1.PHP，推薦PHP4.4.0的ZIP解壓版本：
PHP（4.4.0）：

http://cn.php.net/get/php-4.4.0-Win32.zip/from/a/mirror

[供選用]：
PHP（5.1.2）：

http://cn.php.net/get/php-5.1.2-Win32.zip/from/a/mirror

2.MySQL，配合PHP4推薦MySQL4.0.26的WIN系統安裝版本：
MySQL（4.0.26）：

http://download.discuz.net/mysql-4.0.26-win32.zip

http://dev.mysql.com/get/Downloa ... p/from/pick#mirrors

[供選用]：
MySQL（4.1.16）：

http://www.skycn.com/soft/24418.html

http://dev.mysql.com/get/Downloa ... p/from/pick#mirrors

MySQL（5.0.18）：

http://www.skycn.com/soft/1262.html

http://dev.mysql.com/get/Downloa ... p/from/pick#mirrors

3.Zend Optimizer，當然選擇當前最新版本拉：
Zend Optimizer（2.6.2）：

http://www.zend.com/store/free_download.php?pid=13

（Zend軟體雖然免費下載，但需要注冊用戶，這里提供本人注冊好的帳戶名:
xqincom
和密碼:
xqin.com
，方便大家使用，請不要修改本帳號或將本帳戶用於其他費正當途徑，謝謝！）
登陸後選擇Windows x86的Platform版本，如最新版本2.6.2

https://www.zend.com/store/getfreefile.php?pid=13&zbid=995

4.phpMyAdmin，當然同樣選擇當前最新版本拉，注意選擇for Windows 的版本哦：
phpMyAdmin（2.7.0）：

http://www.crsky.com/soft/4190.html

http://www.skycn.com/soft/10687.html

假設 C:\ 為你現在所使用操作系統的系統盤，如果你目前操作系統不是安裝在 C:\ ，請自行對應修改相應路徑。同時由於C盤經常會因為各種原因重裝系統，數據放在該盤不易備份和轉移
選擇安裝目錄，故本文將所有PHP相關軟體均安裝到D:\php目錄下，這個路徑你可以自行設定，如果你安裝到不同目錄涉及到路徑的請對應修改以下的對應路徑即可
二、安裝 PHP ：本文PHP安裝路徑取為D:\php\php4\
(為避混淆，PHP5.1.x版本安裝路徑取為D:\php\php5\)
（1）、下載後得到 php-4.4.0-Win32.zip ，解壓至D:\php目錄，將得到二級目錄php-4.4.0-Win32，改名為 php4，也即得到PHP文件存放目錄D:\php\php4\[如果是PHP5.1.2，得到的文件是php-5.1.2-Win32.zip，直接全 部接壓至D:\php\php5目錄即可得PHP文件存放目錄D:\php\php5\
]；
（2）、再將D:\php\php4目錄和D:\php\php4\dlls目錄[
PHP5為D:\php\php5\
]下的所有dll文件拷到c:\Windows\system32(win2000系統為 c:/winnt/system32/)下，覆蓋已有的dll文件；

（3）、將php.ini-dist用記事本打開，利用記事本的查找功能搜索並修改：
搜索
CODE:

[Copy to clipboard]

register_globals = Off，將 Off 改成 On ，即得到register_globals = On；
註：這個對應PHP的全局變數功能，考慮有很多PHP程序需要全局變數功能故打開，打開後請注意-PHP程序的嚴謹性，如果不需要推薦不修改保持默認Off狀態
再搜索
CODE:

[Copy to clipboard]

extension_dir =，並將其路徑指到你的 PHP 目錄下的 extensions 目錄，比如：修改extension_dir = "./"為extension_dir = "D:/php/php4/extensions/" ；
PHP擴展功能目錄[PHP5對應修改為extension_dir = "D:/php/php5/ext/"]
在D:\php下建立文件夾並命名為tmp
查找
CODE:

[Copy to clipboard]

;upload_tmp_dir =將;upload_tmp_dir該行的注釋符，即前面的分號「；」去掉，使該行在php.ini文檔中起作用。upload_tmp_dir是用來定 義上傳文件存放的臨時路徑，在這里你還可以修改並給其定義一個絕對路徑，這里設置的目錄必須有讀寫許可權。
這里我設置為upload_tmp_dir = D:/php/tmp (即前面建立的這個文件夾呵)
搜索找到
CODE:

[Copy to clipboard]

;Windows Extensions將下面一些常用的項前面的;去掉
CODE:

[Copy to clipboard]

;extension=php_mbstring.dll
CODE:

[Copy to clipboard]

;extension=php_curl.dll
CODE:

[Copy to clipboard]

;extension=php_dbase.dll
CODE:

[Copy to clipboard]

;extension=php_gd2.dll
這個是用來支持GD庫的，一般需要，必選
CODE:

[Copy to clipboard]

;extension=php_ldap.dll
CODE:

[Copy to clipboard]

extension=php_zip.dll去掉前面的";"
對於PHP5的版本還需要查找
CODE:

[Copy to clipboard]

;extension=php_mysql.dll並同樣去掉前面的";"
這個是用來支持MYSQL的，由於PHP5將MySQL作為一個獨立的模塊來載入運行的，故要支持MYSQL必選
查找
CODE:

[Copy to clipboard]

;session.save_path =去掉前面;號,本文這里將其設置置為
session.save_path = D:/php/tmp
其他的你可以選擇需要的去掉前面的;然後將該文件另存為為php.ini到C:\Windows ( Windows 2000 下為 C:\WINNT)目錄下，注意更改文件後綴名為ini，得到C:\Windows\php.ini ( Windows 2000 下為 C:\WINNT\php.ini)
本人配置成功後的PHP.INI文件示例可供大家參考：

http://xqin.com/iis/php4/php.ini

對應版本為PHP4.4.0

http://xqin.com/iis/php5/php.ini

對應版本為PHP5.1.12
若路徑等和本文相同可直接保存到C:\Windows ( Windows 2000 下為 C:\WINNT)目錄下使用若路徑等和本文相同可直接保存到C:\Windows ( Windows 2000 下為 C:\WINNT)目錄下使用
一些朋友經常反映無法上傳較大的文件或者運行某些程序經常超時，那麼可以找到C:\Windows ( Windows 2000 下為 C:\WINNT)目錄下的PHP.INI以下內容修改：
max_execution_time = 30 ; 這個是每個腳本運行的最長時間，可以自己修改加長，單位秒
max_input_time = 60 ; 這是每個腳本可以消耗的時間，單位也是秒
memory_limit = 8M ; 這個是腳本運行最大消耗的內存，也可以自己加大
upload_max_filesize = 2M ; 上載文件的最大許可大小 ，自己改吧，一些圖片論壇需要這個更大的值
（4）、配置 IIS 使其支持 PHP ：
首先必須確定系統中已經正確安裝 IIS ，如果沒有安裝，需要先安裝 IIS ，安裝步驟如下：
Windows 2000/XP 下的 IIS 安裝：
用 Administrator 帳號登陸系統，將 Windows 2000 安裝光碟插入光碟驅動器，進入「控制面板」點擊「添加/刪除程序」，再點擊左側的「添加/刪除 Windows 組件」，在彈出的窗口中選擇「Internet 信息服務（IIS）」，點下面的「詳細信息」按鈕，選擇組件，以下組件是必須的：「Internet 服務管理器」、「World Wide Web 伺服器」和「公用文件」，確定安裝。
安裝完畢後，在「控制面板」的「管理工具」里打開「服務」，檢查「IIS Admin Service」和「World Wide Web Publishing Service」兩項服務，如果沒有啟動，將其啟動即可。
Windows 2003 下的 IIS 安裝：
由於 Windows 2003 的 IIS 6.0 集成在應用程序伺服器中，因此安裝應用程序伺服器就會默認安裝 IIS 6.0 ，在「開始」菜單中點擊「配置您的伺服器」，在打開的「配置您的伺服器向導」里左側選擇「應用程序伺服器（IIS，ASP.NET）」，單擊「下一步」出 現「應用程序伺服器選項」，你可以選擇和應用程序伺服器一起安裝的組件，默認全選即可，單擊「下一步」，出現「選擇總結界面」，提示了本次安裝中的選項， 配置程序將自動按照「選擇總結」中的選項進行安裝和配置。

打開瀏覽器，輸入：

http://localhost/

，看到成功頁面後進行下面的操作：
PHP 支持 CGI 和 ISAPI 兩種安裝模式，CGI 更消耗資源，容易因為超時而沒有反映，但是實際上比較安全，負載能力強，節省資源，但是安全性略差於CGI，本人推薦使用 ISAPI 模式。故這里只解介紹 ISAPI 模式安裝方法：(以下的截圖因各個系統不同，窗口界面可能不同，但對應選項卡欄目是相同的，只需找到提到的對應選項卡即可)
在「控制面板」的「管理工具」中選擇「Internet 服務管理器」，打開 IIS 後停止服務，對於WIN2000系統在」Internet 服務管理器「的下級樹一般為你的」計算機名「上單擊右鍵選擇「屬性」，再在屬性頁面選擇主屬性」WWW 服務「右邊的」編輯「

對於XP/2003系統展開」Internet 服務管理器「的下級樹一般為你的」計算機名「選擇」網站「並單擊右鍵選擇「屬性」

在彈出的屬性窗口上選擇「ISAPI 篩選器」選項卡找到並點擊「添加」按鈕，在彈出的「篩選器屬性」窗口中的「篩選器名稱」欄中輸入：PHP ，再將瀏覽可執行文件使路徑指向 php4isapi.dll 所在路徑，如本文中為：D:\php\php4\sapi\php4isapi.dll[PHP5對應路徑為D:\php\php5\ php5isapi.dll
]。

打開「站點屬性」窗口的「主目錄」選項卡，找到並點擊「配置」按鈕

在彈出的「應用程序配置」窗口中的」應用程序映射「選項卡找到並點擊「添加」按鈕新增一個擴展名映射，在彈出的窗口中單擊「瀏覽」將可執行文件指向 php4isapi.dll 所在路徑，如本文中為：D:\php\php4\sapi\php4isapi.dll[
PHP5對應路徑為D:\php\php5\php5isapi.dll
]，擴展名為 .php ，動作限於」GET,HEAD,POST,TRACE「，將「腳本引擎」「確認文件是否存在」選中，然後一路確定即可。如果還想支持諸如 .php3 ，.phtml 等擴展名的 PHP 文件，可以重復「添加」步驟，對應擴展名設置為需要的即可如.PHPX。

此步操作將使你伺服器IIS下的所有站點都支持你所添加的PHP擴展文件，當然如果你只需要部分站點支持PHP，只需要在「你需要支持PHP的Web站 點」比如「默認Web站點」上單擊右鍵選擇「屬性」，在打開的「 Web 站點屬性」「主目錄」選項卡，編輯或者添加PHP的擴展名映射即可或者將你步需要支持PHP的站點中的PHP擴展映射刪除即可

再打開「站點屬性」窗口的「文檔」選項卡，找到並點擊「添加」按鈕，向默認的 Web 站點啟動文檔列表中添加 index.php 項。您可以將 index.php 升到最高優先順序，這樣，訪問站點時就會首先自動尋找並打開 index.php 文檔。

確定 Web 目錄的應用程序設置和執行許可中選擇為純腳本，然後關閉 Internet 信息服務管理器
對於2003系統還需要在「Internet 服務管理器」左邊的「WEB服務擴展」中設置ISAPI 擴展允許，Active Server Pages 允許

完成所有操作後，重新啟動IIS服務。
在CMD命令提示符中執行如下命令：
net stop w3svc
net stop iisadmin
net start w3svc
到此，PHP的基本安裝已經完成，我們已經使網站支持PHP腳本。
檢查方法是，在 IIS 根目錄下新建一個文本文件存為 php.php ，內容如下：
CODE:

[Copy to clipboard]

打開瀏覽器，輸入：

http://localhost/php.php

，將顯示當前伺服器所支持 PHP 的全部信息，可以看到 Server API的模式為：ISAPI 。

或者利用PHP探針檢測

http://xqin.com/index.rar

下載後解壓到你的站點根目錄下並訪問即可

三、安裝 MySQL ：

對於MySQL4.0.26下載得到的是mysql-4.0.26-win32.zip，解壓到mysql-4.0.26-win32目錄雙擊執行 Setup.exe 一路Next下一步，選擇安裝目錄為D:\php\MySQL和安裝方式為Custom自定義安裝，再一路Next下一步即可。

安裝完畢後，在CMD命令行中輸入並運行：
CODE:

[Copy to clipboard]

D:\php\MySQL\bin\mysqld-nt -install如果返回Service successfully installed.則說明系統服務成功安裝
新建一文本文件存為MY.INI，編輯配置MY.INI，這里給出一個參考的配置
（

http://xqin.com/iis/my.ini

可以下載後直接保存到WINDOWS或者WINNT目錄使用）
CODE:

[Copy to clipboard]

[mysqld]
basedir=D:/php/MySQL
#MySQL所在目錄
datadir=D:/php/MySQL/data
#MySQL資料庫所在目錄，可以更改為其他你存放資料庫的目錄
#language=D:/php/MySQL/share/your language directory
#port=3306
set-variable = max_connections=800
skip-locking
set-variable = key_buffer=512M
set-variable = max_allowed_packet=4M
set-variable = table_cache=1024
set-variable = sort_buffer=2M
set-variable = thread_cache=64
set-variable = join_buffer_size=32M
set-variable = record_buffer=32M
set-variable = thread_concurrency=8
set-variable = myisam_sort_buffer_size=64M
set-variable = connect_timeout=10
set-variable = wait_timeout=10
server-id = 1
[isamchk]
set-variable = key_buffer=128M
set-variable = sort_buffer=128M
set-variable = read_buffer=2M
set-variable = write_buffer=2M
[myisamchk]
set-variable = key_buffer=128M
set-variable = sort_buffer=128M
set-variable = read_buffer=2M
set-variable = write_buffer=2M
[WinMySQLadmin]
Server=D:/php/MySQL/bin/mysqld-nt.exe保存後復制此MY.INI文件到C:\Windows ( Windows 2000 下為 C:\WINNT)目錄下
回到CMD命令行中輸入並運行：
CODE:

[Copy to clipboard]

net start mysqlMySQL 服務正在啟動 .
MySQL 服務已經啟動成功。
將啟動 MySQL 服務；
DOS下修改ROOT密碼：當然後面安裝PHPMYADMIN後修改密碼也可以通過PHPMYADMIN修改
格式：mysqladmin -u用戶名 -p舊密碼 password 新密碼
例：給root加個密碼xqin.com
首先在進入CMD命令行，轉到MYSQL目錄下的bin目錄，然後鍵入以下命令
mysqladmin -uroot password xqin.com
註：因為開始時root沒有密碼，所以-p舊密碼一項就可以省略了。
D:\php\MySQL\bin>mysqladmin -uroot password xqin.com回車後ROOT密碼就設置為xqin.com了
如果你下載的是 MySQL5.x或者MySQL4.1.x，例mysql-5.0.18-win32：解壓後雙擊執行 Setup.exe ，Next下一步後選擇Custom自定義安裝，再Next下一步選擇安裝路徑這里我們選擇D:\php\MySQL，繼續Next下一步跳過Sign UP完成安裝。

安裝完成後會提示你是不是立即進行配置，選擇是即可進行配置。當然一般安裝後菜單裡面也有配置向導MySQL Server Instance Config Wizar，運行後按下面步驟配置並設置ROOT密碼即可
Next下一步後選擇Standard Configuration

Next下一步，鉤選Include .. PATH

Next下一步，設置ROOT密碼，建議社設置復雜點，確保伺服器安全！

Apply完成後將在D:\php\MySQL目錄下生成MY.INI配置文件，添加並啟動MySQL服務

如果你的MySQL安裝出錯，並且卸載重裝仍無法解決，這里提供一個小工具系統服務管理器

http://xqin.com/iis/ser.rar

，用於卸載後刪除存在的MYSQL服務，重起後再按上述說明進行安裝一般即可成功安裝

四、安裝 Zend Optimizer ：

下載後得到 ZendOptimizer-2.6.2-Windows-i386.exe ，直接雙擊安裝即可，安裝過程要你選擇 Web Server 時，選擇 IIS ，然後提示你是否 Restart Web Server，選擇是，完成安裝之前提示是否備份 php.ini ，點確定後安裝完成。我這里安裝到D:\php\Zend

以下兩步的目錄根據你自己的默認WEB站點目錄來選，當然也可以選擇到D:\php\Zend目錄

Zend Optimizer 的安裝向導會自動根據你的選擇來修改 php.ini 幫助你啟動這個引擎。下面簡單介紹一下 Zend Optimizer 的配置選項。以下為本人安裝完成後 php.ini 里的默認配置代碼（分號後面的內容為注釋）：
zend_extension_ts="D:\php\Zend\lib\ZendExtensionManager.dll"
;Zend Optimizer 模塊在硬碟上的安裝路徑。
zend_extension_manager.optimizer_ts="D:\php\Zend\lib\Optimizer-2.6.2"
;優化器所在目錄，默認無須修改。
zend_optimizer.optimization_level=1023
;優化程度，這里定義啟動多少個優化過程，默認值是 15 ，表示同時開啟 10 個優化過程中的 1-4 ，我們可以將這個值改為 1023 ，表示開啟全部10個優化過程。
調用phpinfo()函數後顯示：
Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies with Zend Extension Manager v1.0.9, Copyright (c) 2003-2006, by Zend Technologies with Zend Optimizer v2.6.2, Copyright (c) 1998-2006, by Zend Technologies 則表示安裝成功。

3. php language level選擇哪一個

肯定選PHP了，現在都主流這個了。

4. 【求助】安裝並且配置好apache＋php＋mysql之後該咋辦捏

#
# Based upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://www.apache.org/docs/> for detailed information about
# the directives.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# After this file is processed, the server will look for and process
# C:/Apache/Apache/conf/srm.conf and then C:/Apache/Apache/conf/access.conf
# unless you have overridden these with ResourceConfig and/or
# AccessConfig directives here.
#
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "/usr/local/apache" will be interpreted by the
# server as "/usr/local/apache/logs/foo.log".
#
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
# If a drive letter is omitted, the drive on which Apache.exe is located
# will be used by default. It is recommended that you always supply
# an explicit drive letter in absolute paths, however, to avoid
# confusion.
#

### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#

#
# ServerType is either inetd, or standalone. Inetd mode is only supported on
# Unix platforms.
#
ServerType standalone

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
ServerRoot "C:/Apache/Apache"

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
#
PidFile logs/httpd.pid

#
# ScoreBoardFile: File used to store internal server process information.
# Not all architectures require this. But if yours does (you'll know because
# this file will be created when you run Apache) then you *must* ensure that
# no two invocations of Apache share the same scoreboard file.
#
ScoreBoardFile logs/apache_runtime_status

#
# In the standard configuration, the server will process httpd.conf (this
# file, specified by the -f command line option), srm.conf, and access.conf
# in that order. The latter two files are now distributed empty, as it is
# recommended that all directives be kept in a single file for simplicity.
# The commented-out values below are the built-in defaults. You can have the
# server ignore these files altogether by using "/dev/null" (for Unix) or
# "nul" (for Win32) for the arguments to the directives.
#
#ResourceConfig conf/srm.conf
#AccessConfig conf/access.conf

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# ring a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 15

#
# Apache on Win32 always creates one child process to handle requests. If it
# dies, another child process is created automatically. Within the child
# process multiple threads handle incoming requests. The next two
# directives control the behaviour of the threads and processes.
#

#
# MaxRequestsPerChild: the number of requests each child process is
# allowed to process before the child dies. The child will exit so
# as to avoid problems after prolonged use when Apache (and maybe the
# libraries it uses) leak memory or other resources. On most systems, this
# isn't really needed, but a few (such as Solaris) do have notable leaks
# in the libraries. For Win32, set this value to zero (unlimited)
# unless advised otherwise.
#
# NOTE: This value does not include keepalive requests after the initial
# request per connection. For example, if a child process handles
# an initial request and 10 subsequent "keptalive" requests, it
# would only count as 1 request towards this limit.
#
MaxRequestsPerChild 0

#
# Number of concurrent threads (i.e., requests) the server will allow.
# Set this value according to the responsiveness of the server (more
# requests active at once means they're all handled more slowly) and
# the amount of system resources you'll allow the server to consume.
#
ThreadsPerChild 50

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
#Listen 3000
#Listen 12.34.56.78:80

#
# BindAddress: You can support virtual hosts with this option. This directive
# is used to tell the server which IP address to listen to. It can either
# contain "*", an IP address, or a fully qualified Internet domain name.
# See also the <VirtualHost> and Listen directives.
#
#BindAddress *

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a mole which was built as a DSO you
# have to place corresponding `LoadMole' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Please read the file README.DSO in the Apache 1.3 distribution for more
# details about the DSO mechanism and run `apache -l' for the list of already
# built-in (statically linked and thus always available) moles in your Apache
# binary.
#
# Note: The order in which moles are loaded is important. Don't change
# the order below without expert advice.
#
# Example:
# LoadMole foo_mole moles/mod_foo.so
#
#LoadMole vhost_alias_mole moles/mod_vhost_alias.so
#LoadMole mime_magic_mole moles/mod_mime_magic.so
#LoadMole status_mole moles/mod_status.so
#LoadMole info_mole moles/mod_info.so
#LoadMole speling_mole moles/mod_speling.so
#LoadMole rewrite_mole moles/mod_rewrite.so
#LoadMole anon_auth_mole moles/mod_auth_anon.so
#LoadMole dbm_auth_mole moles/mod_auth_dbm.so
#LoadMole digest_auth_mole moles/mod_auth_digest.so
#LoadMole digest_mole moles/mod_digest.so
#LoadMole proxy_mole moles/mod_proxy.so
#LoadMole cern_meta_mole moles/mod_cern_meta.so
#LoadMole expires_mole moles/mod_expires.so
#LoadMole headers_mole moles/mod_headers.so
#LoadMole usertrack_mole moles/mod_usertrack.so
#LoadMole unique_id_mole moles/mod_unique_id.so

#
# Reconstruction of the complete mole list from all available moles
# (static and shared ones) to achieve correct mole execution order.
#
# The moles listed below, without a corresponding LoadMole directive,
# are static bound into the standard Apache binary distribution for Windows.
#
# Note: The order in which moles are loaded is important. Don't change
# the order below without expert advice.
#
# [WHENEVER YOU CHANGE THE LOADMODULE SECTION ABOVE, UPDATE THIS TOO!]
ClearMoleList
#AddMole mod_vhost_alias.c
AddMole mod_env.c
AddMole mod_log_config.c
#AddMole mod_mime_magic.c
AddMole mod_mime.c
AddMole mod_negotiation.c
#AddMole mod_status.c
#AddMole mod_info.c
AddMole mod_include.c
AddMole mod_autoindex.c
AddMole mod_dir.c
AddMole mod_isapi.c
AddMole mod_cgi.c
AddMole mod_asis.c
AddMole mod_imap.c
AddMole mod_actions.c
#AddMole mod_speling.c
AddMole mod_userdir.c
AddMole mod_alias.c
#AddMole mod_rewrite.c
AddMole mod_access.c
AddMole mod_auth.c
#AddMole mod_auth_anon.c
#AddMole mod_auth_dbm.c
#AddMole mod_auth_digest.c
#AddMole mod_digest.c
#AddMole mod_proxy.c
#AddMole mod_cern_meta.c
#AddMole mod_expires.c
#AddMole mod_headers.c
#AddMole mod_usertrack.c
#AddMole mod_unique_id.c
AddMole mod_so.c
AddMole mod_setenvif.c

#
# ExtendedStatus controls whether Apache will generate "full" status
# information (ExtendedStatus On) or just basic information (ExtendedStatus
# Off) when the "server-status" handler is called. The default is Off.
#
#ExtendedStatus On

### Section 2: 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# Port: The port to which the standalone server listens. Certain firewall
# procts must be configured before Apache can listen to a specific port.
# Other running httpd servers will also interfere with this port. Disable
# all firewall, security, and other services if you encounter problems.
# To help diagnose problems use the Windows NT command NETSTAT -a
#
Port 80

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents.
#
ServerAdmin [email protected]

#
# ServerName allows you to set a host name which is sent back to clients for
# your server if it's different than the one the program would get (i.e., use
# "www" instead of the host's real name).
#
# Note: You cannot just invent host names and hope they work. The name you
# define here must be a valid DNS name for your host. If you don't understand
# this, ask your network administrator.
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address (e.g., http://123.45.67.89/)
# anyway, and this will make redirections work in a sensible way.
#
# 127.0.0.1 is the TCP/IP local loop-back address, often named localhost. Your
# machine always knows itself by this address. If you use Apache strictly for
# local testing and development, you may use 127.0.0.1 as the server name.
#
ServerName localhost

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "C:/Apache/Apache/htdocs"

#
# Each directory to which Apache has access, can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# permissions.
#
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "C:/Apache/Apache/htdocs">

#
# This may also be "None", "All", or any combination of "Indexes",
# "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
Options Indexes FollowSymLinks MultiViews

#
# This controls which options the .htaccess files in directories can
# override. Can also be "All", or any combination of "Options", "FileInfo",
# "AuthConfig", and "Limit"
#
AllowOverride None

#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all
</Directory>

#
# UserDir: The name of the directory which is appended onto a user's home
# directory if a ~user request is received.
#
# Under Win32, we do not currently try to determine the home directory of
# a Windows login, so a format such as that below needs to be used. See
# the UserDir documentation for details.
#
<IfMole mod_userdir.c>
UserDir "C:/Apache/Apache/users/"
</IfMole>

#
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
#
#<Directory "C:/Apache/Apache/users">
# AllowOverride FileInfo AuthConfig Limit
# Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
# <Limit GET POST OPTIONS PROPFIND>
# Order allow,deny
# Allow from all
# </Limit>
# <LimitExcept GET POST OPTIONS PROPFIND>
# Order deny,allow
# Deny from all
# </LimitExcept>
#</Directory>

#
# DirectoryIndex: Name of the file or files to use as a pre-written HTML
# directory index. Separate multiple entries with spaces.
#
<IfMole mod_dir.c>
DirectoryIndex index.html
</IfMole>

#
# AccessFileName: The name of the file to look for in each directory
# for access control information.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess files from being viewed by
# Web clients. Since .htaccess files often contain authorization
# information, access is disallowed for security reasons. Comment
# these lines out if you want Web visitors to see the contents of
# .htaccess files. If you change the AccessFileName directive above,
# be sure to make the corresponding changes here.
#
# Also, folks tend to use names such as .htpasswd for password
# files, so this will protect those as well.
#
<Files ~ "^\.ht">
Order allow,deny
Deny from all
Satisfy All
</Files>

#
# CacheNegotiatedDocs: By default, Apache sends "Pragma: no-cache" with each
# document that was negotiated on the basis of content. This asks proxy
# servers not to cache the document. Uncommenting the following line disables
# this behavior, and proxies will be allowed to cache the documents.
#
#CacheNegotiatedDocs

#
# UseCanonicalName: (new for 1.3) With this setting turned on, whenever
# Apache needs to construct a self-referencing URL (a URL that refers back
# to the server the response is coming from) it will use ServerName and
# Port to form a "canonical" name. With this setting off, Apache will
# use the hostname:port that the client supplied, when possible. This
# also affects SERVER_NAME and SERVER_PORT in CGI scripts.
#
UseCanonicalName On

#
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
#
<IfMole mod_mime.c>
TypesConfig conf/mime.types
</IfMole>

#
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

#
# The mod_mime_magic mole allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the mole where the hint definitions are located.
# mod_mime_magic is not part of the default server (you have to add
# it yourself with a LoadMole [see the DSO paragraph in the 'Global
# Environment' section], or recompile the server and include mod_mime_magic
# as part of the configuration), so it's enclosed in an <IfMole> container.
# This means that the MIMEMagicFile directive will only be processed if the
# mole is part of the server.
#
<IfMole mod_mime_magic.c>
MIMEMagicFile conf/magic
</IfMole>

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog logs/error.log

#
# LogLevel: Control the number of messages logged to the error.log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
#
CustomLog logs/access.log common

#
# If you would like to have agent and referer logfiles, uncomment the
# following directives.
#
#CustomLog logs/referer.log referer
#CustomLog logs/agent.log agent

#
# If you prefer a single logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#
#CustomLog logs/access.log combined

#
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (error documents, FTP directory listings,
# mod_status and mod_info output etc., but not CGI generated documents).
# Set to "EMail" to also include a mailto: link to the ServerAdmin.
# Set to one of: On | Off | EMail
#
ServerSignature On

#
# Apache parses all CGI scripts for the shebang line by default.
# This comment line, the first line of the script, consists of the symbols
# pound (#) and exclamation (!) followed by the path of the program that
# can execute this specific script. For a perl script, with perl.exe in
# the C:\Program Files\Perl directory, the shebang line should be:

#!c:/program files/perl/perl

# Note you _must_not_ indent the actual shebang line, and it must be the
# first line of the file. Of course, CGI processing must be enabled by
# the appropriate ScriptAlias or Options ExecCGI directives for the files
# or directory in question.
#
# However, Apa

5. 高分求phpmyfaq的詳細教程

phpmyfaq安裝說明

安裝演示版本號：phpmyfaq 2.6.11

教程使用的上傳工具：FlashFXP

教程使用的環境：無憂主機php虛擬主機

教程使用臨時調試域名：http://test.hk1123.51php.com/phpmyfaq

二、phpmyfaq安裝包上傳和在線解壓

使用flashFXP將壓縮包上傳到網站根目錄下，然後在線解壓到網站根目錄。關於如何在無憂php虛擬主機中上傳數據並在線解壓，我之前已經寫過相關教程了，這里不重復敘述了，有需要教程用戶可以點擊深入詳解無憂php空間如何上傳網站數據進行查看。

三、文件目錄許可權修改方法

在純linux環境下安裝phpmyfaq問答系統，務必請用戶參照無憂主機站點目錄（public_html）文件夾的許可權設置中介紹的文件目錄許可權設置的方法，將phpmyfaq根目錄和./config兩個目錄許可權設置為777， 否則在安裝過程會提示錯誤，無法正確完成安裝。

四、phpmyfaq詳細安裝步驟

Phpmyfaq的安裝安裝是非常簡潔的，由於phpmyfaq是全英文安裝界面，為方便用戶安裝和了解每個安裝步驟的含義，我特意將部分phpmyfaq安裝文件進行了翻譯，供用戶參考。如果熟練安裝只需要10分鍾左右，就可以完成phpmyfaq的安裝詳細安裝步驟如下:

1、 運行域名（http://test.hk1123.51php.com/phpmyfaq）啟動安裝向導。

2、 配置mysql資料庫連接和管理員信息。

A、Please add your database connection setup information 請添加資料庫信息

SQL server host：localhost （資料庫連接方式，本地連接）

SQL username： 51php_51php.com （資料庫訪問用戶名）

SQL password： ******** （資料庫密碼）

SQL database： www_51php （資料庫名稱）

Table preflx： phpfaq_ （資料庫表前綴名）

B、phpMYFAQ information phpmyfaq基本信息設置

Default language：chinese(simplified) （簡體中文）

Permission level: 選擇默認

Admin』s real name: administrator （管理員真實名稱）

Admin』s e-mail address: [email protected] （管理員郵箱）

Admin』s username: admin （管理員用戶名）

Admin』s password: ***** （管理員密碼）

Retype password：***** （重復管理員密碼）

phpmyfaq開源問答（FAQ）系統快速安裝教程 image00113 150x150

請用戶對照圖片和安裝界面的翻譯，正確填寫mysql資料庫信息，設置phpmyfaq的管理員帳號、選擇簡體中文語言包。如果確認無誤後，請點擊「Click to install phpMYFAQ 2.6.11」繼續安裝。

3、 等待幾分鍾，phpmyfaq就安裝完成了。安裝完成後phpmyfaq安裝向導會彈出一個調查問卷，如果你不想參與調查問卷，就直接點擊：「your version of phpMYFAQ」登錄phpmyfaq首頁。

phpmyfaq開源問答（FAQ）系統快速安裝教程 image00310 150x150

4、刪除install目錄！phpmyfaq安裝成功！

phpmyfaq開源問答（FAQ）系統快速安裝教程 image0058 150x150

5、如果你有興趣參與phpmyFAQ的官方調查問卷，無憂主機（www.51php.com）已經將調查問卷的內容翻譯如下，請用戶自行對照。

database tables were successfully created. 所有資料庫表都已經成功建立

Congratulation! Everything seems to be okay. 恭喜你！安裝完成

窗體頂端

For further development we would like to get some feedback from our users. 了更好發展，我們渴望從您那裡得到寶貴的建議：

Therefore we』d ask you to take a few minutes of your time to answer a few questions. 耽誤你幾分鍾，回到我們幾個提問：

If you don』t want to participate in the survey, you can directly visit your version of phpMyFAQ or login into your admin section. 如果你不想參閱調查，你可以直接訪問你的網站phpmyfaq，或者登錄你的管理後台

Please delete the file ./install/setup.php manually.

請刪除文件：./install/setup.php

Please delete the file ./install/update.php manually.

請刪除文件：./install/update.php

無憂主機提供美國/香港 純Linux環境下高端php空間產品，只需99元起，有需求的用戶請聯系無憂主機客服。

6. php安裝的問題，無法載入 mysql 擴展，請檢查 PHP 配置

首先你需要將PHP安裝目錄下的php_mysql.dll和php_mysqli.dll（我的在D:\apptools\php5\ext目錄下）復制到c:\windows\system32目錄下，然後修改php.ini文件（需要放到c:\windows目錄下），關鍵是extension=php_mysql.dll 和extension_dir = "D:/apptools/php5/ext"。
我的配置是這樣的：

[PHP]

;;;;;;;;;;;
; WARNING ;
;;;;;;;;;;;
; This is the default settings file for new PHP installations.
; By default, PHP installs itself with a configuration suitable for
; development purposes, and *NOT* for proction purposes.
; For several security-oriented considerations that should be taken
; before going online with your site, please consult php.ini-recommended
; and http://php.net/manual/en/security.php.

;;;;;;;;;;;;;;;;;;;
; About php.ini ;
;;;;;;;;;;;;;;;;;;;
; This file controls many aspects of PHP's behavior. In order for PHP to
; read it, it must be named 'php.ini'. PHP looks for it in the current
; working directory, in the path designated by the environment variable
; PHPRC, and in the path that was defined in compile time (in that order).
; Under Windows, the compile-time path is the Windows directory. The
; path in which the php.ini file is looked for can be overridden using
; the -c argument in command line mode.
;
; The syntax of the file is extremely simple. Whitespace and Lines
; beginning with a semicolon are silently ignored (as you probably guessed).
; Section headers (e.g. [Foo]) are also silently ignored, even though
; they might mean something in the future.
;
; Directives are specified using the following syntax:
; directive = value
; Directive names are *case sensitive* - foo=bar is different from FOO=bar.
;
; The value can be a string, a number, a PHP constant (e.g. E_ALL or M_PI), one
; of the INI constants (On, Off, True, False, Yes, No and None) or an expression
; (e.g. E_ALL & ~E_NOTICE), or a quoted string ("foo").
;
; Expressions in the INI file are limited to bitwise operators and parentheses:
; | bitwise OR
; & bitwise AND
; ~ bitwise NOT
; ! boolean NOT
;
; Boolean flags can be turned on using the values 1, On, True or Yes.
; They can be turned off using the values 0, Off, False or No.
;
; An empty string can be denoted by simply not writing anything after the equal
; sign, or by using the None keyword:
;
; foo = ; sets foo to an empty string
; foo = none ; sets foo to an empty string
; foo = "none" ; sets foo to the string 'none'
;
; If you use constants in your value, and these constants belong to a
; dynamically loaded extension (either a PHP extension or a Zend extension),
; you may only use these constants *after* the line that loads the extension.
;
;
;;;;;;;;;;;;;;;;;;;
; About this file ;
;;;;;;;;;;;;;;;;;;;
; All the values in the php.ini-dist file correspond to the builtin
; defaults (that is, if no php.ini is used, or if you delete these lines,
; the builtin defaults will be identical).

;;;;;;;;;;;;;;;;;;;;
; Language Options ;
;;;;;;;;;;;;;;;;;;;;

; Enable the PHP scripting language engine under Apache.
engine = On

; Enable compatibility mode with Zend Engine 1 (PHP 4.x)
zend.ze1_compatibility_mode = Off

; Allow the <? tag. Otherwise, only <?php and <script> tags are recognized.
; NOTE: Using short tags should be avoided when developing applications or
; libraries that are meant for redistribution, or deployment on PHP
; servers which are not under your control, because short tags may not
; be supported on the target server. For portable, redistributable code,
; be sure not to use short tags.
short_open_tag = On

; Allow ASP-style <% %> tags.
asp_tags = Off

; The number of significant digits displayed in floating point numbers.
precision = 12

; Enforce year 2000 compliance (will cause problems with non-compliant browsers)
y2k_compliance = On

; Output buffering allows you to send header lines (including cookies) even
; after you send body content, at the price of slowing PHP's output layer a
; bit. You can enable output buffering ring runtime by calling the output
; buffering functions. You can also enable output buffering for all files by
; setting this directive to On. If you wish to limit the size of the buffer
; to a certain size - you can use a maximum number of bytes instead of 'On', as
; a value for this directive (e.g., output_buffering=4096).
output_buffering = On

; You can redirect all of the output of your scripts to a function. For
; example, if you set output_handler to "mb_output_handler", character
; encoding will be transparently converted to the specified encoding.
; Setting any output handler automatically turns on output buffering.
; Note: People who wrote portable scripts should not depend on this ini
; directive. Instead, explicitly set the output handler using ob_start().
; Using this ini directive may cause problems unless you know what script
; is doing.
; Note: You cannot use both "mb_output_handler" with "ob_iconv_handler"
; and you cannot use both "ob_gzhandler" and "zlib.output_compression".
; Note: output_handler must be empty if this is set 'On' !!!!
; Instead you must use zlib.output_handler.
;output_handler =

; Transparent output compression using the zlib library
; Valid values for this option are 'off', 'on', or a specific buffer size
; to be used for compression (default is 4KB)
; Note: Resulting chunk size may vary e to nature of compression. PHP
; outputs chunks that are few hundreds bytes each as a result of
; compression. If you prefer a larger chunk size for better
; performance, enable output_buffering in addition.
; Note: You need to use zlib.output_handler instead of the standard
; output_handler, or otherwise the output will be corrupted.
zlib.output_compression = Off

; You cannot specify additional output handlers if zlib.output_compression
; is activated here. This setting does the same as output_handler but in
; a different order.
;zlib.output_handler =

; Implicit flush tells PHP to tell the output layer to flush itself
; automatically after every output block. This is equivalent to calling the
; PHP function flush() after each and every call to print() or echo() and each
; and every HTML block. Turning this option on has serious performance
; implications and is generally recommended for debugging purposes only.
implicit_flush = Off

; The unserialize callback function will be called (with the undefined class'
; name as parameter), if the unserializer finds an undefined class
; which should be instantiated.
; A warning appears if the specified function is not defined, or if the
; function doesn't include/implement the missing class.
; So only set this entry, if you really want to implement such a
; callback-function.
unserialize_callback_func=

; When floats & doubles are serialized store serialize_precision significant
; digits after the floating point. The default value ensures that when floats
; are decoded with unserialize, the data will remain the same.
serialize_precision = 100

; Whether to enable the ability to force arguments to be passed by reference
; at function call time. This method is deprecated and is likely to be
; unsupported in future versions of PHP/Zend. The encouraged method of
; specifying which arguments should be passed by reference is in the function
; declaration. You're encouraged to try and turn this option Off and make
; sure your scripts work properly with it in order to ensure they will work
; with future versions of the language (you will receive a warning each time
; you use this feature, and the argument will be passed by value instead of by
; reference).
allow_call_time_pass_reference = On

;
; Safe Mode
;
safe_mode = Off

; By default, Safe Mode does a UID compare check when
; opening files. If you want to relax this to a GID compare,
; then turn on safe_mode_gid.
safe_mode_gid = Off

; When safe_mode is on, UID/GID checks are bypassed when
; including files from this directory and its subdirectories.
; (directory must also be in include_path or full path must
; be used when including)
safe_mode_include_dir =

; When safe_mode is on, only executables located in the safe_mode_exec_dir
; will be allowed to be executed via the exec family of functions.
safe_mode_exec_dir =

; Setting certain environment variables may be a potential security breach.
; This directive contains a comma-delimited list of prefixes. In Safe Mode,
; the user may only alter environment variables whose names begin with the
; prefixes supplied here. By default, users will only be able to set
; environment variables that begin with PHP_ (e.g. PHP_FOO=BAR).
;
; Note: If this directive is empty, PHP will let the user modify ANY
; environment variable!
safe_mode_allowed_env_vars = PHP_

; This directive contains a comma-delimited list of environment variables that
; the end user won't be able to change using putenv(). These variables will be
; protected even if safe_mode_allowed_env_vars is set to allow to change them.
safe_mode_protected_env_vars = LD_LIBRARY_PATH

; open_basedir, if set, limits all file operations to the defined directory
; and below. This directive makes most sense if used in a per-directory
; or per-virtualhost web server configuration file. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
;open_basedir =

; This directive allows you to disable certain functions for security reasons.
; It receives a comma-delimited list of function names. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
disable_functions =

; This directive allows you to disable certain classes for security reasons.
; It receives a comma-delimited list of class names. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
disable_classes =

; Colors for Syntax Highlighting mode. Anything that's acceptable in
; <span style="color: ???????"> would work.
;highlight.string = #DD0000
;highlight.comment = #FF9900
;highlight.keyword = #007700
;highlight.bg = #FFFFFF
;highlight.default = #0000BB
;highlight.html = #000000

; If enabled, the request will be allowed to complete even if the user aborts
; the request. Consider enabling it if executing long request, which may end up
; being interrupted by the user or a browser timing out.
; ignore_user_abort = On

;
; Misc
;
; Decides whether PHP may expose the fact that it is installed on the server
; (e.g. by adding its signature to the Web server header). It is no security
; threat in any way, but it makes it possible to determine whether you use PHP
; on your server or not.
expose_php = On

;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;

max_execution_time = 3000 ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
memory_limit = 8M ; Maximum amount of memory a script may consume (8MB)

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Error handling and logging ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

; error_reporting is a bit-field. Or each number up to get desired error
; reporting level
; E_ALL - All errors and warnings (doesn't include E_STRICT)
; E_ERROR - fatal run-time errors
; E_WARNING - run-time warnings (non-fatal errors)
; E_PARSE - compile-time parse errors
; E_NOTICE - run-time notices (these are warnings which often result
; from a bug in your code, but it's possible that it was
; intentional (e.g., using an uninitialized variable and
; relying on the fact it's automatically initialized to an
; empty string)
; E_STRICT - run-time notices, enable to have PHP suggest changes
; to your code which will ensure the best interoperability
; and forward compatibility of your code
; E_CORE_ERROR - fatal errors that occur ring PHP's initial startup
; E_CORE_WARNING - warnings (non-fatal errors) that occur ring PHP's
; initial startup
; E_COMPILE_ERROR - fatal compile-time errors
; E_COMPILE_WARNING - compile-time warnings (non-fatal errors)
; E_USER_ERROR - user-generated error message
; E_USER_WARNING - user-generated warning message
; E_USER_NOTICE - user-generated notice message
;
; Examples:
;
; - Show all errors, except for notices and coding standards warnings
;
;error_reporting = E_ALL & ~E_NOTICE
;
; - Show all errors, except for notices
;
;error_reporting = E_ALL & ~E_NOTICE | E_STRICT
;
; - Show only errors
;
;error_reporting = E_COMPILE_ERROR|E_ERROR|E_CORE_ERROR
;
; - Show all errors except for notices and coding standards warnings
;
error_reporting = E_ALL & ~E_NOTICE

; Print out errors (as a part of the output). For proction web sites,
; you're strongly encouraged to turn this feature off, and use error logging
; instead (see below). Keeping display_errors enabled on a proction web site
; may reveal security information to end users, such as file paths on your Web
; server, your database schema or other information.
display_errors = On

; Even when display_errors is on, errors that occur ring PHP's startup
; sequence are not displayed. It's strongly recommended to keep
; display_startup_errors off, except for when debugging.
display_startup_errors = Off

; Log errors into a log file (server-specific log, stderr, or error_log (below))
; As stated above, you're strongly advised to use error logging in place of
; error displaying on proction web sites.
log_errors = Off

; Set maximum length of log_errors. In error_log information about the source is
; added. The default is 1024 and 0 allows to not apply any maximum length at all.
log_errors_max_len = 1024

; Do not log repeated messages. Repeated errors must occur in same file on same
; line until ignore_repeated_source is set true.
ignore_repeated_errors = Off

; Ignore source of message when ignoring repeated messages. When this setting
; is On you will not log errors with repeated messages from different files or
; sourcelines.
ignore_repeated_source = Off

; If this parameter is set to Off, then memory leaks will not be shown (on
; stdout or in the log). This has only effect in a debug compile, and if
; error reporting includes E_WARNING in the allowed list
report_memleaks = On

; Store the last error/warning message in $php_errormsg (boolean).
track_errors = Off

; Disable the inclusion of HTML tags in error messages.
; Note: Never use this feature for proction boxes.
;html_errors = Off

; If html_errors is set On PHP proces clickable error messages that direct
; to a page describing the error or function causing the error in detail.
; You can download a of the PHP manual from http://www.php.net/docs.php
; and change docref_root to the base URL of your local including the
; leading '/'. You must also specify the file extension being used including
; the dot.
; Note: Never use this feature for proction boxes.
;docref_root = "/phpmanual/"
;docref_ext = .html

; String to output before an error message.
;error_prepend_string = "<font color=ff0000>"

; String to output after an error message.
;error_append_string = "</font>"

; Log errors to specified file.
;error_log = filename

; Log errors to syslog (Event Log on NT, not valid in Windows 95).
;error_log = syslog

;;;;;;;;;;;;;;;;;
; Data Handling ;
;;;;;;;;;;;;;;;;;
;
; Note - track_vars is ALWAYS enabled as of PHP 4.0.3

; The separator used in PHP generated URLs to separate arguments.
; Default is "&".
;arg_separator.output = "&"

; List of separator(s) used by PHP to parse input URLs into variables.
; Default is "&".
; NOTE: Every character in this directive is considered as separator!
;arg_separator.input = ";&"

; This directive describes the order in which PHP registers GET, POST, Cookie,
; Environment and Built-in variables (G, P, C, E & S respectively, often
; referred to as EGPCS or GPC). Registration is done from left to right, newer
; values override older values.
variables_order = "EGPCS"

; Whether or not to register the EGPCS variables as global variables. You may
; want to turn this off if you don't want to clutter your scripts' global scope
; with user data. This makes most sense when coupled with track_vars - in which
; case you can access all of the GPC variables through the $HTTP_*_VARS[],
; variables.
;
; You should do your best to write your scripts so that they do not require
; register_globals to be on; Using form variables as globals can easily lead
; to possible security problems, if the code is not very well thought of.
register_globals = On

; Whether or not to register the old-style input arrays, HTTP_GET_VARS
; and friends. If you're not using them, it's recommended to turn them off,
; for performance reasons.
register_long_arrays = On

; This directive tells PHP whether to declare the argv&argc variables (that
; would contain the GET information). If you don't use these variables, you
; should turn it off for increased performance.
register_argc_argv = On

; When enabled, the SERVER and ENV variables are created when they're first
; used (Just In Time) instead of when the script starts. If these variables
; are not used within a script, having this directive on will result in a
; performance gain. The PHP directives register_globals, register_long_arrays,
; and register_argc_argv must be disabled for this directive to have any affect.
auto_globals_jit = On

; Maximum size of POST data that PHP will accept.
post_max_size = 8M

; Magic quotes
;

; Magic quotes for incoming GET/POST/Cookie data.
magic_quotes_gpc = On

; Magic quotes for runtime-generated data, e.g. data from SQL, from exec(), etc.
magic_quotes_runtime = Off

; Use Sybase-style magic quotes (escape ' with '' instead of \').
magic_quotes_sybase = Off

; Automatically add files before or after any PHP document.
auto_prepend_file =
auto_append_file =

; As of 4.0b4, PHP always outputs a character encoding by default in
; the Content-type: header. To disable sending of the charset, simply
; set it to be empty.
;
; PHP's built-in default is text/html
default_mimetype = "text/html"
;default_charset = "iso-8859-1"

; Always populate the $HTTP_RAW_POST_DATA variable.
;always_populate_raw_post_data = On

;;;;;;;;;;;;;;;;;;;;;;;;;
; Paths and Directories ;
;;;;;;;;;;;;;;;;;;;;;;;;;

; UNIX: "/path1:/path2"
;include_path = ".:/php/includes"
;
; Windows: "\path1;\path2"
include_path = ".;D:\apptools\php5\PEAR"

; The root of the PHP pages, used only if nonempty.
; if PHP was not compiled with FORCE_REDIRECT, you SHOULD set doc_root
; if you are running php as a CGI under any web server (other than IIS)
; see documentation for security issues. The alternate is to use the
; cgi.force_redirect configuration below
doc_root =

; The directory under which PHP opens the script using /~username used only
; if nonempty.
user_dir =

; Directory in which the loadable extensions (moles) reside.
extension_dir = "D:/apptools/php5/ext"

; Whether or not to enable the dl() function. The dl() function does NOT work
; properly in multithreaded servers, such as IIS or Zeus, and is automatically
; disabled on them.
enable_dl = On

7. 編程都有哪些語言

目前熱門的語言有：C、C++、JAVA、VB、VC、FoxPro、Delphi、SQL、PHP、ASP、JSP等等。

專門有機構為編程語言進行排名，如下圖：

8. 編程語言一共有多少種

一般編程語言分成機器語言、匯編語言和高級語言。機器語言就是二進制代碼，可讀性低，所以一般是用其他語言先編寫代碼，然後編譯為機器代碼，方可運行。
編程語言有好幾千種，這里是一些常見的：
C,C++,C#,Java,JavaScript,python,Pascal,Delphi,PHP,SQL,ASP,Matlab,HTML,Bash,Batch,Ruby,Basic,Visual Basic等等

9. Sublime Text，php代碼格式化插件codeformatter 設置PHP代碼格式時報錯 怎麼處理

{
"codeformatter_debug": false,
"codeformatter_php_options":
{
"syntaxes": "php", // Syntax names which must process PHP formatter
"php_path": "這里改成你php的路徑", // Path for PHP executable, e.g. "/usr/lib/php" or "C:/Program Files/PHP/php.exe". If empty, uses command "php" from system environments
"format_on_save": false, // Format on save. Either a boolean (true/false) or a string regexp tested on filename. Example : "^((?!.min.|vendor).)*$"
"php55_compat": false, // PHP 5.5 compatible mode
"psr1": false, // Activate PSR1 style
"psr1_naming": false, // Activate PSR1 style - Section 3 and 4.3 - Class and method names case
"psr2": true, // Activate PSR2 style
"indent_with_space": 4, // Use spaces instead of tabs for indentation
"enable_auto_align": true, // Enable auto align of = and =>
"visibility_order": true, // Fixes visibility order for method in classes - PSR-2 4.2
"smart_linebreak_after_curly": true, // Convert multistatement blocks into multiline blocks
// Enable specific transformations. Example: ["ConvertOpenTagWithEcho", "PrettyPrintDocBlocks"]
// You can list all available transformations from command palette: CodeFormatter: Show PHP Transformations
"passes": [],
// Disable specific transformations
"excludes": []
},
"codeformatter_js_options":
{
"syntaxes": "javascript,json", // Syntax names which must process JS formatter
"format_on_save": false, // Format on save. Either a boolean (true/false) or a string regexp tested on filename. Example : "^((?!.min.|vendor).)*$"
"indent_size": 4, // indentation size
"indent_char": " ", // Indent character
"indent_with_tabs": false, // Indent with one tab (overrides indent_size and indent_char options)
"eol": "\n", // EOL symbol
"preserve_newlines": false, // whether existing line breaks should be preserved,
"max_preserve_newlines": 10, // maximum number of line breaks to be preserved in one chunk
"space_in_paren": false, // Add padding spaces within paren, ie. f( a, b )
"space_in_empty_paren": false, // Add padding spaces within paren if parent empty, ie. f( )
"e4x": false, // Pass E4X xml literals through untouched
"jslint_happy": false, // if true, then jslint-stricter mode is enforced. Example function () vs function()
"space_after_anon_function": false, // Space after anonimouse functions
"brace_style": "collapse", // "collapse" | "expand" | "end-expand". put braces on the same line as control statements (default), or put braces on own line (Allman / ANSI style), or just put end braces on own line.
"keep_array_indentation": false, // keep array indentation.
"keep_function_indentation": false, // keep function indentation.
"eval_code": false, // eval code
"unescape_strings": false, // Decode printable characters encoded in xNN notation
"wrap_line_length": 0, // Wrap lines at next opportunity after N characters
"unindent_chained_methods": false, // Unindent chained method calls
"break_chained_methods": false, // Break chained method calls across subsequent lines
"end_with_newline": false, // Add new line at end of file
"comma_first": false, // Add comma first
"operator_position": "before-newline" // Operator position: before-newline, after-newline, preserve-newline
},
"codeformatter_css_options":
{
"syntaxes": "css,less", // Syntax names which must process CSS formatter
"format_on_save": false, // Format on save. Either a boolean (true/false) or a string regexp tested on filename. Example : "^((?!.min.|vendor).)*$"
"indent_size": 4, // Indentation size
"indent_char": " ", // Indentation character
"indent_with_tabs": false, // Indent with one tab (overrides indent_size and indent_char options)
"selector_separator_newline": false, // Add new lines after selector separators
"end_with_newline": false, // Add new line of end in file
"newline_between_rules": false, // Add new line between rules
"space_around_combinator": false, // Space around combinator
"eol": "\n" // EOL symbol
},
"codeformatter_scss_options":
{
"syntaxes": "scss,sass", // Indentation size
"format_on_save": false, // Format on save. Either a boolean (true/false) or a string regexp tested on filename. Example : "^((?!.min.|vendor).)*$"
"indent_size": 4, // Indentation size
"indent_char": " ", // Indentation character
"indent_with_tabs": false, // Indent with one tab (overrides indent_size and indent_char options)
"selector_separator_newline": false, // Add new lines after selector separators
"end_with_newline": false, // Add new line of end in file
"newline_between_rules": false, // Add new line between rules
"space_around_combinator": false, // Space around combinator
"eol": "\n" // EOL symbol
},
"codeformatter_html_options":
{
"syntaxes": "html,blade,asp,xml", // Syntax names which must process HTML formatter
"format_on_save": false, // Format on save. Either a boolean (true/false) or a string regexp tested on filename. Example : "^((?!.min.|vendor).)*$"
"formatter_version": "bs4", // Which formatter to use. Current options are "bs4" and "regexp". If an error occurs while loading the bs4 formatter, the regexp formatter will automatically be used
"indent_size": 4, // indentation size
"indent_char": " ", // Indentation character
"indent_with_tabs": false, // Indent with one tab (overrides indent_size and indent_char options)
"exception_on_tag_mismatch": false, // If the last closing tag is not at the same indentation level as the first opening tag, there's probably a tag mismatch in the file
"expand_javascript": false, // (Under construction) Expand JavaScript inside of <script> tags (also affects CSS purely by coincidence)
"expand_tags": false, // Expand tag attributes onto new lines
"minimum_attribute_count": 2, // Minimum number of attributes needed before tag attributes are expanded to new lines
"first_attribute_on_new_line": false, // Put all attributes on separate lines from the tag (only uses 1 indentation unit as opposed to lining all attributes up with the first)
"rece_empty_tags": false, // Put closing tags on same line as opening tag if there is no content between them
"rece_whole_word_tags": false, // Put closing tags on same line as opening tag if there is whole word between them
"custom_singletons": "" // Custom singleton tags for various template languages outside of the HTML5 spec
},
"codeformatter_python_options":
{
"syntaxes": "python", // Syntax names which must process Python formatter
"format_on_save": false, // Format on save. Either a boolean (true/false) or a string regexp tested on filename. Example : "^((?!.min.|vendor).)*$"
"indent_size": 1, // indentation size
"indent_with_tabs": true, // Indent with tabs or spaces
"max_char": 80, // Width of output lines in characters.
"assignment": " = ", // This is how the assignment operator is to appear.
"function_param_assignment": "=", // This is how function-parameter assignment should appear.
"function_param_sep": ", ", // This is how function parameters are separated.
"list_sep": ", ", // This is how list items are separated.
"subscript_sep": "=", // This is how subscripts are separated.
"dict_colon": ": ", // This separates dictionary keys from values.
"slice_colon": ":", // this separates the start:end indices of slices.
"comment_prefix": "# ", // This is the sentinel that marks the beginning of a commentary string.
"shebang": "#!/usr/bin/env python", // Hashbang, a line-one comment naming the Python interpreter to Unix shells.
"boilerplate": "", // Standard code block (if any). This is inserted after the mole doc string on output.
"blank_line": "", // This is how a blank line is to appear (up to the newline character).
"keep_blank_lines": true, // If true, preserve one blank where blank(s) are encountered.
"add_blank_lines_around_comments": true, // If true, set off comment blocks with blanks.
"add_blank_line_after_doc_string": true, // If true, add blank line after doc strings.
"max_seps_func_def": 3, // Split lines containing longer function definitions.
"max_seps_func_ref": 5, // Split lines containing longer function calls.
"max_seps_series": 5, // Split lines containing longer lists or tuples.
"max_seps_dict": 3, // Split lines containing longer dictionary definitions.
"max_lines_before_split_lit": 2, // Split string literals containing more newline characters.
"left_margin": "", // This is how the left margin is to appear.
"normalize_doc_strings": false, // If true, normalize white space in doc strings.
"leftjust_doc_strings": false, // If true, left justify doc strings.
"wrap_doc_strings": false, // If true, wrap doc strings to max_char.
"leftjust_comments": false, // If true, left justify comments.
"wrap_comments": false, // If true, wrap comments to max_char.
"double_quoted_strings": false, // If true, use quotes instead of apostrophes for string literals.
"single_quoted_strings": false, // If true, use apostrophes instead of quotes for string literals.
"can_split_strings": false, // If true, longer strings are split at the max_char.
"doc_tab_replacement": "....", // This literal replaces tab characters in doc strings and comments.
// Optionally preserve unassigned constants so that code to be tidied
// may contain blocks of commented-out lines that have been no-op'ed
// with leading and trailing triple quotes. Python scripts may declare
// constants without assigning them to a variables, but CodeFormatter
// considers this wasteful and normally elides them.
"keep_unassigned_constants": false,
// Optionally omit parentheses around tuples, which are superfluous
// after all. Normal CodeFormatter behavior will be still to include them
// as a sort of tuple display analogous to list displays, dict
// displays, and yet-to-come set displays.
"parenthesize_tuple_display": true,
// When CodeFormatter splits longer lines because max_seps
// are exceeded, the statement normally is closed before the margin is
// restored. The closing bracket, brace, or parenthesis is placed at the
// current indent level. This looks ugly to "C" programmers. When
// java_style_list_dedent is True, the closing bracket, brace, or
// parenthesis is brought back left to the indent level of the enclosing
// statement.
"java_style_list_dedent": false
},
"codeformatter_vbscript_options":
{
"syntaxes": "vbscript", // Syntax names which must process VBScript formatter
"format_on_save": false, // Format on save. Either a boolean (true/false) or a string regexp tested on filename. Example : "^((?!.min.|vendor).)*$"
"indent_size": 1, // indentation size
"indent_char": "\t", // Indentation character
"indent_with_tabs": true, // Indent with one tab (overrides indent_size and indent_char options)
"preserve_newlines": true, // Preserve existing line-breaks
"max_preserve_newlines": 10, // Maximum number of line-breaks to be preserved in one chunk
"opening_tags": "^(Function .*|Sub .*|If .* Then|For .*|Do While .*|Select Case.*)", // List of keywords which open a new block
"middle_tags": "^(Else|ElseIf .* Then|Case .*)$", // List of keywords which divide a block, but neither open or close the block
"closing_tags": "(End Function|End Sub|End If|Next|Loop|End Select)$" // List of keywords which close an open block
},
"codeformatter_coldfusion_options":
{
"syntaxes": "coldfusion,cfm,cfml", // Syntax names which must process Coldfusion Markup Language formatter
"format_on_save": false, // Format on save. Either a boolean (true/false) or a string regexp tested on filename. Example : "^((?!.min.|vendor).)*$"
"indent_size": 2, // indentation size
"indent_char": " ", // Indentation character
"indent_with_tabs": false, // Indent with one tab (overrides indent_size and indent_char options)
"exception_on_tag_mismatch": false, // If the last closing tag is not at the same indentation level as the first opening tag, there's probably a tag mismatch in the file
"expand_javascript": false, // (Under construction) Expand JavaScript inside of <script> tags (also affects CSS purely by coincidence)
"expand_tags": false, // Expand tag attributes onto new lines
"minimum_attribute_count": 2, // Minimum number of attributes needed before tag attributes are expanded to new lines
"first_attribute_on_new_line": false, // Put all attributes on separate lines from the tag (only uses 1 indentation unit as opposed to lining all attributes up with the first)
"rece_empty_tags": false, // Put closing tags on same line as opening tag if there is no content between them
"rece_whole_word_tags": false, // Put closing tags on same line as opening tag if there is whole word between them
"custom_singletons": "" // Custom singleton tags for various template languages outside of the HTML5 spec
}
}

10. PHP，JSP，ASP是什麼干什麼用的之間有什麼關系嗎

PHP，Hypertext Preprocessor，最初在95年問世（那時以前叫Personal Home Page）。PHP最初是製作動態網頁的伺服器端腳本語言，但現在PHP已經可以作為command line運行有GUI的standalone的程序。現在是PHP Group在開發和管理PHP的規則，功能等。但PHP大都用在dynamic webpage scripting上，好象沒聽過誰用它開發desktop application。

PHP使用率是製作動態網頁的幾種語言（JSP，ASP，ASP.NET, ColdFusion, Ruby, SHTML）中最高的。因為PHP在95年已經問世至今，以有相當數量的開發者。我們熟知的國際權威網路全書Wikipedia有90%用PHP寫的，而且國外流行多年的「校內網」FaceBook 也全部用PHP寫的，同時Yahoo, Sony官方，Pepsi百事官方這些網站都是用PHP的。根據維基網路（Wikipedia）的說法，PHP被超過20,000,000的網站所用，被超過1,000,000的網頁伺服器所用。目前到2008五月，PHP最新版本為5.2.6。

PHP不僅使用率高，而且能兼容各類平台。它可以在大多數網頁伺服器上運行（如：MS IIS，Apache），大多數操作系統上運行（如：Windows, UNIX, Linux）。而且PHP支持很大多數牌子的資料庫：MySQL, Informix, Oracle, Sybase, Solid, PostgreSQL, Gerneric ODBC等。

結構方面，雖比JSP，ASP.NET差點，PHP也有很多Framework可用。微軟的ASP.NET結構是出名的，JSP的MVC結構也很厲害，所以開發大網站ASP.NET，JSP都很快。而PHP Group也為此付出很大努力，來開發自己特有的結構適應不同類型的大網站的需求。常見的PHP的Framework有：CakePHP, PRADO, Symfony, Zend等。

另外LAMP結構，是PHP最常用的開發模式，即是配合Linux, Apache, MySQL, PHP，合稱LAMP。個人認為這種方式才是ASP.NET,PHP,JSP中最簡單的。

3. 說說JSP。（本人工作中用的最多的就是JSP）
JSP, JavaServer Pages 是Java技術的一部分，可以說是Java Platform Enterprise Edition的一部分（JAVA主要3個大技術，Java SE, Java EE, Java ME）。軟體開發者可以用JSP來動態生成HTML，XML或者其他的文檔。然後把文檔response給網頁用戶。這項技術，可以用Java里的所有定義過的library來支持它的功能，所以JSP的API和普通Java EE的API一樣。

JSP里還有很多有功能的XML tag（如：<jsp:include>,<jsp:useBean）。這些都是JAVA內置功能，不需要導入新的外置 library。這些XML tag，可以在很多Web Server里使用（如：Apache, Apache TomCat, WebLogic等）。

JSP在編譯後就完全和Servlet一樣了。JSP頁面在第一次被用戶訪問的時候，首先被JAVA 編譯器，編譯成Java Servlet Class。然後編譯後Servlet Class，在以後被用戶訪問時，直接在JVM里運行，由JSP Web Container來輸出HTML給用戶。JSP這種「首次訪問-預編譯」的運行方式比傳統PHP（PHP 4和PHP以前版本），過時的ASP（所有版本的ASP），要快很多。（網路一位網友作過一個1萬次For Loop，循環的測試，結果發現JSP比傳統PHP，ASP快盡10被的速度就完成運算）。預編譯的運行方式後來被PHP5效仿，ASP.NET也是預編譯的。當然JSP還有一個好處，就是可以直接用純Java （無HTML），來寫一個Servlet，直接在JVM運行後，由JSP Web Container輸出HTML給用戶。只是Servlet有的時候寫一些presentation tier的東西很麻煩，因為它不能融合XML和輸出邏輯在一起。所以一般Servlet用於純Java的business logic邏輯。

JSP的tag還可以由用戶自己來創造和使用，這個和ASP.NET里的user-defined controls差不多。

MVC, Model-View-Controller，是JSP的普遍開發架構，用來把JSP技術中的presentation, business logic, data storage三層清楚的分開。這樣使開發過程更佳清楚明了，便於開發，維護。常用的MVB架構有：Barracuda, Apache Struts和Spring。JSF,JavaServer Faces是一個由SUN官方開發的Framework，是模仿ASP.NET的event-driven開發模式，和ASP.NET非常相似。但SUN 並沒有讓JSF替代JSP，相反JSF的開發者少之又少，但是據說現在JSF或JSP配合RAD（AJAX）開發很流行（校內網就是這樣，而且結合Struts）。

4. ASP（Active Server Pages）, ASP.NET 兩個分別是 動態網頁開發語言，動態網頁開發語言和結構
(1) 關於ASP的淘汰
ASP, Active Server Pages已經過時了, 但因為其出現的早，96年就有了，所以現在有些中小網站還用（但，使用最多最廣的是PHP，最初於95年現世。ASP是微軟第一代動態網頁開發語言，只能在Windows系統 + MS IIS伺服器平台下運行。

Wikipedia, Facebook, 網路等都用PHP，PHP學習的簡單度和ASP差不多；JSP稍微難點，JSP用的一般都是銀行，購物等安全性較高的網站，Google也用JSP）。但隨著開發者的各種需求，ASP以後可以被ASP.NET取代，因為微軟停止對其的一切技術維護與功能更新。ASP.NET是革新版本的ASP（注意是「革新版本」，而非「改進版本」），或者說是完全新一代的Dynamic Web Scripting。

ASP代表著傳統的dynamic web scripting，與ASP.NET沒什麼關系，學了確實也沒用。因為ASP不象CGI（Common Gateway Interface），CGI是動態網站製作的始祖，所有ASP，JSP，PHP什麼的都根據CGI演化而來，而且ASP，PHP，JSP都包含了些 CGI的東西；而ASP卻沒有被衍生出任何新技術，ASP.NET也不算基於ASP，只能說ASP.NET開發理念，library，功能完全是基於.NET的其它組件。

其實PHP，JSP，ASP明白其中一種，其它的都很容易學會了。如果非要學學傳統的dynamic web scripting，那就學學PHP吧，不比ASP難，但比ASP功能多，穩定性好，PHP5運行速度也比ASP快很多（JSP稍難因為要學點 Java）。學了PHP或JSP什麼的，對學ASP.NET有好處，而且還可以直接用PHP，JSP進行開發。去google差差英文資源，有評價PHP 最好的，有評價JSP最好的，還從沒有聽誰說過ASP最好。

ASP.NET畢竟在.NET中，所以ASP.NET還是有相當地位的。

(2). 關於ASP.NET的優勢
ASP.NET是微軟.NET Framework的一部分。伴隨.NET 1.0在2002的問世，ASP.NET也出現在動態網頁開發語言的家族中（與PHP,JSP,ColdFusion, Ruby, SHTML等並行了）。

功能上，ASP.NET比ASP有更強大的library, 更好的穩定性。 ASP.NET可以使用.NET Framework中所有組件（也就是說.NET能實現的，ASP.NET一樣能實現），功能上顯然強大於傳統功能單調的ASP。最強的技術支持Web Service, 而且有.NET的所有library做後盾。而且ASP.NET 在.NET 3.5中還有微軟專門為AJAX開發的功能--ASP.NET AJAX。

結構上，傳統的ASP把所有代碼混為一團，簡單的用<%%>把HTML和VBScript（或JScript）分開，實現動態輸出 HTML。因為ASP.NET模仿JSP的MVC網頁結構，微軟為ASP.NET開發了自己的Code-Behind結構，將 presentation（文件拓展名：.aspx）和business logic(文件拓展名：.cs或.vb等)分離。同時Code-Behind模式也實現了讓ASP.NET開發者用.NET中最普通Winform的開發模式來開發網站，方便非網頁開發者製作動態網站。所以ASP.NET更容易維護，比ASP更適合於Enterprise Level 的大網站開發。

由於ASP.NET比JSP，PHP等更接近於.NET Winform的開發。如Tree View, Datagrid View（即高級Table）等高級UI，都可以直接用ASP.NET中的Web Control來實現，這比傳統的使用JavaScript + XTHML + CSS的DHTML開發方式簡單不少，也更好維護。同時ASP.NET開發這可以定義自己的User Control，製作自己特別的一種UI（如網站LOGO，版權等部分），而且此User Control可以被存為.ascx文件，方便讓每一頁(.aspx)來使用。

運行速度上，ASP.NET模仿了JSP的預編譯機制(Pre-Compile)。使編譯好的代碼(MSIL語言)在網頁伺服器上運行。這樣比傳統的ASP，傳統PHP（PHP4以前版本）更快，因為傳統的ASP是直接運行開發者寫的Script，相當於每運行一次，就得編譯一次那麼慢。 ASP.NET可以用VB, C#, J#等所有.NET Framework的語言開發.(但其實每種語言做的東西都一樣... 就象山東話, 東北話, 寫出來都是中文:)

不過ASP.NET對出學者可能有點難. 因為它其實在模擬desktop application development，即Winforms開發的模式, 不象傳統的JSP,PHP, ASP這樣容易明白。傳統的Dynamic Server Scripting, 象PHP 5, 這是現在最簡單的, 最有效的了。（ 那個JSP也不難. 如果有錢還可以考慮下Adobe ColdFusion。）

ASP.NET的新潮的Dynamic Server Scripting, 在其帶動下SUN也推出自己的JavaServer Faces (其實是拓展JSP，但JSF無法取代JSP), 和ASP.NET很象, 也有很多Web Control（JTable, JTree），同時JSF也曾強了對WEB SERVCIE的支持, 也很適合ENTERPRISE LEVEL 的網站。

(3). ASP與ASP.NET的優劣總結：
-- ASP已經被微軟停止更新；ASP.NET卻在.NET（1.0, 2.0, 3.0, 3.5）中突飛猛進；
-- ASP在96年出現，並沒有引領一個潮流，PHP，ColdFusion都出現於95年，引領了整個潮流；ASP.NET引領新的動態網站開發潮流，SUN的JSF（JavaServer Faces）就是與ASP.NET極其相似；
-- ASP大多被用在是中小網站；PHP被Wikipedia, Facebook, 網路所用，JSP被GOOGLE所用；
-- ASP不支持Web Service; ASP.NET支持Web Service。要是了解.NET中的Web Service在大組織系統中的重要性，就能立桿見影的看出差距
-- ASP開發AJAX比較麻煩；而ASP.NET專門用AJAX控制項，更方便。要是了解Web 2.0，那麼AJAX是什麼地位，就不用我說了吧。
-- ASP.NET模仿JSP，是pre-compile的；ASP不compile，直接運行Script的速度顯然沒有compile之後的快。
-- ASP.NET的唯一缺點，就是開發用的IDE--Visual Studio Professional比較貴（express版免費的功能太少）；ASP的唯一優點是，其

學起來最簡單，跟PHP一樣簡單，比JSP簡單，更比ASP.NET簡單幾倍。