<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
  <channel>
    <title>Allen</title>
    <description>[center][b][color=navy]... 知我者谓我心忧，不知我者谓我何求 ...[/color][/b][center]</description>
    <link>http://allen.javaeye.com</link>
    <language>UTF-8</language>
    <copyright>Copyright 2003-2008, JavaEye.com</copyright>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <generator>JavaEye - 做最棒的软件开发交流社区</generator>
      <item>
        <title>今天看到关于Java 7代码书写上的一些方便的新特性</title>
        <author>Allen</author>
        <description>
          <![CDATA[
          <br/>
          作者: <a href="http://allen.javaeye.com">Allen</a>&nbsp;
          链接：<a href="http://allen.javaeye.com/blog/53215" style="color:red;">http://allen.javaeye.com/blog/53215</a>&nbsp;
          发表时间: 2007年02月08日
          <br/><br/>
          声明：本文系JavaEye网站发布的原创博客文章，未经作者书面许可，严禁任何网站转载本文，否则必将追究法律责任！
          <br/><br/>
          <div id="ArticleTitle">来源：<a href="http://www-128.ibm.com/developerworks/java/library/j-java2007.html"><font color="#660099" face="Verdana">http://www-128.ibm.com/developerworks/java/library/j-java2007.html</font></a></div>
<div>作者：<a href="http://www-128.ibm.com/developerworks/java/library/j-java2007.html#author"><em><font color="#494949"><strong>Elliotte Harold</strong></font></em></a></div>
<div></div>
<div></div>
<div></div>
<div><em><font size="2" color="#666699" face="Courier New">以下文章的中文部分是我自己的一点小评价，它们中的一些也许不会出现在正式的Java 7当中，因为有的目前还只是提案而已（尽管提案被通过的机会很大）。</font></em></div>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><a name="N10094" id="N10094"><span class="atitle"><strong><font size="4" color="#000000" face="Georgia">Looking forward to Java 7</font></strong></span></a></p>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">Dolphin will not be released in 2007. Next year is a more realistic goal. That said, work is underway and some features may make their debut as standard extensions earlier, or at least as betas.</font></p>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000000" face="Georgia">我也觉得必须要留够时间给Mustang来折腾折腾啊，要是弄得和Tiger一样短命且孤芳自赏的话，SUN和一干Java幕后势力的面子也不好看哟。</font></p>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">It's unfortunate that it's far, far easier to add features to a language than to take them away. Almost inevitably, languages get more complex and confusing over time, not less. Even features that look good in isolation become problematic when piled on top of each other.</font></p>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">Unfortunately, the Java community has not yet learned this lesson, despite the debacle that is generics. There's just something about new syntax that's too cool and exciting for language designers to resist, even when it doesn't solve any actual problems. Thus the huge clamor for new language features in Java 7, including closures, multiple inheritance, and operator overloading.</font></p>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">I suspect that before the year is out we will see closures in a Java 7 beta, and we may well see operator overloading (50/50 chance), but multiple inheritance simply will not happen. Too much of Java is based on a singly rooted inheritance hierarchy. There's no plausible way to retrofit multiple inheritance into the language.</font></p>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">Currently there's a lot of syntax sugar on the table, some of which makes sense, some of which doesn't. A lot of the proposals focus on replacing methods like <font color="#990000"><code>get<em>Foo</em>()</code></font> with operators like <code><font color="#990000">-&gt;</font></code>.</font></p>
<ul>
    <li>
    <div><a name="lists" id="lists"><span class="smalltitle"><strong><font size="3" color="#000000" face="Georgia">Lists</font></strong></span></a></div>
    </li>
</ul>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">The first possibility is using array syntax for collections access. For example, instead of writing this:</font></p>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word">
<table cellspacing="0" border="0" width="324" cellpadding="0" style="WIDTH: 324px; HEIGHT: 83px">
    <tbody>
        <tr>
            <td class="code-outline">
            <pre class="displaycode"><font color="#990000">List content = new LinkedList(10);
content.add(0, &quot;Fred&quot;);
content.add(1, &quot;Barney&quot;);
String name = content.get(0);</font></pre>
            </td>
        </tr>
    </tbody>
</table>
</div>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">you could instead write this:</font></p>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word">
<table cellspacing="0" border="0" width="327" cellpadding="0" style="WIDTH: 327px; HEIGHT: 83px">
    <tbody>
        <tr>
            <td class="code-outline">
            <pre class="displaycode"><font color="#990000">List content = new LinkedList(10);
content[0] = &quot;Fred&quot;;
content[1] = &quot;Barney&quot;;
String name = content[0];</font></pre>
            </td>
        </tr>
    </tbody>
</table>
</div>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">Another possibility is allowing array initializer syntax for lists. For example:</font></p>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word">
<table cellspacing="0" border="0" width="449" cellpadding="0" style="WIDTH: 449px; HEIGHT: 38px">
    <tbody>
        <tr>
            <td class="code-outline">
            <pre class="displaycode"><font color="#000066" face="Georgia"><font color="#990000" face="Courier New">LinkedList content = {&quot;Fred&quot;, &quot;Barney&quot;, &quot;Wilma&quot;, &quot;Betty&quot;}</font></font></pre>
            </td>
        </tr>
    </tbody>
</table>
</div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word">这样的类似于数组的各项对集合的操作的写法可以说是很友好的形式，可以另人更加直观的看到赋值和取值的语句。这个对那些很熟悉C语言的人事来说应该是一件好事情，就是不知道集合的操作速度会不会受到影响&hellip;&hellip;</div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><br />
</div>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">Both of these proposals could be implemented with a little compiler magic without changing the virtual machine (VM), an important characteristic for any revised syntax. Neither proposal would invalidate or redefine any existing source code, an even more important issue for new syntax.</font></p>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">One language feature that might make a real difference in developers' productivity would be built-in primitives for managing tables, trees, and maps, such as you encounter when working with XML and SQL. Projects like E4X in JavaScript land and C&omega; and Linq in the Microsoft world are pioneering this idea, but sadly, the Java platform seems to be missing the boat. If anyone feels like making a potential game-saving play by forking the compiler, here is a very good place to look.</font></p>
<ul>
    <li>
    <div><a name="properties" id="properties"><span class="smalltitle"><strong><font size="3" color="#000000" face="Georgia">Properties</font></strong></span></a></div>
    </li>
</ul>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">We'll probably also see some syntax sugar for property access. One proposal is to use <code>-&gt;</code> as a shorthand for calling <code>get<em>Foo</em></code> and <code>set<em>Foo</em></code>. For example, instead of writing:</font></p>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word">
<table cellspacing="0" border="0" width="100%" cellpadding="0">
    <tbody>
        <tr>
            <td class="code-outline">
            <pre class="displaycode"><font color="#990000">Point p = new Point();
p.setX(56);
p.setY(87);
int z = p.getX();</font>
</pre>
            </td>
        </tr>
    </tbody>
</table>
</div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><br />
</div>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">you could write&quot;</font></p>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word">
<table cellspacing="0" border="0" width="100%" cellpadding="0">
    <tbody>
        <tr>
            <td class="code-outline">
            <pre class="displaycode"><font color="#990000">Point p = new Point();
p-&gt;X = 56;
p-&gt;Y = 87;
int z = p-&gt;X;</font>
</pre>
            </td>
        </tr>
    </tbody>
</table>
</div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><br />
</div>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">Other symbols including <code>.</code> and <code>#</code> have also been proposed in lieu of <code>-&gt;</code>.</font></p>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">In the future, you may or may not have to explicitly identify the relevant field as a property in the <code>Point</code> class, like so:</font></p>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word">
<table cellspacing="0" border="0" width="100%" cellpadding="0">
    <tbody>
        <tr>
            <td class="code-outline">
            <pre class="displaycode"><font color="#990000">public class Point {

    public int property x;
    public int property y;

}</font></pre>
            </td>
        </tr>
    </tbody>
</table>
</div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word">是的，只要类当中定义的属性对于外部的对象是可见的话，就完全不必再书写getter和setter方法来获取它们了！这样一来，势必可以大量减少书写getter，setter方法在代码中说占据的篇幅。对于经常编写pojo的同志来说，这个应该是个便利的特性。</div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><br />
</div>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">Personally, I'm underwhelmed. I'd like to see the Java platform adopt a more Eiffel-like approach in which we could actually use public fields. However, if getters or setters are defined with the same names as the fields, then reads and writes to the fields are automatically dispatched to the methods instead. It uses less syntax and it's more flexible.</font></p>
<ul>
    <li>
    <div><a name="N10113" id="N10113"><span class="smalltitle"><strong><font size="3" color="#000000" face="Georgia">Arbitrary precision arithmetic</font></strong></span></a></div>
    </li>
</ul>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">Another proposal to replace methods with operators aims at <code>BigDecimal</code> and <code>BigInteger</code>. For example, currently you have to code unlimited precision arithmetic like so:</font></p>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word">
<table cellspacing="0" border="0" width="50%" cellpadding="0">
    <tbody>
        <tr>
            <td class="code-outline">
            <pre class="displaycode"><font color="#990000">BigInteger low  = BigInteger.ONE;
BigInteger high = BigInteger.ONE;
for (int i = 0; i &lt; 500; i++) {
    System.out.print(low);
    BigInteger temp = high;
    high = high.add(low);
    low = temp;
};</font></pre>
            </td>
        </tr>
    </tbody>
</table>
</div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"></div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"></div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">This could more clearly be written as:</font> </div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word">&nbsp;</div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"></div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"></div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word">
<table cellspacing="0" border="0" width="337" cellpadding="0" style="WIDTH: 337px; HEIGHT: 143px">
    <tbody>
        <tr>
            <td class="code-outline">
            <pre class="displaycode"><font color="#990000">BigInteger low  = 1;
BigInteger high = 1;
for (int i = 0; i &lt; 500; i++) {
    System.out.print(low);
    BigInteger temp = high;
    high = high + low;
    low = temp;
};</font></pre>
            </td>
        </tr>
    </tbody>
</table>
</div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000000" face="Georgia">我想这个可以算是Java 5加入autoboxing以后的又一次在代码便利性上面的进展吧！这样的写法让代码的易读性变得更高，相信也是受到了Ruby等新势力的影响所造成的吧。</font></div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font face="Georgia"></font>&nbsp;</div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia"></font></div>
<div onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">The proposal seems inoffensive enough, though it could possibly lead to overuse of these classes and consequent performance degradation in naive code.</font> </div>
<ul>
    <li>
    <div><a name="jam" id="jam"><span class="smalltitle"><strong><font size="3" color="#000000" face="Georgia">Taking the JAM out of the JAR</font></strong></span></a></div>
    </li>
</ul>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">Java 7 could fix the most long-standing source of irritation to Java developers: the various class loaders and associated classpaths. Sun is taking another whack at this problem with the Java Module System. Instead of a .jar file, data will be stored in a .jam file. This is a sort of &quot;superjar&quot; that contains all the code and metadata. Most importantly, the Java Module System will support versioning for the first time, so you can say that a program needs Xerces 2.7.1 but not 2.6. It will also allow you to specify dependencies; for instance, to say that the program in the JAM requires JDOM. It should also enable you to load one module without loading them all. Finally, it will support a centralized repository that can provide many different versions of many different JAMs, from which applications can pick the ones they need. If the JMS works, jre/lib/ext will be a thing of the past.&nbsp; </font></p>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia"><font color="#000000">(Jam 也有果酱的意思，不知道这个甚至可以支持版本化的&quot;superjar&quot;能不能得到大家的认同。在我看来，它确实有够前卫的啊！)</font></font></p>
<ul>
    <li>
    <div><a name="packages" id="packages"><span class="smalltitle"><strong><font size="3" color="#000000" face="Georgia">Package access</font></strong></span></a></div>
    </li>
</ul>
<p><font color="#000066" face="Georgia">I'm also hopeful that Java 7 will relax access restriction just a bit. It may become possible for subpackages to see the package-protected fields and methods of classes in their superpackages. Alternately, it may be possible for subpackages to see the package-protected members of superpackages that explicitly declare their friendliness. Either way, this would make dividing an application into multiple packages much simpler and dramatically improve testability. As long as unit tests were in a subpackage, you wouldn't have to make methods public to test them.</font></p>
<p><font face="Georgia">(包的作用将会在Java 7中会有一些变化/改进？这样一来，对象在方法和属性在声明的时候兴许能够变得灵活一些&hellip;&hellip;)</font></p>
<ul>
    <li>
    <div><a name="filesystem" id="filesystem"><span class="smalltitle"><strong><font size="3" color="#000000" face="Georgia">Filesystem access</font></strong></span></a></div>
    </li>
</ul>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">Filesystem access has been a major problem for the Java platform since 1995. More than 10 years later, there's still no reliable cross-platform way to perform basic operations like copying or moving files. Fixing this has been an open issue for at least the past three JDKs (1.4, 5, and 6). Sadly, boring but necessary APIs for moving and copying files have been shunted aside in favor of less common but sexier operations like memory-mapped I/O. Possibly JSR 203 will finally fix this and give us a plausible, cross-platform file system API. Then again, the working group may once again spend so much time on the relatively unimportant problem of true asynchronous I/O that the filesystem gets left at the altar once again. We should know by this time next year.</font></p>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000000" face="Georgia">(对文件系统的操作看来这次也是一个比较关注的事宜&mdash;&mdash;如果真的能够做到在跨平台之后无需改变负责I/O部分的代码的话，我想无论是对于Java EE 还是Java桌面应用乃至Java ME都是利好的消息。)</font></p>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><a name="Experimentation" id="Experimentation"><span class="smalltitle"><strong><font size="3" color="#000000" face="Georgia">Experimentation</font></strong></span></a></p>
<p onselectstart="return false;" style="OVERFLOW: hidden; WORD-BREAK: break-all; WORD-WRAP: break-word"><font color="#000066" face="Georgia">Whatever changes are made, it would be nice if they could be implemented in open source forks first, so we can see just how much or how little difference they really make. Toward this end, Sun's Peter Ah&egrave; has started the Kitchen Sink Project on java.net. The goal is to branch and fork the javac compiler repeatedly to test many different ideas like these. Blogging about pet features is one thing; actually producing running code is something else entirely.</font></p>
          <br/>
          <span style="color:red;">
            <a href="http://allen.javaeye.com/blog/53215#comments" style="color:red;">本文的讨论也很精彩，浏览讨论>></a>
          </span>
          <br/><br/><br/>
          <span style="color:#E28822;">JavaEye推荐</span>
          <br/>
          <ul class='adverts'><li><a href='/adverts/41' target='_blank'><span style="color:red;font-weight:bold;">北京: 千橡集团暨校内网诚聘软件研发工程师</span></a></li><li><a href='/adverts/42' target='_blank'><span style="color:red;font-weight:bold;">搜狐网站诚聘Java、PHP和C++工程师</span></a></li></ul>
          <br/><br/><br/>
          ]]>
        </description>
        <pubDate>Thu, 08 Feb 2007 15:12:16 +0800</pubDate>
        <link>http://allen.javaeye.com/blog/53215</link>
        <guid>http://allen.javaeye.com/blog/53215</guid>
      </item>
      <item>
        <title>[科学故事] 2006美国国家地理十大新闻故事</title>
        <author>Allen</author>
        <description>
          <![CDATA[
          <br/>
          作者: <a href="http://allen.javaeye.com">Allen</a>&nbsp;
          链接：<a href="http://allen.javaeye.com/blog/38957" style="color:red;">http://allen.javaeye.com/blog/38957</a>&nbsp;
          发表时间: 2006年12月14日
          <br/><br/>
          声明：本文系JavaEye网站发布的原创博客文章，未经作者书面许可，严禁任何网站转载本文，否则必将追究法律责任！
          <br/><br/>
          <p>来源：<font color="#ff00ff" face="Arial"><a href="http://tech.163.com/06/1214/08/329R7I3C00091537.html">http://tech.163.com/06/1214/08/329R7I3C00091537.html</a></font></p>
<p><font color="#008080">作者：美国国家地理杂志&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </font><font color="#008080">翻译编辑：网易探索 编译/卡迈拉</font></p>
<p align="center"><strong><font size="4" color="#993366">美国国家地理评选出的2006年度最具吸引力的十大新闻故事</font></strong></p>
<p style="TEXT-INDENT: 2em"><strong style="mso-bidi-font-weight: normal">1． </strong><strong style="mso-bidi-font-weight: normal">《犹大福音》揭秘：犹大不是叛徒，是英雄</strong></p>
<p align="center" style="TEXT-INDENT: 2em"><strong style="mso-bidi-font-weight: normal"><o:p></o:p></strong>新发现的《犹大福音》的残页</p>
<center><img src="http://cimg2.163.com/tech/2006/12/14/200612140827348493c.jpg" border="0" alt="" /></center><center></center>
<p style="TEXT-INDENT: 2em">一本失踪了近1700年的《犹大福音》对于犹大和耶稣之间的关系提出了一种截然不同的观点，它不同于《马太福音》、《马可福音》、《约翰福音》等将犹大描绘成叛徒，新发现的福音认为犹大是应耶稣的要求才把他出卖的，并非是他本人的意愿。</p>
<p style="TEXT-INDENT: 2em">&nbsp;</p>
<p style="TEXT-INDENT: 2em"><strong style="mso-bidi-font-weight: normal">2． </strong><strong style="mso-bidi-font-weight: normal">土耳其惊现用四肢走路的&ldquo;爬行家族&rdquo;，为人类的进化提供宝贵线索。</strong></p>
<p style="TEXT-INDENT: 2em">&nbsp;</p>
<center><center><img src="http://cimg2.163.com/tech/2006/12/14/20061214091548db040.jpg" border="0" alt="" /></center></center><center>这户家庭里的三位姐妹和两位兄弟都是在地上爬行前进<o:p></o:p></center>
<p style="TEXT-INDENT: 2em">今年3月土耳其的科学家在当地的一处偏远地区发现了一户&ldquo;爬行家族&rdquo;，该家族里的三位姐妹和两位兄弟都是靠手脚在地面上爬行前进，而且说类似大猩猩叫声的原始语言。他们的父母已经60多岁，属于近亲结婚，生有19名子女，除了他们5个之外，其他兄弟姐妹都和正常人一样用双脚走路。科学家研究后发现他们存在严重的基因缺陷，所以无法直立行走，平时只能用四肢爬行走路，言行能力倒退100多万年。科学家称有关发现可能为人类在超过300万年前如何进化至用两脚步行提供珍贵的资料。</p>
<p style="TEXT-INDENT: 2em">&nbsp;</p>
<p style="TEXT-INDENT: 2em"><strong style="mso-bidi-font-weight: normal">3</strong><strong style="mso-bidi-font-weight: normal">．</strong><strong style="mso-bidi-font-weight: normal"> </strong><strong style="mso-bidi-font-weight: normal">&ldquo;鳄鱼猎人&rdquo;史蒂夫&middot;欧文被魟鱼背棘刺中胸部中毒身亡</strong></p>
<p align="center" style="TEXT-INDENT: 2em"><strong style="mso-bidi-font-weight: normal"><o:p></o:p></strong>&ldquo;鳄鱼猎人&rdquo;史蒂夫&middot;欧文</p>
<center><img src="http://cimg2.163.com/tech/2006/12/14/20061214082957667d4.jpg" border="0" alt="" /></center><center></center>
<p style="TEXT-INDENT: 2em">著名的动物保护主义者，电视明星&ldquo;鳄鱼猎人&rdquo;史蒂夫-欧文( Steve Irwin ) 在今年9月4日在澳东北部海域录制一部水下纪录片时被一条魟鱼的背棘刺中胸部，中毒身亡，年仅44岁。<o:p></o:p></p>
<p style="TEXT-INDENT: 2em">欧文1962年2月22日生于澳大利亚墨尔本，幼年随父母移居澳大利亚昆士兰州。他自小热爱野生动物，9岁时曾徒手捕到一条鳄鱼。1991年，他接管父亲留下的爬行动物园并将其更名为&ldquo;澳大利亚动物园&rdquo;。<o:p></o:p></p>
<p style="TEXT-INDENT: 2em">1992年，欧文录制了他的第一部纪录片《鳄鱼猎人日记》，并通过《探索》有线电视频道在全球播出，欧文因此一举成名。他生前录制的《鳄鱼猎人日记》节目全球观众总数达2亿人。</p>
<p style="TEXT-INDENT: 2em">&nbsp;</p>
<p style="TEXT-INDENT: 2em"><strong style="mso-bidi-font-weight: normal">4． </strong><strong style="mso-bidi-font-weight: normal">失踪</strong><strong style="mso-bidi-font-weight: normal">1700</strong><strong style="mso-bidi-font-weight: normal">多年《犹大福音》的传奇之旅</strong></p>
<center><img src="http://cimg2.163.com/tech/2006/12/14/200612140844049cd29.jpg" border="0" alt="" /></center>
<p style="TEXT-INDENT: 2em">失踪1700多年的《犹大福音》手稿它本身的故事与它里面所描述犹大和耶稣之间的故事一样具有传奇色彩。<o:p></o:p></p>
<p style="TEXT-INDENT: 2em">在这本手抄本里，故事中描绘了犹大不是我们先前所认为的叛徒，而是英雄，他是应耶稣要求才出卖了他。它被埋藏了数个世纪，在20世纪70年代后期人们在埃及发现了它，当时只是一堆残缺破损的草纸，它用古代埃及所使用的哥普特文字抄写，大约抄于公元3世纪到4世纪之间，从内容上看大约写于公元180年左右。在1980年，一次抢劫案中被人偷走被带出了埃及，后来在瑞士人们又找到了它，学者们想把它买下来做细致的研究，但当时手稿主人要价300万美元，但没人买的起，于是这份手稿在纽约州长岛花旗银行的保险箱躺了近二十年，直到前几年，才由瑞士的梅塞纳－马恩省斯古代艺术基金会取得，才最终被修复、重组、翻译后公布于众。最后，所有的书稿又被带回到了埃及，被存放在了柯普特博物馆里。</p>
<p style="TEXT-INDENT: 2em">&nbsp;</p>
<p style="TEXT-INDENT: 2em"><strong style="mso-bidi-font-weight: normal">5</strong><strong style="mso-bidi-font-weight: normal">．印尼发现&ldquo;失落的世界&rdquo;，雨林中发现上百新奇物种</strong><strong style="mso-bidi-font-weight: normal"><o:p></o:p></strong></p>
<p style="TEXT-INDENT: 2em">&nbsp;</p>
<center><img src="http://cimg2.163.com/tech/2006/12/14/2006121408313306269.jpg" border="0" alt="" /></center>
<p align="center" style="TEXT-INDENT: 2em">罕见的金披凤树袋鼠在那里被发现，它被认为是世界上最漂亮的袋鼠,同时也是栖息在丛林地区的最为珍贵的有袋动物。</p>
<p style="TEXT-INDENT: 2em">&nbsp;</p>
<p style="TEXT-INDENT: 2em">&nbsp;</p>
<center><img src="http://cimg2.163.com/tech/2006/12/14/20061214083218862b8.jpg" border="0" alt="" /></center>
<p style="TEXT-INDENT: 2em"><o:p></o:p></p>
<p style="TEXT-INDENT: 2em"><o:p></o:p></p>
<p align="center" style="TEXT-INDENT: 2em">这是一种叫做密雀的鸟类，人们上一次见到这种稀有鸟类是在1939年。</p>
<p align="center" style="TEXT-INDENT: 2em">&nbsp;</p>
<p style="TEXT-INDENT: 2em">&nbsp;</p>
<center><img src="http://cimg2.163.com/tech/2006/12/14/2006121408325958ac7.jpg" border="0" alt="" /></center>
<p style="TEXT-INDENT: 2em"><o:p></o:p></p>
<p style="TEXT-INDENT: 2em"><o:p></o:p></p>
<p align="center" style="TEXT-INDENT: 2em">科学家首次拍到了这种被他们叫做新几内亚&ldquo;天堂迷失&rdquo;鸟的图片。鸟类学家Berlepsch将它命名为&ldquo;六线天堂鸟&rdquo;，因其头部长有六根精美的羽毛。人们只在一个世纪前看到过一次这种鸟。</p>
<p style="TEXT-INDENT: 2em">&nbsp;</p>
<p style="TEXT-INDENT: 2em">&nbsp;</p>
<center><img src="http://cimg2.163.com/tech/2006/12/14/2006121408342143af1.jpg" border="0" alt="" /></center>
<p style="TEXT-INDENT: 2em"><o:p></o:p></p>
<p style="TEXT-INDENT: 2em"><o:p></o:p></p>
<p align="center" style="TEXT-INDENT: 2em">这只个头较小的蛙是科学家在岛上发现的20个蛙类新物种里的一种，大约只有14毫米长。</p>
<p style="TEXT-INDENT: 2em"><o:p></o:p></p>
<p style="TEXT-INDENT: 2em">在南太平洋的岛屿丛林深处，探险家们发现了一座世外桃源，那里生活着许多不知名的袋鼠、鸟类、昆虫以及其他动物等等。<o:p></o:p></p>
<p style="TEXT-INDENT: 2em">在新几内亚南太平洋的一座孤岛上，一个科学家小组在那里进行了15天的探险活动，发现了许多未曾见过的或者先前认为已经灭绝的物种。</p>
<p style="TEXT-INDENT: 2em">&nbsp;</p>
<p style="TEXT-INDENT: 2em"><strong style="mso-bidi-font-weight: normal">6． </strong><strong style="mso-bidi-font-weight: normal">诺亚方舟在伊朗被发现？</strong></p>
<o:p><center><strong><img src="http://cimg2.163.com/tech/2006/12/14/200612140836538fe3c.jpg" border="0" alt="" /></strong></center><center></center>
<p style="TEXT-INDENT: 2em">今年7月，科学家在伊朗的厄尔布尔士山脉中发现了一块船形的巨型岩石，一些基督教考古学家们猜测它可能是传说中的诺亚方舟的遗骸。许多人对此都表示怀疑。一些圣经学者认为诺亚方舟应该在土耳其东部的阿拉拉特山脉附近，他们认为诺亚是在6000年前到10000年前建造了诺亚方舟。</p>
<p style="TEXT-INDENT: 2em"><strong>&nbsp;</strong></p>
<p style="TEXT-INDENT: 2em"><strong>7． 巨型兔子入侵英国村庄</strong></p>
<o:p><center><strong><img src="http://cimg2.163.com/tech/2006/12/14/200612140837501c87d.jpg" border="0" alt="" /><br />
</strong></center>
<p style="TEXT-INDENT: 2em"><strong>&nbsp;</strong></p>
<p style="TEXT-INDENT: 2em"><o:p></o:p></p>
<p style="TEXT-INDENT: 2em">德国埃伯斯瓦尔德市，一名兔子饲养员手提一只雄兔。专家认为那只村名发现的巨兔，可能就是饲养的兔子逃出去后野化的结果。<o:p></o:p></p>
<p style="TEXT-INDENT: 2em">今年四月，英国某村庄发生了一件怪事，一只和狗一般大小的兔子突然闯入村子里的菜园，偷吃那里的蔬菜。这只兔子白天藏身洞穴，晚上就出来偷吃那里农作物，而且胃口特别大，神出鬼没，弄的整个村子鸡犬不宁，而且只有几位村名见过它，他们说这只兔子身形比一般兔子大的多，毛色呈黑色和棕色。气愤的村民布下了各种陷阱捕杀它，当地政府还把这件事列入了要务。</p>
<p style="TEXT-INDENT: 2em"><strong>&nbsp;</strong></p>
<p style="TEXT-INDENT: 2em"><strong>8．2000年前爱尔兰古尸赶时髦用发胶、修指甲</strong></p>
<o:p><center><strong><img src="http://cimg2.163.com/tech/2006/12/14/20061214083841e5f80.jpg" border="0" alt="" /></strong></center><center></center><o:p><center><strong><img src="http://cimg2.163.com/tech/2006/12/14/2006121408394195b55.jpg" border="0" alt="" /></strong></center><center></center>
<p style="TEXT-INDENT: 2em">今年1月，考古学家发现，在爱尔兰沼泽地发现的两具铁器时代的古尸，其中一具古尸的头发用了发胶，可能是为了使自己看起来更高更优雅，他的身高只有1.57米。另外一具则修剪了指甲，站起来有1.98米高。他们大约生活在公元前392年到201年之间，使用的发胶由松树的树脂和蔬菜汁混合而成。两具古尸年龄大约在20多岁，可能是被谋杀。科学家猜测他们很可能是2300多年前的爱尔兰贵族。</p>
<p style="TEXT-INDENT: 2em"><strong>&nbsp;</strong></p>
<p style="TEXT-INDENT: 2em"><strong>9． 冥王星被赶出9大行星行列</strong></p>
<o:p><center><strong><img src="http://cimg2.163.com/tech/2006/12/14/20061214084031063f7.jpg" border="0" alt="" /></strong></center><center></center>
<p style="TEXT-INDENT: 2em">今年8月，国际天文学联合会大会上冥王星被开除出了9大行星的行列，而被归入了&ldquo;矮行星&rdquo;。冥王星直径只有2300公里，比月球还要小，它所处的轨道在海王星之外，属于太阳系外围的柯伊伯带，这个区域一直是太阳系小行星和彗星诞生的地方。冥王星的出局也在国际上引发了很大争论。<o:p></o:p></p>
<p style="TEXT-INDENT: 2em">太阳系新家谱：<o:p></o:p></p>
<p style="TEXT-INDENT: 2em">一、行星：成员包括水星、金星、地球等8颗行星。定义：围绕太阳运转，自身引力足以克服其刚体力而使天体呈圆球状，并且能够清除其轨道附近其他物体的天体。<o:p></o:p></p>
<p style="TEXT-INDENT: 2em">二、矮行星：成员包括冥王星和谷神星等。定义：与行星同样具有足够的质量，呈圆球状，但不能清除其轨道附近其他物体的天体。<o:p></o:p></p>
<p style="TEXT-INDENT: 2em">三、太阳系小天体。定义：围绕太阳运转但不符合行星和矮行星条件的物体。</p>
<p style="TEXT-INDENT: 2em"><strong>&nbsp;</strong></p>
<p style="TEXT-INDENT: 2em"><strong>10．为穆斯林妇女特制的可遮盖全身的运动衣</strong></p>
<o:p><center><strong><img src="http://cimg2.163.com/tech/2006/12/14/2006121408412402c60.jpg" border="0" alt="" /><br />
</strong></center>
<p style="TEXT-INDENT: 2em"><strong>&nbsp;</strong></p>
<p style="TEXT-INDENT: 2em"><o:p></o:p></p>
<p style="TEXT-INDENT: 2em">一名穆斯林妇女穿着特制的可以遮盖全身的泳衣，使她不会违背《可兰经》上的守则。<o:p></o:p></p>
<p style="TEXT-INDENT: 2em">在穆斯林的守则里，女子的穿着必须遮盖住全身，只可露出面孔、手、脚。多年来穆斯林女性一直在为寻找一件合适的运动衣而努力。现在，澳大利亚的一家名为Ahiida的公司采用一种很轻的织物设计出了一种可以覆盖全身的衣服，取名为Hijood，该公司还专门为穆斯林女性设计了一种可以遮盖全身的泳衣。同时，这些特制的运动衣也受到了那些不喜欢展示自己身体皮肤的人的欢迎。 </p>
</o:p></o:p>冥王星和其最大的卫星的艺术图<o:p></o:p></o:p>这具生活在铁器时代的古尸还修了指甲<o:p></o:p></o:p>用发胶的爱尔兰古尸头部图像</o:p></o:p>考古学家在伊朗厄尔布尔士山脉中发现的怀疑是诺亚方舟遗骸的岩石<strong style="mso-bidi-font-weight: normal"><o:p></o:p></strong>
          <br/>
          <span style="color:red;">
            <a href="http://allen.javaeye.com/blog/38957#comments" style="color:red;">本文的讨论也很精彩，浏览讨论>></a>
          </span>
          <br/><br/><br/>
          <span style="color:#E28822;">JavaEye推荐</span>
          <br/>
          <ul class='adverts'><li><a href='/adverts/41' target='_blank'><span style="color:red;font-weight:bold;">北京: 千橡集团暨校内网诚聘软件研发工程师</span></a></li><li><a href='/adverts/42' target='_blank'><span style="color:red;font-weight:bold;">搜狐网站诚聘Java、PHP和C++工程师</span></a></li></ul>
          <br/><br/><br/>
          ]]>
        </description>
        <pubDate>Thu, 14 Dec 2006 09:21:23 +0800</pubDate>
        <link>http://allen.javaeye.com/blog/38957</link>
        <guid>http://allen.javaeye.com/blog/38957</guid>
      </item>
  </channel>
</rss>