当前位置:首页 » 编程博文
开发技术指南» 文章正文
    引言: Preface IN: 17pt 0cm
 

 

    摘要:在web应用当中!我们往往会用到很多textbox来处理录入的信息。 在页面提交之前,在textbox失去焦点的时候,可能就是要处理一下我们输入的信息。 比如: 1、对输入信息的校验 2、根据输入的信息对后面即将录入的信息的不同处理 3、需要回到服务端处理 等等... 基于这些要求啊!给textbox加上onblur 的服务端事件就可以了!如图: 服务端就会自动生成根onclick一样事件 thi......
 ·公农历转换vb类    »显示摘要«
    摘要:网上流传很多计算公农历的源代码,很多,但是居然没有vb的,晕, 所以。。。。。 用法: 以l开始的方法均为阴历,以s开始的方法均为公历 基本的两个初使函数: linitdate:用农历年月日初使化日期对象 sinitdate: 用公历年月日初使化日期对象 其它的方法看下面的一小段代码吧 示例代码 private sub command1_click() dim t as clsdate dim y......


TAOUP初译稿:提交版本
preface

unix is not so much an operating system as an oral history. 【程序编程相关:C++从零开始(十一)下篇——类的相关知

前言 【推荐阅读:如何不使用可视化设计来显示登陆窗体?

<author>nealstephenson</author> 【扩展信息:什么是Python?

--

unix,与其说是操作系统,不如说是口述历史.

--

<author>nealstephenson</author>

there is a vast difference between knowledge and expertise. knowledge lets you deduce the right thing to do; expertise makes the right thing a reflex, hardly requiring conscious thought at all.

知识与专家经验有很大的区别.根据知识,可以推断出该做的正确的事;从专家经验出发,可以反射般地得到正确的事,几乎不需要有意识的思考.

this book has a lot of knowledge in it, but it is mainly about expertise. it is going to try to teach you the things about unix development that unix experts know, but aren’t aware that they know. it is therefore less about technicalia and more about shared culture than most unix books — both explicit and implicit culture, both conscious and unconscious traditions. it is not a ‘how-to’ book, it is a ‘why-to’ book.

本书中有许多知识,但主要还是关于专家经验的.本书试图教会你与unix开发相关的事情——unix专家知道他们,但却没有意识到他们已经知道.从而,与大多数unix书籍不同,本书涉及的技术细节较少,谈得比较多的是共同的文化——外在或内在的文化.自觉或不自觉的传统.这不是一本讲“怎样做”的书,而是讲“为什么”的书.

the why-to has great practical importance, because far too much software is poorly designed. much of it suffers from bloat, is exceedingly hard to maintain, and is too difficult to port to new platforms or extend in ways the original programmers didn’t anticipate. these problems are symptoms of bad design. we hope that readers of this book will learn something of what unix has to teach about good design.

“为什么”在实践中非常重要,这是因为太多的软件都设计得很糟糕.大多数软件体积臃肿,其维护极为艰巨;要把他们移植到新平台.或者以原先开发人员没有预见到的方式进行扩展,更是举步维艰.我们希望本书的读者学到一些关于良好设计的东西,这正是unix可以教会我们的.

 

this book is divided into four parts: context, design, tools, and community. the first part(context) is philosophy and history, to help provide foundation and motivation for what follows. the second part (design) unfolds the principles of the unix philosophy into more specific advice about design and implementation. the third part (tools) focuses on the software unix provides for helping you solve problems. the fourth part (community) is about the human-to-human transactions and agreements that make the unix culture so effective at what it does.

本书分为四部分:背景.设计.工具与社区.第一部分(背景)是哲学与历史,描述了后续部分的基础与动机.第二部分(设计)揭示了unix哲学的原理,阐述了关于设计与实现的更为明确的建议.第三部分(工具)关注unix提供的.有助于你解决问题的各种软件.第四部分(社区)讲述人与人之间的沟通与协作,这种沟通与协作使得unix文化在其所作所为上给人印象深刻.

because this is a book about shared culture, i never planned to write it alone. you will notice that the text includes guest appearances by prominent unix developers, the shapers of the unix tradition. the book went through an extended public review process during which i invited these luminaries to comment on and argue with the text. rather than submerging the results of that review process in the final version, these guests were encouraged to speak with their own voices, amplifying and developing and even disagreeing with the main line of the text.

因为这是一本关于共同文化的书,我从未打算独自写完它.你会注意到书中包括了客串表演,客串嘉宾是杰出的unix开发人员,他们是unix传统的塑造者.本书经过长期而公开的评审,评审期间,我邀请这些学识渊博的人来评价与讨论书中的文字.不过,最终版本中,评审过程的成果并没有被湮没;客串嘉宾们受到鼓励,鼓励他们表达自己的观点——补充.展开其观点,甚至是用与正文主线有分歧的方式来表达他们的观点.

in this book, when i use the editorial ‘we’ it is not to pretend omniscience but to reflect the fact that it attempts to articulate the expertise of an entire community.

书中,当我使用社论般的“我们”的时候,并不是要装做无所不知,这只不过是反映了一个事实:本书试图清晰地表达社区整体的专家经验.

because this book is aimed at transmitting culture, it includes much more in the way of history and folklore and asides than is normal for a technical book. enjoy; these things, too, are part of your education as a unix programmer. no single one of the historical details is vital, but the gestalt of them all is important. we think it makes a more interesting story this way. more importantly, understanding where unix came from and how it got the way it is will help you develop an intuitive feel for the unix style.

因为本书旨在传播文化,与技术书籍相比,书中有更多的历史.传说与旁白.欣赏吧;这些内容,也是你作为unix程序员应该受到的教育的一部分.任何单独的历史事件都不重要,但他们的“格”(gestalt, 结构或形态,其构成因素并不是各组成部分间的简单相加,而是一种完整的结构或形式——译者注)却是重要的.我们认为,这样处理会使故事有趣许多.更重要的是,理解unix来自何处.又怎么走上了现在的道路,将有助于你培养对unix风格的直觉.

for the same reason, we refuse to write as if history is over. you will find an unusually large number of references to the time of writing in this book. we do not wish to pretend that current practice reflects some sort of timeless and perfectly logical outcome of preordained destiny. references to time of writing are meant as an alert to the reader two or three or five years hence that the associated statements of fact may have become dated and should be double-checked.

基于同样的原因,我们拒绝这样的写法,即,似乎历史已经完结.你将发现数量多得异乎寻常的参考文献,在本书写作的时候这些参考文献都是最新的.
...   下一页
 ·c学习笔记一    »显示摘要«
    摘要:1.函数体中的变量定义语句,必须在所有可执行语句之前。 main() { int x,y; /*变量定义语句:定义2个整型变量x、y*/ x=3; /*可执行的赋值语句:将3赋值给变量x*/ y=6; /*可执行的赋值语句:将6赋值给变量y*/ int max; /*变量定义语句:出现在可执行的 赋值语句“x=3;”和“ y=6;”之后,非法!*/ max=x>y?x:y; printf(“......
» 本期热门文章:

©2000-2007 All Rights Reserved. 最佳浏览:1024X768 MSIE