LINUKS BLOG

人生哲理

2008-03-26T00:22:00.000-07:00

人生哲理

题一：如果你家附近有一家餐厅，东西又贵又难吃，桌上还爬着蟑螂，你会因为它很近很方便，就一而再、再而三地光临吗？

　回答：你一定会说，这是什么烂问题，谁那么笨，花钱买罪受？　可同样的情况换个场合，自己或许就做类似的蠢事。　不少男女都曾经抱怨过他们的情人或配偶品性不端，三心二意，不负责任。明知在一起没什么好的结果，怨恨已经比爱还多，但却“不知道为什么”还是要和他搅和下去，分不了手。说穿了，只是为了不甘，为了习惯，这不也和光临餐厅一样？　——做人，为什么要过于执著？！　

问题二：如果你不小心丢掉100块钱，只知道它好像丢在某个你走过的地方，你会花200块钱的车费去把那100块找回来吗？　回答：一个超级愚蠢的问题。　可是，相似的事情却在人生中不断发生。做错了一件事，明知自己有问题，却怎么也不肯认错，反而花加倍的时间来找藉口，让别人对自己的印象大打折扣。被人骂了一句话，却花了无数时间难过，道理相同。为一件事情发火，不惜损人不利已，不惜血本，不惜时间，只为报复，不也一样无聊？　失去一个人的感情，明知一切已无法挽回，却还是那么伤心，而且一伤心就是好几年，还要借酒浇愁，形销骨立。其实这样一点用也没有，只是损失更多。　——做人，干吗为难自己？！　

问题三：你会因为打开报纸发现每天都有车祸，就不敢出门吗？　回答：这是个什么烂问题？当然不会，那叫因噎废食。　然而，有不少人却曾说：现在的离婚率那么高，让我都不敢谈恋爱了。说得还挺理所当然。也有不少女人看到有关的诸多报道，就对自己的另一半忧心忡忡，这不也是类似的反应？所谓乐观，就是得相信：虽然道路多艰险，我还是那个会平安过马路的人，只要我小心一点，不必害怕过马路。　——做人，先要相信自己。　

问题四：你相信每个人随便都可以成功立业吗？　回答：当然不会相信。　但据观察，有人总是在听完成功人士绞尽脑汁的建议，比如说，多读书，多练习之后，问了另一个问题？那不是很难？　我们都想在3分钟内学好英文，在5分钟内解决所有难题，难道成功是那么容易的吗？改变当然是难的。成功只因不怕困难，所以才能出类拔萃。　有一次坐在出租车上，听见司机看到自己前后都是高档车，兀自感叹：“唉，为什么别人那么有钱，我的钱这么难赚？” 　我心血来潮，问他：“你认为世上有什么钱是好赚的？”他答不出来，过了半晌才说：好像都是别人的钱比较好赚。　其实任何一个成功者都是艰辛取得。我们实在不该抱怨命运。　——做人，依靠自己！　

问题五：你认为完全没有打过篮球的人，可以当很好的篮球教练吗？　回答：当然不可能，外行不可能领导内行。　可是，有许多人，对某个行业完全不了解，只听到那个行业好赚钱，就马上开起业来了。　我看过对穿着没有任何口味、或根本不在乎穿着的人，梦想却是开间服装店；不知道电脑怎么开机的人，却想在网上聊天，结果道听途说，却不反省自己是否专业能力不足，只抱怨时不我与。　——做人，量力而行。　

问题六：相似但不相同的问题：你是否认为，篮球教练不上篮球场，闭着眼睛也可以主导一场完美的胜利？　回答：有病啊，当然是不可能的。　可是却有不少朋友，自己没有时间打理，却拼命投资去开咖啡馆，开餐厅，开自己根本不懂的公司，火烧屁股一样急着把辛苦积攒的积蓄花掉，去当一个稀里糊涂的投资人。亏的总是比赚的多，却觉得自己是因为运气不好，而不是想法出了问题。　——做人，记得反省自己。　

问题七：你宁可永远后悔，也不愿意试一试自己能否转败为胜？　解答：恐怕没有人会说：“对，我就是这样的孬种”吧。　然而，我们却常常在不该打退堂鼓时拼命打退堂鼓，为了恐惧失败而不敢尝试成功。　以关颖珊赢得2000年世界花样滑冰冠军时的精彩表现为例：她一心想赢得第一名，然而在最后一场比赛前，她的总积分只排名第三位，在最后的自选曲项目上，她选择了突破，而不是少出错。在4分钟的长曲中，结合了最高难度的三周跳，并且还大胆地连跳了两次。她也可能会败得很难看，但是她毕竟成功了。　她说：“因为我不想等到失败，才后悔自己还有潜力没发挥。” 　一个中国伟人曾说；胜利的希望和有利情况的恢复，往往产生于再坚持一下的努力之中。　——做人，何妨放手一搏。　

问题八：你的时间无限，长生不老，所以最想做的事，应该无限延期？　回答：不，傻瓜才会这样认为。　然而我们却常说，等我老了，要去环游世界；等我退休，就要去做想做的事情；等孩子长大了，我就可以…… 　我们都以为自己有无限的时间与精力。其实我们可以一步一步实现理想，不必在等待中徒耗生命。如果现在就能一步一步努力接近，我们就不会活了半生，却出现自己最不想看到的结局。　——做人，要活在当下。

爆笑80后

2008-03-12T18:03:00.000-07:00

爆笑80后

1、早上临上班，和老公吻别。我：亲一个！老公：啵！我:再亲一个!老公:啵!:还要嘛～～～老公:……流氓!

2 、昨天晚上睡觉,跟老公抢他的胳膊～，老公抵死不从!我急了,就冒出了一句: 衲,你就从了师太吧!老公笑到手软。于是我得逞。

3、某日,我早起,给他留了200元钱放在桌子上(我是家里的财政大臣)。上班后,摸着他已起床,就短他: 老公,桌上是给你昨夜的服务费。他回:全套服务才200呀? 赶明儿找个富婆去。。。

4、老公：今天坐车人特多，不过在拥挤的车上看到美女了！我:....怒！老公:还跟我搭讪呢！我:她跟你说什么``(吃醋) 老公:离我远点!

5、老公学习无聊中会短信骚扰:小妞,给大爷我笑一个!我回:客官请自重,小女子卖身不艺! 、我出差在外:臣妾今晚不能来侍寝,也请陛下早些歇息,养足精神,明日再来翻妾的牌子。老公:朕有后宫佳丽三千,此事爱妃不必太过忧虑,还须耐住寂寞:看来今晚非杀回来****不可!老公:说笑说笑,朕的后宫牌子虽多,写的可都是个人的名字！

6、如厕无聊中，和老公用喊的方式沟通：小子，给主子唱个曲儿！老公：无语中。。。我：怎么？怕主子我付不起银子？老公：之前赊的账还没还呢！

2008-02-14T17:23:00.000-08:00

只有basic,而没有project,只会让学习失去目标...

2008-02-14T17:19:00.000-08:00

Basic 是最为重要的,所以要有一块专门的地儿去做这事儿.

&.

ThinkingJava3_c02 : javadoc---Java API 文档生成器的使用 javadoc Example.java -d dir

保留两位小数 DecimalFormat的使用

java.text.DecimalFormat df =new java.text.DecimalFormat("0.00");
String str1=df.format(50000);
String str2=df.format(8);

equals() 与==的使用

String s="Hello" "Hello" s=="Hello":s.equals("Hello") true:true

String s=new String("Hello"); "Hello" s=="Hello":s.equals("Hello") false:true

==与!=比较的是引用(reference)

equal比较的是内容(content)/上下文

如果是比较两个对象时,而又没有重写equals()方法,只能调用object中的equals()方法,就不会相等,除非二者有相等的hashcode,而如果要想得到相等的结果,只是能重写hashcode的equals()方法

关于赋值的一点奇妙的现象

class Number{
int i;
}
class E072_Assign{
public static void main(String[] args){
Number n1=new Number();
Number n2=new Number();
n1.i=9;
n2.i=27;
System.out.println("1: n1.i="+n1.i+" "+"n2.i="+n2.i);
n1=n2;
System.out.println("2: n1.i="+n1.i+" "+"n2.i="+n2.i);
n1.i=47;
System.out.println("3: n1.i="+n1.i+" "+"n2.i="+n2.i);
}
}

首先研究一下上面的这段程序代码,如果没有仔细认真思考的话,我们很容易得出错误的结果的

而正确的结果是这样的:

1: n1.i=9 n2.i=27
2: n1.i=27 n2.i=27
3: n1.i=47 n2.i=47

其中最让人不可理解的主要是第三条,主要是因为赋值主要是对reference修改的.因而修改n1.i就会关联到n2

finalize() VS System.gc()

ystem.gc()建议（但不是要求）java虚拟机执行垃圾回收
一个对象的finalize()方法在它被垃圾回收器回收时被调用

inalize的什么时候执行，是无法预料的，一般来说不会去写的。
于System.gc()来说，系统的垃圾回收不是每时每刻都在做的，刚被释放的对象一定马上会被虚拟机处理，在内存很紧张的情况下，可以使用这个方法来强制让虚拟机进行垃圾回收，但是这样做的效率是低下的，执行时会花掉一些时间。

public class E12_FinalizeAlwaysCalled {
protected void finalize() {
System.out.println("Finalize called");
}
public static void main(String args[]) {
new E12_FinalizeAlwaysCalled();
System.gc();//如果这里没有,将会是另一番景象
}
} ///:~

关于二维数组的几点体会

1.double数组的定义: double[][] array=new double[vSize1][vSize2];

2.二维数组的for循环:

for(int i=0;i<array.length;i++){ // 这里的length是第一维数组的大小

for(int j=0;j<array[i].length;i++){ //这里的length是第二维数组的大小

...

}

3.对于main函数中的有返回值的方法调用:

public static void maint(String[] args){

double[][] array=TwoDDoubleArray(3,3,1.0,10.0);// 注意这里没有new,并且前面要加上类型,只有方法名加参数

}

public && protected && friendly && private:

1. public 任何类和方法都可以访问
2. protect 可被同一个包内访问,包外的话,只能由继承该类的子类访问。
3. fiendly 同一个包内的才可以访问。
4. private 只能在该类的内部访问

final && static :

1. 被static修饰的成员变量和成员方法独立于该类的任何对象。也就是说，它不依赖类特定的实例，被类的所有实例共享。只要类被加载,该成员变量就会存在,不引用任何对象. 静态变量在内存中只有一个拷贝,而实例变量,在每创建一个对像时就会有一个拷贝.

2. final变量（常量）
用final修饰的成员变量表示常量，值一旦给定就无法改变！

3. static final用来修饰成员变量和成员方法，可简单理解为“全局常量”！
对于变量，表示一旦给值就不可修改，并且通过类名可以访问。
对于方法，表示不可覆盖，并且可以通过类名直接访问。

&.

Abstract:

1.一个没有Abstract方法的抽象类是不能在main函数中实例化的.

2.一个Abstract类是可以继承并且实例化的.

3.如果一个类没有足够的信息来描述一个对象的话,那么这个类就是一个抽象类

4.在abstractclass方式中，Demo可以有自己的数据成员，也可以有非abstarct的成员方法，而在interface方式的实现中，Demo只能够有静态的不能被修改的数据成员（也就是必须是staticfinal的，不过在interface中一般不定义数据成员），所有的成员方法都是abstract的。从某种意义上说，interface是一种特殊形式的abstractclass。
从编程的角度来看，abstractclass和interface都可以用来实现"designbycontract"的思想。但是在具体的使用上面还是有一些区别的。
首先，abstractclass在Java语言中表示的是一种继承关系，一个类只能使用一次继承关系。但是，一个类却可以实现多个interface。也许，这是Java语言的设计者在考虑Java对于多重继承的支持方面的一种折中考虑吧。
其次，在abstractclass的定义中，我们可以赋予方法的默认行为。但是在interface的定义中，方法却不能拥有默认行为，为了绕过这个限制，必须使用委托，但是这会增加一些复杂性，有时会造成很大的麻烦。
5.关于接口和另外一个不知道是什么东西接口是需要实现其所有方法的,而另外一个则不需要实现所有方法,而只需要实现需要实现的方法即可@??????

2008-01-23T00:48:00.000-08:00

需要一点规划

突然间想写点什么,很突然,真的,都有点措手不及~~~!
有些时候觉得,虽然朋友也不少,值真正知心的没几个,所以说想找个人说说聊聊,但好像每个人都很忙,都在忙自个的事儿.........

人没个目标不中,一辈子的时间虽然不能说是漫长,但也不能总是即兴发挥...写作得有个大纲,人生得有个规划!有些时候觉得有一种文体叫做散文,就很好---形散神不散.时间如流水,人生如戏,不仅要做一个好的演员也要做一个出色的导演.

本文提纲罗列如下:

1.做人做事得有个规划

2.为什么要规划

3.怎样做规划

关于第一点,上面已经给出了引子啦,就不再重述了

至于第二点,不管是以往还是在平时思想中,都多少有些体现,但是问题出在于没有很好地理解其很重要性,或者没有做到实处.有些时候规划不单单指指划划,更重要的量化,尽量使其规范化.就像是编程一样,只有量化规范化后才能更方便更容易地信手拈来.而不用花费更大的脑力去记去背还一定能做得好.至于其它的多么很重要就不再多说了吧

而怎样才能做到规划呢,可能是应该详细说明的重点.

first,一切东西都要量化,就是不能量化的,也得有个大概.

second,不能再做什么东西,都以顺序的方式啦,像记流水账一样,要分阶段,分目标地行进.

the third,不要贪多,贪多容易生产消化不良,和粗制滥造...但也不能走以前的老路---为自己的懒惰去开拓.但不能是尽量的去熟练它.

做工程,做项目都得有个蓝图,只有尽可能合理优良的蓝图才能可做出好的工程项目,要不然一切都是枉然.

2007-11-02T00:07:00.000-07:00

Java 中的多线程

import java.awt.*;
public class MainFrame extends Frame implements Runnable
{
public MainFrame(String title)
{
super(title);
……
new Thread(this).start();
……
}
……
public void run()
{
try
{
while(true)
{
this.sleep(1000);
//这里写调用的方法名

}
}
}
}

2007-11-01T00:28:00.000-07:00

Java String

String s;//创建一个引用变量
String s="abc";//创建一个字符对象"abc"和一个引用变量s
String s=new String("abc");//创建两个字符对象,和两个引用变量

equal

String s=new String(); s="abc";//先创建一个空间对象,而后又用引用指向"abc"这个字符对象.

java 术语:constant pool 字符串池

2007-10-31T23:58:00.000-07:00

A little knowladge in SmartPhone

Graphics, Windowing, and Events Subsystem---gwes.exe
图形、开窗口和事件子系统 (GWES) 负责所有图形输出以及与用户的所有交互。
shell32.exe
动态链接库函数启动器，相当于PC中的Rundll32.dll
不过另一说是相当于EXPLORER……反正是基础进程。
==========================
Gwes.exe
图形、开窗口和事件子系统 (GWES) 负责所有图形输出以及与用户的所有交互。

驻留在 GWES 地址空间中的驱动程序包括显示驱动程序、打印机驱动程序、键盘驱动程序、

鼠标驱动程序和触摸屏驱动程序。
===========================
device.exe
是设备管理器，也是所有驱动程序所运行的进程。device.exe为每个驱动程序创建一个线程

。
=================================
nk.exe（OAL 和内核） nk.exe (OAL)
kernel.dll（内核）从 CE 6.0 开始，OEM 代码从 CE 内核代码中分离
=================================
filesys.exe filesys.dll 注册表、文件系统和属性数据库
=================================
device.exe device.dll 管理内核模式设备驱动程序
device.exe udevice.exe 新增到 CE 6.0 中，用于管理用户模式设备驱动程序的独立进程
=================================
services.exe servicesd.exe 系统服务的宿主进程
services.exe services.exe 用于配置服务的命令行接口
=================================
cprog.exe Micro$oft 的电话程序
=====================
repllog.exe 使用串口进行同步
据MS说这个程序让COM打开40秒
=================
MemMaid.exe
凸！这个就使你看进程的东西！
==================
STK.exe 中国移动……

SIM卡应用相关，准确地说是SIM Toolkit，但是如果是行货的话肯定有移动在里面OOXX过了

……
==================
tmail.exe
发送邮件的
====================
smspatch.exe
smsreceiver.exe
这两个应该是和短信有关的
下面那个是管理从数据库中存取短信
==========================
xFlashMan.exe 同步日历、联系人、任务等的进程
AFlashman.exe = Appointments
CFlashman.exe = Contacts
不过似乎没有TFlashman.exe = Tasks ……以前的CE系统曾经有过
===========================
USSd.exe
非结构化补充数据业务（USSD Unstructured Supplementary Service Data）是一种基于GSM

网络的新型实时交互式数据业务，它是在GSM的短消息系统技术基础上推出的一种全新业务。

据说有的系统上没有这个
===========================
connmgr.exe
Connection Manager ……看的懂英语的都明白这个是什么意思了
就是管理连接的（这个不是同步那个哦~是什么WLAN，BT，Irda之类的）

private int tootalImages=10;//注意这里的作用
awt thread当为显露的时候,调用patint方法.

if(jLabel.getText().equal("")){
rs=stm.executeQuery("select * from student");
}else{
rs=stm.executeQuery("select * from student where zjm='"+jLabel.getText()

+"'");
}

2007-09-25T19:10:00.000-07:00

关于eclipse连接JDBC的问题

第一步：安装jdbc,我们所需的是SQL Server 2000 Driver for JDBC Service Pack 3

点击java访问sqlserver服务器驱动程序安装程序setup.exe（可以到微软网站下载 http://www.microsoft.com/downloads/details.aspx?familyid=07287B11-0502-461A-B138-2AA54BFDC03A&displaylang=en下载）

第二步：设置系统变量classpath

假设SQL Server for JDBC 驱动程序安装在d：jdbc，安装完毕后应在d:jdbclib下生成3个.jar文件，则classpath应该设置如下：

classpath：＝.;…;d:jdbclib; d:jdbclibmssqlserver.jar; d:jdbclibmsutil.jar; d:jdbclibmsbase.jar;

设置时要在最前面的点号和分号

注意：事实上这些工作做完之后并没有数据库连接程序仍然连接不上，正确的做法应该是将JDBC驱动程序安装目录下的3个.jar文件通过Add External JARs添加到Java Build Path中,其它的工作都是多余的。

2007-09-18T20:11:00.000-07:00

Programming Can Ruin Your Life

There are many essays and articles extolling the virtues of becoming a great programmer. You’ll have a sharp mind, great abstract reasoning skills, and a chance to become wealthy by working mere hours a day. This is what you’ve heard, right?

Sadly, no one ever tells you about the ways in which it will adversely affect your life. The physical effects are obvious. You’ll spend most of your time sitting, probably in an uncomfortable chair that doesn’t promote good posture. You’ll fuel yourself with food that is readily available, meaning it’s more than likely processed and full of sugar and you’ll likely choose either coffee or soda to stave off the drowsiness. A coworker once remarked, “If it doesn’t come out of a vending machine, programmers don’t eat it.”

But I’m not particularly interested in the health risks, as I said, they’re obvious. So what am I talking about? Programming changes more than your body. Programming changes the way you think. You might hear a programmer say, “I like python because it matches the way I think.” Or is it really that they’ve learned to think in python? Regardless of the language employed, you think differently when you program. No decent programmer will deny that. This is why it’s often so hard to explain to someone “how you do that” because, as clear as your explanation may be, you simply think differently. It is this change in thinking that can ruin your life.

The application of programming specific processes and habits to the everyday is where peril lies. The same traits that make you a great programmer can make you an awkward, misunderstood and miserable human being.

Programming presents you with a problem and allows you to eventually solve it provided you don’t quit. A solution is out there somewhere. Make enough attempts and chances are you’ll eventually prevail. Aren’t computers great? They afford a large degree of freedom in problem solving. If nothing else, you are able to make as may attempts as you please and it will happily execute each one. This instills in you a sense that failure is not final. Any obstacle can be hurdled. This is not true in the real world. While you may find second chances now and again, the wheels that turn in the big blue room are largely unforgiving. Time marches on in one direction.

When faced with an interesting programming problem your mind will chew it over in the background. Maybe it’s an algorithm you need to develop, maybe it’s a tricky architecture problem, maybe it’s data that needs to be modeled. It doesn’t matter. Your mind will quietly work the problem over in search of a solution. The “ah-ha!” moment will come when you’re in the shower, or playing Tetris. This practice of constant churning will slowly work its way into the rest of your life. Each problem or puzzle you encounter will start it’s own thread; the toughest and most troubling of which will be blocking.

A program is highly malleable. You can make a nearly unlimited number of changes. You can re-implement. You can optimize. You can run the compile-test-debug cycle ad infinitum. Make a change, see a result. Life is not like this. Every action you take is followed by a commit and the transaction cannot be rolled back. You can continue to make changes and optimizations as you move forward but the effects of these will not be immediately apparent. The instant feedback of development is sorely lacking in real life. Furthermore, your changes might simply be ignored. Data will be skipped. Blocks will not be executed. Optimizations will go unnoticed. The world is resistant to your tinkering.

Programmers become obsessed with perfection. This is why they are constantly talking about rewrites. They cannot resist optimum solutions. Perfection requires tossing aside mediocre ideas in search of great ones. A good programmer would rather leave a problem temporarily unsolved than solve it poorly. A good solution takes into account all predictable outcomes and solves the largest number of them in the most efficient way. This mindset prevents you from writing code with limited utility and life span. While it’s a wonderful trait to have in programming, the demons of scope and efficiency will start to assert themselves on your ordinary life. You will avoid taking care of simple things because the solution is inelegant or simply feels wrong. Time to think will no doubt yield a better result, you’ll say.

The obsession with perfection develops a forward-thinking mindset. The ability to anticipate provides a huge advantage because you won’t waste your time implementing solutions that ultimately fail due to short-sightedness or lack of imagination. You will constantly be mapping out flows and running the permutations through your head. Back in the real world, you will find yourself piecing together plans of breath-taking size and beauty that simultaneously resolve multiple problems and fulfill numerous dreams. You will attempt to kill every bird with one stone. The impossibility of actualizing these plans will be agonizing, yet your mind will continue to pour over every detail as it seeks to anticipate every possible outcome and construct the perfect solution.

Everything is now data. Every bit is worthy of attention. Every interaction is worthy of analysis. Your mind has been trained to do this since it is usually the insignificant or subtle bits that have to be rooted out when debugging. You will find it frustrating that everyone else does not collect and analyze data. You will notice details that others simply gloss over. Your penchant for detail and over-analysis will earn you strange glances and confused shrugs. Your decision making process will resemble that of your peers less and less.

The frantic pace of the software world will instill in you a sense of panic and urgency. You must do everything now. Tomorrow is too late. The thought of working constantly will no longer seem foreign or ridiculous. You will spend your free time feeling guilty about not working. But you will be working. Your hands may not be at the keyboard, but your mind will be.

The romanticized story of young upstarts toiling away in a garage to build the world’s next great company is alluring. It’s easy to convince yourself that the dream is there for the taking. But understand that there are many factors you cannot control. Luck and timing being but two. Don’t miss the life you have in the search for the one you think you want. To quote John Lennon, “Life is what happens while you are busy making other plans.” But perhaps Pascal said it best, “We never keep to the present. We … anticipate the future as if we found it too slow in coming and were trying to hurry it up, or we recall the past as if to stay its too rapid flight. We are so unwise that we wander about in times that do not belong to us and do not think of the only one that does; so vain that we dream of times that are not and blindly flee the only one that is… [We] think of how we are going to arrange things over which we have no control for a time we can never be sure of reaching… Thus we never actually live, but hope to live, and since we are always planning how to be happy, it is inevitable that we should never be so.”

Is programming the road to ruin? Or is it that those with a predilection for detail and mental gymnastics find themselves drawn to it. Perhaps it simply exacerbates a pre-existing mindset. There are certainly other traits (stereotypical or not) that most programmers seem to share. I have focused mainly on the negative impacts, but there are certainly positive ones as well. All things listed as bad can be good if simply kept in check. Obsession is dangerous, and anything great requires obsession. Programming is no exception.

2007-09-10T01:32:00.000-07:00

一点心得

7.18

不管东西有多么微小,只要能方便,或者是好的东西都应该积极去学习,不应该采取排斥的态度.

2007-09-10T01:31:00.000-07:00

关于windows控制面板的小知识

7.15

control 控制面板
rundll32.exe shell32.dll,Control_RunDLL appwiz.cpl,,1添加删除模块

2007-09-10T01:30:00.000-07:00

闲着无聊

Music flow around the ear, it's a beautiful thing. I like ,though i was weak in the music distance(才能). Thinking about the cheer life everyday, i know i like to do what, but don't know what i really want to do! Maybe the interesting is disturb(区别) from the i like. The interesting 强调 the long period and the like express the 快感. Touched with the engeener(工程师) made me thinking much. Maybe thinking much more than the (行为) will let people tired. And the failure come from the un-signral(无意义)'s thinking. For me, not thinking much, just do it! do it!

reading book all the time, not for anybody, just for yourself.

2007-09-10T01:29:00.000-07:00

小文一篇

静静的调整好彼此的心情，小心问对方，做不了爱人我们做什么?

“那我们做知己吧”！她对他说。他说：“不，我承受不了那份永久的牵挂与思念，没有人能做好一辈子的知己。”

　　“那我们做情人吧”！她对他说。他说：“不，因为你是善良的女人，尽管我们的感情没有阳光的青睐，但是这样暧昧的词语是对我们的玷污”。

　　“那我们做兄妹吧”！她对他说。他说：“不，我们的爱早已越过了兄妹之间的亲情，会有哥哥用带着柔情爱意的目光看待妹妹的吗？我不会做这样的哥哥”。

　　“那我们做朋友吧，我只能给你这个了”她对他说。他说：“不，在我的心里你早已经是我的爱人了，做了朋友的身份，我无法面对你和你的另一半，也无法想象你和你另一半在一起的时候……我也无法抗拒和我的另一半同床共眠的时候不去想你。

　　“唉，我们还是做仇人吧”！他对她说。既然我们都改变不了自己的命运，此生注定了没有相互厮守一生的幸福，与其这样相互的念着、痛着，仇恨的远离对方的视线，永远的找寻不到对方，也许会是一种最好的解脱。

　　她愕然了，他哭了。无法想象最后能给与对方的竟然是这样的结局。但是他们明白，也只有这样选择，才可以保留住对方的那份善良与纯洁，也不再会去伤害更多的人。
　
　　从此，他们消失了，没有相互的祝福，就这样静静的消失在茫茫的人海中。

　　两副柔弱的肩膀，承受不住另类的爱情。

　　爱就这样不堪承受生命之重。

　　也许……恨比爱容易……

2007-09-07T17:43:00.000-07:00

Have a rest in my blog for a month

Don't know why clearly for what, stop bloging for the daily in my life . Maybe the busy job, maybe the disinsist character,maybe the bad mood. But i find it should be renew begin today. The life is busy and the time is not enough, but there should not dissort in the future life road.

I said to others i like programing. no ever it is a ture or not, i should not deceive others and myself. Having programing for program is the biggest advantage for the programer. Since i like programing, i should know well and can make full use of the advantage of the programing .Make a long period program for my life , and though my road as the programing exactly......

2007-07-19T17:17:00.000-07:00

The record of learning of thinking JAVA

*动态绑定是java的缺省行为,因此无需添加什么额外的关键词就能获得多态性.

"你是一个Shape对吧,好,我知道你可以erase()和draw(),这这么做,照顾好自己."

通常在有些设计方案中,你只想让基类去表示由其派生出的类的接口.也就是你不想让人创建一个基类的对象,而只是想把对象上传给它,以期能使用这个类的接口.这样你就需要使用abstract关键词来把这个类做成抽象类.

abstract就像是一个声明"由这个类所派生出的所有的类都有这个方法,但是它的实现不在这里" 的存根.如果有个类继承了这个abstract类,那么它要么实现这个方法,要么也是一个abstract类.

Chapter2
5.这个对象不是primitive型的.
char c='x';
Character C=new Character(c);

Character C=new Character('x');

Java中的数组
实际上所有编程语言都有数组,使用C和C++的数组是有风险的,因为在它们眼里,数组只是一段内存.如果程序访问到数组之外的内存,或者还未进行初始化就使用了这些内存,那么很有可能会发生一些无法预料的后果.

Java对象的生命同期同primitive的不同.当你用new创建java对象之后,它会晃荡作用域外面.如:
{
String s=new String("a string");
}//End of scope
s这个reference会在作用域结束之后消失.但是s所指的那个String仍然还占着内存.在这段代码里,你已经没法访问这个对象了,因为唯一指向它那个的reference现在已经出了作用域.

8.如果万物皆对象,那么特定类型的对象的特征和行为又是由什么决定的?
class这个关键词,它的意思是"现在我要告诉你这种新类型的对象都有些什么特征."

当你定义类的时候(java编程要做的就是定义类,创建这些类的对象,然后再向这些对象发送消息),你可以往类里放两种元素:数据(field,有时也被称为数据成员),以及方法(method,有时也被称为成员函数member function).数据可以是任何类型的,能通过reference进行操控的对象.它也可以是任何一种primitive数据(这时它就不是reference了).如果它是一个对象的reference,那么你就必须用一种被称为构造函数(construtor)的特殊方法对它进行初始化,这样才能确保将它连上一个真实的对象(用new,就像前面看到的).如果这是个primitive数据,那么你可以在定义的时候直接对它进行初始化.

9.下面就是一个带数据成员的类:
class DataOnly{
int i;
float f;
boolean b;
}

DataOnly类只保存数据,要想理解方法是怎么工作的,你必须先理解参数(argument)和返回值(return value)的概念.

10.当primitive数据成为类的成员时,它会得到一个默认值,但只有在"变量被用作类的成员"时,java才能确保它获得这些默认值.

方法的基本的组成包括方法的名字,参数,返回类型,以及方法的正文.
returnType methodName(/*Argument list*/){
/*Method body*/
}

2007-07-08T20:38:00.000-07:00

编程题

32.Question:

编程题: 写一个Singleton出来。

Answer:

　　Singleton模式主要作用是保证在Java应用程序中，一个类Class只有一个实例

存在。

　　一般Singleton模式通常有几种种形式:

　　第一种形式: 定义一个类，它的构造函数为private的，它有一个static的

private的该类变量，在类初始化时实例话，通过一个public的getInstance方法获

取对它的引用,继而调用其中的方法。

public class Singleton {
　　private Singleton(){}
　　//在自己内部定义自己一个实例，是不是很奇怪？
　　//注意这是private 只供内部调用
　　private static Singleton instance = new Singleton();
　　//这里提供了一个供外部访问本class的静态方法，可以直接访问　　
　　public static Singleton getInstance() {
　　　　return instance; 　　
　　 }
}

　　第二种形式:

public class Singleton {
　　private static Singleton instance = null;
　　public static synchronized Singleton getInstance() {
　　//这个方法比上面有所改进，不用每次都进行生成对象，只是第一次　　　　
　　//使用时生成实例，提高了效率！
　　if (instance==null)
　　　　instance＝new Singleton();
return instance; 　　}
}

　　其他形式:

　　定义一个类，它的构造函数为private的，所有方法为static的。

　　一般认为第一种形式要更加安全些

　　第三十三 Hashtable和HashMap

　　Hashtable继承自Dictionary类，而HashMap是Java1.2引进的Map interface的

一个实现

　　HashMap允许将null作为一个entry的key或者value，而Hashtable不允许

　　还有就是，HashMap把Hashtable的contains方法去掉了，改成containsvalue和

containsKey。因为contains方法容易让人引起误解。

　　最大的不同是，Hashtable的方法是Synchronize的，而HashMap不是，在多个线

程访问Hashtable时，不需要自己为它的方法实现同步，而HashMap就必须为之提供

外同步。

　　Hashtable和HashMap采用的hash/rehash算法都大概一样，所以性能不会有很大

的差异。

2007-07-03T17:22:00.000-07:00

Switch用法

31.Question:

switch是否能作用在byte上，是否能作用在long上，是否能作用在String上?

Answer:　　

switch（expr1）中，expr1是一个整数表达式。因此传递给 switch 和 case 语句的参数应该是 int、 short、 char 或者 byte。long,string 都不能作用于switch。

2007-07-03T17:19:00.000-07:00

Decision

If you make a decision,would you like to finish it in any condition. Maybe you can do it. But i find i can't. So something and chance escaped from my hand silence. So i have no success today.
Recently, decide to prepare for the coming master test i told to myself. But day by day, had no change, no progress, no goal.

那你就把你想作的事情,安能实现的难易和时间的长短分类,然后现在去做最简单最容易实现最能让自己开心的事情.!!!-------------来自一位朋友的衷告.

Have dreamed to have a job in a software company. When touched with the engeers from the small software company, i become to re-check the dream of being a member in the small software company. In my opinion ,they are confused with what they want to do like me . If i become a member of them, what i will be ? confused, don't kown what to do? Have no significance.

So decide to take the master test return to the school is the only correct choice.

2007-07-01T06:15:00.000-07:00

值传递与引用传递

30.Question:

当一个对象被当作参数传递到一个方法后，此方法可改变这个对象的属性，并可返回变化后的结果，那么这里到底是值传递还是引用传递?

Answer:　

　是值传递。Java 编程语言只由值传递参数。当一个对象实例作为一个参数被传递到方法中时，参数的值就是对该对象的引用。对象的内容可以在被调用的方法中改变，但对象的引用是永远不会改变的。

2007-06-29T17:43:00.000-07:00

判断

29.Question:

两个对象值相同(x.equals(y) == true)，但却可有不同的hash code，这句话对不对?

Answer:　　

不对，有相同的hash code。

Very happy to move to the new office last night. !!!!

2007-06-29T01:23:00.000-07:00

One C problem

28.Question:

编程题: 用最有效率的方法算出2乘以8等於几?

　　有C背景的程序员特别喜欢问这种问题。

　 Answer:

　2 << 3

2007-06-26T18:29:00.000-07:00

Return语句

27.Questiontry:

{}里有一个return语句，那么紧跟在这个try后的finally {}里的code会不会被执行，什么时候被执行，在return前还是后?

Answer:　

　会执行，在return前执行。

2007-06-26T01:00:00.000-07:00

Normal life

I forgot the thing whether i had did when the other pointed it out yesterday. I become to found the serious of the question. My normal life become to changed for some thing. May it is not because the others, maybe the mainly reason is myself.

Many times, i don't like search the memory of the remember. And the normal program is recreate the new wheel for the car. For some reason, i have the create thinking. But for the more fault, i like waste my brain resource. Step by step, the normal life maybe disturb by the un-normal thinking.

We have a normal job life half of a month ago. By accident, the big smoke break the normal silence. In the normal understand, i trust the environment would produce great influence to the life.

I have a normal emotion life half year ago.But i find it's had not yet normal again.Recall the one person, to do what you want. Don't think much, and don't prepare for the future. Alone man is beautiful.But now, mother let me to think of myself, and advise me to search for the other part. But have no experience, and have no standard for it. In the last Sunday, i compared with a friend of girl to have meal. She is a clever girl and can bear the larger fault of me. In the primary opinion, she is a good girl. But i find that i can't let me to accept her for some reason. So we told a lot in the park about the possibility of us. And we were agree on the recoganize of it in clamness. Although we can't be lover, we can be good friends.

In my opinion, the most people like spending happy time with the normal life. But i don't know why what i have to do with the normal life. Don't know how many times i have made the word "I have decided to get the master test to escape from the reality of now", but i find i am a person who can't come true my own promise. So it produce the failure in the final.

2007-06-24T02:27:00.000-07:00

Don't understand!

......