从别人的blog看到的一篇文章，原文如下

                                         ——爱的感觉·施岷

    有太多太多的话无从说起，有太多太多的感受埋在心底。不要太过奢华，不要太多的甜言蜜语，只要每一天都能生活在一起，守着一个小小的家，彼此心里有着彼此，虽然平平淡淡却也充满乐趣。一个眼神，一个拥抱，一份关心，就让心融化在暖暖的春风里。我满足了，无须多语。

                       　     ——有一个字，藏在心底·系海石

    男人对女人的爱，是不用语言的。他是你生病时，送药的一杯清水；他是你疲惫时，为你揉捏的那双温柔的大手；他是你伤心落泪时，递来的一方含香的纸巾；他是你无助时，让你依靠的宽厚的肩膀；他是你受到伤害时，第一个冲出来为你遮风拦雨的胸膛；他是每天夜里，为了你的性福而燃烧自己的狼（女人总认为男人的性是自私的，换个角度思考这个问题吧）；他是你命中注定的男人。

                     　——大爱无言，小爱无私·阳光依旧

    爱情就是彼此倾慕，相互关心，互相呵护，一生一世，白头偕老，历经风雨，不离不弃。

                            　　——端午答题·竹林小溪

    爱不成，索性从容一些，与其恨生恨死，不如立刻转身去寻找真正属于自己的那一份感情；爱不成，索性洒脱一些，与其用眼泪泡着自己，不如调整自己的心，去迎接崭新的未来。

——爱不成,不生恨·敏事纳言

    新浪有这本书的连载，点击这里

从平凡到杰出

--《邮差弗雷德》读后感

    读完《邮差弗雷德》这本书，我被弗雷德深深地感染、激励。我想之所以它能感动那么多人，能在众多励志书籍中脱颖而出，主要是因为我们大多数人是平凡的，而该书以平凡的人物在平凡的工作岗位，以不平凡的工作态度和工作能力所创造出来的不平凡的工作效应告诉我们：每个人都可以不平凡。

    让我感受最深刻的是弗雷德们的真诚、激情、创新，这些点点滴滴的平凡的事对接受者能产生深刻的感受，因为这些平凡的事我们所有人都可以做。而在现实生活中，我们往往因为只重视那些过分的不必要的“欲念”，往往忽略了或者根本没意识到这些小事的重要性，往往忽略了自己生活中、工作中的每一件小事所带来的快乐和成就，结果却一事无成，失去了不平凡的机会。弗雷德的感动大家的地方是他自己高度的责任心与创新精神，他从自己平凡琐碎的工作中创造快乐，自己也会获得同等的快乐，是工作被认可的快乐，是因顾客的满意而快乐。在弗雷德的价值观里：提供服务，不是一种责任，而是一次机会；因为他知道，提供帮助比接受帮助更快乐。通过学习弗雷德的精神，我们可以得到人生最重要的东西，即灵魂的安宁和心灵的充实。

    弗雷德和他的工作方式，对于当今社会任何希望有所成就以及脱颖而出的人们来说，都是极为实用的象征。我参加工作以来，都是尽职尽责的把每一件事做好，可时间一长，感觉工作毫无创新、枯燥无味，感觉自己像一个机器人一样，每天在做重复相同的无创新的工作。通过这个故事我才发现并不是工作让自己成为机器人，而是自己让自己成为机器人。如果工作毫无乐趣，每天也就只会简单重复。回想曾有同事跟我抱怨这个工作岗位如何如何不好，现在想起来，我觉得我们应该把每一件小事做好，提高客户的服务质量，从中感受乐趣；在工作思考更好，创新的东西，从中寻找乐趣。

    弗雷德的精神不仅对个人的发展有很好的指导，企业的成长壮大也是非常需要“弗雷德”精神的职员。书中提到，作者在一个会议上做演讲。会议的赞助人之一是一家邮递公司，他们认为“美国邮政”是自己的竞争对手。结果在那次演讲中，他们禁止作者使用弗雷德的例子。我想这是因为有“弗雷德”这种职员的存在，“美国邮政”公司的声誉也得到了提高，自然会带来企业效益的提高。

    弗雷德，深深地影响了我们每一个人，让我们感受到其实我们离成功并非遥遥不可及。弗雷德，在平凡的工作岗位上做出不平凡的工作，我们同样是在平凡的工作岗位，同样也能够做出不平凡的工作，从而从平凡走向杰出。

int main()
{
cout<<"白日依山尽,\n";
return 0;
}

要求是输出"白日依山尽
           黄河入海流
           欲穷千里目
           更上一层楼"

但绝对不能改动main()函数

--------------------

我当然是不会，楼下有个id为slime的哥么倒是给了很多答案

--------------------

----------------

在VC 6.0下测试了一下，2、3、4、5、7都可以，1、6不能达到题目要求

----------------

答案1 回答者想用类来解答，出了问题，这个问题什么原因导致我也不清楚。

答案2 回答者用条件编译的方法解决了问题

答案3、5、7 回答者用宏定义（这样用我还没见过）解决了问题

答案4 回答者偷换main函数了

答案6 。。。看不懂 

This page contains a listing of "difficult to diagnose" error messages and possible fixes. I haven't taught a programming class that uses Visual C++ in several years so this list is probably out of date by now.  It was valid for Microsoft Visual C++ version 6.0 service pack 3.

--------------------------------------------------------------------------------

C1001: INTERNAL COMPILER ERROR (compiler file 'msc1.cpp', line 1786) Please choose the Technical Support command on the Visual C++ Help menu, or open the Technical Support help file for more information

This error results from leaving off the parentheses immediately following the function name in a function header.  To correct the error simply add () to the end of the function name.

--------------------------------------------------------------------------------

C1010: unexpected end of file while looking for precompiled header directive

If your project is an MFC AppWizard created project then this error results from not #including StdAfx.h as the first #include statement (before any other #includes, data declarations, or executable program code).

--------------------------------------------------------------------------------

C1083: Cannot open precompiled header file: 'Debug/<Project-Name>.pch': No such file or directory

This error results from a missing file - the compiled version of StdAfx.cpp. Visual C++ does a poor job of keeping track of this file and frequently "forgets" how to build it. This problem often occurs after restoring a saved workspace from diskette without the Debug directory. To fix the error select StdAfx.cpp from the workspace file list them choose Compile from the Build menu.  If that doesn't work the go to Project -> Settings, select the C/C++ tab, and click the radio button labeled Create Precompiled Headers.

--------------------------------------------------------------------------------

C2001: newline in constant

This error is usually caused by a string or character constant that is missing its closing ' or " symbol.

--------------------------------------------------------------------------------

C2065: '<data-member name>' : undeclared identifier

If this error occurs in one of your member functions then it is generally the result of forgetting the class scope operator in front of the function name in your .cpp file.

--------------------------------------------------------------------------------

C2143: syntax error : missing ';' before 'PCH creation point'

Check each of the #include files to ensure that the closing brace of each class declaration is followed by a semicolon.

--------------------------------------------------------------------------------

C2143: syntax error : missing ';' before '*'

If this error is followed by two C2501 errors then the problem is an undeclared class name within a pointer declaration.

For example, the declaration:

CClass *pObject;

will generate the above error message followed by a C2501 error message for 'CClass' and another C2501 message for 'pObject'.  The problem is that the compiler isn't recognizing CClass as a valid class/type name.  To correct the problem add a #include of the file containing the declaration of CClass (e.g., #include CClass.h)

--------------------------------------------------------------------------------

C2447: missing function header (old-style formal list?)

This error usually results from a missing { or use of a ; instead of a { following the parameter list of a function header.

--------------------------------------------------------------------------------

C2511: '<function-name>' : overloaded member function not found in '<class-name>'

This error results from a mismatch in the parameter list of a member function declaration (.h file) and definition (.ccp file). Check the forward declaration of the function in the .h file and its definition in the .cpp file and ensure that the number of parameters and the type of each parameter match exactly.

--------------------------------------------------------------------------------

C2512: '<constructor-function-name>' : no appropriate default constructor available

This error usually occurs when you implement the constructor function of a derived class and forget to include parameter passing to the base class constructor function.   For example assume that CDerived is derived from CBase and that the CBase constructor function requires one parameter (e.g., int A).  If you define the CDerived constructor function as:

CDerived::CDerived(int A, int B) { ... }

the compiler will issue the above error message on the line containing the function header of CDerived::CDerived() because you haven't provided instructions for routing the parameter A to CBase::CBase().  Because you didn't provide instructions the compiler assumes that CBase::CBase() requires no arguments and it complains because no version of CBase::CBase() has been defined that accepts zero arguments.

If you intended to provide a version of CBase::CBase() that requires no arguments then the error message indicates that you forgot to declare that function in your base class declaration (e.g., in CBase.h).

If CBase::CBase() does require one or more arguments then you must correct the problem by including explicit instructions for passing parameters from the derived class constructor function to the base class constructor function.  The correction for the example above is:

CDerived::CDerived(int A, int B) : CBase(A) { ... }

--------------------------------------------------------------------------------

C2556: '<function-name>' : overloaded functions only differ by return type
C2371: '<function-name>' : redefinition; different basic types

These errors usually result from a mismatch of function type between a .h and .cpp file. Check the forward declaration of the function in the .h file and its definition in the .cpp file and make the function return type identical in both files.

--------------------------------------------------------------------------------

C2601: '<function-name>' : local function definitions are illegal

This error results from defining one function inside the body of another function.   It usually means that you omitted one or more } symbols in the function just before the function named in the error message.

--------------------------------------------------------------------------------

C2653: '<Class-Name>' : is not a class or namespace name

This error usually results from not having #include "StdAfx.h" as the first #include statement in your class.cpp file.  It can also occur if your class definition is in a .h file and you forget to #include that .h file in another file that refers to the class name.

--------------------------------------------------------------------------------

C2661: '<Class-Name>::<Function-Name>' : no overloaded function takes n parameters

This error indicates a mismatch between the parameters used in a function call (e.g., from main.cpp) and the declaration of the function.  The function call is passing n parameters and there is no function declaration that uses that number of parameters.

--------------------------------------------------------------------------------

LNK1104: Cannot open file nafxcwd.lib

This error sometimes occurs when a project uses a class from the MFC but the project settings don't explicitly tell the link editor to look in the MFC libraries. 

Go to Project --> Settings (Build --> Settings in Visual C++ 4.0). On the General tab check the box that says "Use MFC in a Shared DLL".

--------------------------------------------------------------------------------

LNK1168: cannot open Debug\<Project-Name>.exe for writing

This error occurs when the link editor attempts to write to a .exe file that is currently in use. The .exe file of an executing program is write protected until the program is terminated. Look at the status bar at the bottom of your screen and find the icon representing your executable application. Open the application and exit from it. Then select Build.

--------------------------------------------------------------------------------

LNK2001: unresolved external symbol __endthreadex
LNK2001: unresolved external symbol __beginthreadex

These errors result from using an MFC object or function without telling the link editor to search the MFC libraries.

Go to Project --> Settings (Build --> Settings in Visual C++ 4.0). On the General tab check the box that says "Use MFC in a Shared DLL".

--------------------------------------------------------------------------------

LNK2001: unresolved external symbol _main

Your project doesn't contain a function called main().  The error usually results from forgeting to add main.cpp to the project workspace.

--------------------------------------------------------------------------------

<File>.obj : error LNK2001: unresolved external symbol "public: void __thiscall <Class1>::<Function1>(<Type>)"

This a generic form of a LNK2001 error where <File>.obj can be any object file in your project and <Class1>::<Function1>(<Type>) can be any function in any class.  Substitute the specific <File>, <Class>, <Function>, and <Type> in your message into the instructions below to diagnose and correct the problem.

An LNK2001 error means that the link editor is looking for a compiled function and can't find it.  The call to the "missing function" is somewhere in <File>.cpp. Unfortunately, double-clicking on the error message won't take you to the point in <File.cpp> where the function is called but you can search for it with Find or Find In Files.  The function the link editor can't find is a member of <Class>, its name is <Function1>, and its return type is <Type>.

There are two common reasons for a LNK2001 error:

The call in <File>.cpp doesn't match the function prototype in <Class>.h and/or the implementation in <Class>.cpp.  The mismatch may be in the function name, return type, or number and/or type of parameters.   Correction strategies include:
Check that the function name is spelled the same (case sensitive) in all three files (File.cpp, Class.h, and Class.cpp).
Check that the function is actually declared and defined within <Class> - perhaps you defined it as a member of a different class or perhaps you tried to call the function (in <File>.cpp) using an object or object pointer of a different class.
Check that the number and type of parameters in the function implementation (in <Class>.cpp) matches the number and type of parameters declared in the function declaration in <Class>.h.
Check that the number and type of parameters in the function call (in <File>.cpp) matches the number and type of parameters declared in the function header in <Class>.cpp.
The function was never declared or was declared but never defined.  To see if either is the case go to the ClassView window of the Workspace view.  Click the + next to <Class> and find <Function> in the list of member functions.
If <Function> is NOT in the list then it was never declared or defined - add a declaration to the class declaraion in <Class>.h and implement the function in <Class>.cpp.
If <Function> is in the list then right click on it and select Go To Definition from the pop-up menu.  If you get the error message Cannot find definition (implementation) of this function then the function was declared but never defined (implemented).  Implement the function to <Class>.cpp.

--------------------------------------------------------------------------------

LNK2005: <some-long-string-of-mostly-garbage> already defined in <name>.lib(<name>.obj)

This error usually results from including a source code file multiple times. If you recognize any of the names in the message then it probably results from multiple inclusion of one of your own header files. Check to be sure that you've used #ifndef/#define/#endif properly your header files. If you don't recognize the name then it's probably multiple inclusion of a system file (e.g., afxwin.h). Make sure that you haven't explicitly included something in main.cpp that is already included in one of your own header files.   Also check that you haven't #included a .cpp file where you should have #included a .h file.