- 경시대회준비반/BigInteger . . . . 86 matches
* provided that the above copyright notice appear in all copies and
* representations about the suitability of this software for any
enum BigMathERROR { BigMathMEM = 1 , BigMathOVERFLOW , BigMathUNDERFLOW, BigMathINVALIDINTEGER, BigMathDIVIDEBYZERO,BigMathDomain};
void Dump(const char *,enum BigMathERROR);
string& DumpString (char const*,enum BigMathERROR);
// The Size Type
// The Data Type
// The Base Used
// The integer array to hold the number
DATATYPE *TheNumber;
// Start of the location of the number in the array
// End of the location of the number in the array
// True if the number is negative
// deallocates the array
// the array with the `fill' value
// The Destructor
// Returns Number of digits in the BigInteger
// Determines if the number representation is OK or not
// True is the nubmer is zero
// Returns the BigInteger absolute
- WikiTextFormattingTestPage . . . . 33 matches
This page originated on Wiki:WardsWiki, and the most up-to-date copy resides there. This page has been copied here in order to make a quick visual determination of which TextFormattingRules work for this wiki. Currently it primarily determines how text formatted using the original Wiki:WardsWiki text formatting rules is displayed. See http://www.c2.com/cgi/wiki?WikiOriginalTextFormattingRules.
If you want to see how this text appears in the original Wiki:WardsWiki, see http://www.c2.com/cgi/wiki?WikiEngineReviewTextFormattingTest
People reviewing this wiki from the original Wiki:WardsWiki will be referred to this page. If you want to see the review, go to http://www.c2.com/cgi/wiki?WikiEngineReview.
Other places this page appears (perhaps as an older version):
This page contains sample marked up text to make a quick visual determination as to which Wiki:TextFormattingRules work for a given wiki. To use the page, copy the text from the edit window, and paste it in the wiki under test. Then read it.
And, the next logical thing to do is put a page like this on a public wiki running each Wiki:WikiEngine, and link to it from the appropriate Wiki:WikiReview page, as has been done in some cases -- see above.
The next line (4 dashes) should show up as a horizontal rule. In a few wikis, the width of the rule is controlled by the number of dashes. That will be tested in a later section of this test page.
This first section will test the Wiki:WikiOriginalTextFormattingRules.
If a wiki properly interprets the Wiki:WikiOriginalTextFormattingRules, the text will appear as described here.
The original Wiki:WardsWiki text formatting rules make no provision for headings. They can be simulated by applying emphasis. See the next several lines.
The next phrase, even though enclosed in triple quotes, '''will not display in bold because
I've broken the phrase across a line''' boundary by inserting a <return>.
If I don't break the phrase by inserting a <return>, '''the bold portion can start and end on different lines,''' as this does.
Note that the logic seems to be easily confused. In the next paragraph I combine the two sentences (with no other changes). Notice the results. (The portion between the "innermost" set of triple quotes, and nothing else, is bold.)
The next phrase, even though enclosed in triple quotes, '''will not display in bold because
I've broken the phrase across a line''' boundary by inserting a <return>. If I don't break the phrase by inserting a <return>, '''the bold portion can start and end on different lines,''' as this does.
I don't know if Wiki:WardCunningham considers this the desired behavior.
* Tenth level, preceded by <tab><tab><tab><tab><tab><tab><tab><tab><tab><tab>*<space>, appears indented 40 spaces with a solid square bullet. It is left to the reader to determine whether there is a limit to this progression.
This is another bulleted list, formatted the same way but with shortened lines to display the behavior when nested and when separated by blank lines.
* Top level -- these headings should appear with a blank line between them
- EnglishSpeaking/2011년스터디 . . . . 23 matches
1. The Simpsons (심슨네 가족들)의 한 장면을 역할 분담해서 따라하기.
* [EnglishSpeaking/TheSimpsons]
1. Theme Talking
* There are four members in my family: my father, mother, and a younger brother. Well, actually there are five including our dog. My father was a military officer for twenty years. He recently retired from service and now works in a weaponry company. My mother is a typical housewife. She takes care of me and my brother and keeps our house running well. My brother is attending a university in the U.S.A. He just entered the university as a freshman and is adjusting to the environment. I miss the memory of fighting over things with him. The last member of my family is my dog named Joy. She is a Maltese terrier and my mother named her Joy to bring joy into our family. That's about it for the introduction of my family members.
1. The Simpsons
* [EnglishSpeaking/TheSimpsons/S01E01]
1. Theme Talking
* [김수경] - 오늘 처음으로 심슨 대사를 따라해봤습니다. 지원언니께서 네명이 같이 연습할만한 장면들을 미리 골라두셨는데 막상 오늘 온 사람이 두명이라 다른 장면을 연습했습니다. 40초도 채 안 되는 짧은 대화인데 참 어렵더라구요. 한 문장씩 듣고 따라하고, 받아쓰기도 하고, 외워서 해보는 등 한 장면을 가지고 여러번 연습한 것은 매우 좋았습니다. ''You tell me that all the time.''이나 ''Let me be honest with you.''가 어려운 문장은 아니지만 막상 말하려면 딱 생각이 안 났을 것 같은데 오늘 이후로는 좀 더 유려하게 말할 수 있을 것 같아요. 앞으로 매주 진행하면 이런 표현들이 늘어나겠죠 ㅋㅋㅋ
* [송지원] - 혹시나 했지만 역시나 현지 영어 따라하기는 쉽지 않습니다. 짧은 몇 줄 문장을 외워서 따라하기는 어렵지만 많이 하면 실력이 늘 거라는 생각은 들어요. Free Talking은 제가 하고 싶은 말을 나름 자유롭게 구사해서 만족했는데 Theme Talking에서는 한계를 느끼고 한국어를 섞어서 그 점이 좀 아쉬웠어요. 다음 주에는 The Simpsons.. 정말 4명이 함께 하기를 (온 성의를 다해 대본을 준비하는 만큼;ㅁ;)
1. The Simpsons
* [EnglishSpeaking/TheSimpsons/S01E02]
1. Theme Talking
* [김수경] - 이번주 영상은 문장이 단어 조금 바꾸면 여기저기 가져다 쓸만한 것이 많아 재미있었어요. 가위바위보로 역할을 분담했는데 ''Along with the ego and the superego, one of three components of the psyche.''라는 문장을 외워보고 싶어서 리사를 선택했습니다. 그런데 리사 분량이 제일 적어서 본의아니게(?) 가장 날로먹었네요 ㅋㅋ
1. The Simpsons
* [EnglishSpeaking/TheSimpsons/S01E03]
1. Theme Talking
1. The Simpsons
* [EnglishSpeaking/TheSimpsons/S01E04]
1. Theme Talking
* Theme : 자신의 ''Role Model''.
- MoreEffectiveC++/Appendix . . . . 21 matches
So your appetite for information on C++ remains unsated. Fear not, there's more — much more. In the sections that follow, I put forth my recommendations for further reading on C++. It goes without saying that such recommendations are both subjective and selective, but in view of the litigious age in which we live, it's probably a good idea to say it anyway. ¤ MEC++ Rec Reading, P2
There are hundreds — possibly thousands — of books on C++, and new contenders join the fray with great frequency. I haven't seen all these books, much less read them, but my experience has been that while some books are very good, some of them, well, some of them aren't. ¤ MEC++ Rec Reading, P4
What follows is the list of books I find myself consulting when I have questions about software development in C++. Other good books are available, I'm sure, but these are the ones I use, the ones I can truly recommend. ¤ MEC++ Rec Reading, P5
A good place to begin is with the books that describe the language itself. Unless you are crucially dependent on the nuances of the °official standards documents, I suggest you do, too. ¤ MEC++ Rec Reading, P6
* '''''The Annotated C++ Reference Manual''''', Margaret A. Ellis and Bjarne Stroustrup, Addison-Wesley, 1990, ISBN 0-201-51459-1. ¤ MEC++ Rec Reading, P7
* '''''The Design and Evolution of C++''''', Bjarne Stroustrup, Addison-Wesley, 1994, ISBN 0-201-54330-3. ¤ MEC++ Rec Reading, P8
These books contain not just a description of what's in the language, they also explain the rationale behind the design decisions — something you won't find in the official standard documents. The Annotated C++ Reference Manual is now incomplete (several language features have been added since it was published — see Item 35) and is in some cases out of date, but it is still the best reference for the core parts of the language, including templates and exceptions. The Design and Evolution of C++ covers most of what's missing in The Annotated C++ Reference Manual; the only thing it lacks is a discussion of the Standard Template Library (again, see Item 35). These books are not tutorials, they're references, but you can't truly understand C++ unless you understand the material in these books
For a more general reference on the language, the standard library, and how to apply it, there is no better place to look than the book by the man responsible for C++ in the first place: ¤ MEC++ Rec Reading, P10
* '''''The C++ Programming Language (Third Edition)''''', Bjarne Stroustrup, Addison-Wesley, 1997, ISBN 0-201-88954-4. ¤ MEC++ Rec Reading, P11
Stroustrup has been intimately involved in the language's design, implementation, application, and standardization since its inception, and he probably knows more about it than anybody else does. His descriptions of language features make for dense reading, but that's primarily because they contain so much information. The chapters on the standard C++ library provide a good introduction to this crucial aspect of modern C++. ¤ MEC++ Rec Reading, P12
If you're ready to move beyond the language itself and are interested in how to apply it effectively, you might consider my other book on the subject: ¤ MEC++ Rec Reading, P13
A book pitched at roughly the same level as my Effective C++ books, but covering different topics, is ¤ MEC++ Rec Reading, P16
Murray's book is especially strong on the fundamentals of template design, a topic to which he devotes two chapters. He also includes a chapter on the important topic of migrating from C development to C++ development. Much of my discussion on reference counting (see Item 29) is based on the ideas in C++ Strategies and Tactics.
If you're the kind of person who likes to learn proper programming technique by reading code, the book for you is ¤ MEC++ Rec Reading, P19
Each chapter in this book starts with some C++ software that has been published as an example of how to do something correctly. Cargill then proceeds to dissect — nay, vivisect — each program, identifying likely trouble spots, poor design choices, brittle implementation decisions, and things that are just plain wrong. He then iteratively rewrites each example to eliminate the weaknesses, and by the time he's done, he's produced code that is more robust, more maintainable, more efficient, and more portable, and it still fulfills the original problem specification. Anybody programming in C++ would do well to heed the lessons of this book, but it is especially important for those involved in code inspections. ¤ MEC++ Rec Reading, P21
One topic Cargill does not discuss in C++ Programming Style is exceptions. He turns his critical eye to this language feature in the following article, however, which demonstrates why writing exception-safe code is more difficult than most programmers realize: ¤ MEC++ Rec Reading, P22
If you are contemplating the use of exceptions, read this article before you proceed. ¤ MEC++ Rec Reading, P24
Once you've mastered the basics of C++ and are ready to start pushing the envelope, you must familiarize yourself with ¤ MEC++ Rec Reading, P25
I generally refer to this as "the LSD book," because it's purple and it will expand your mind. Coplien covers some straightforward material, but his focus is really on showing you how to do things in C++ you're not supposed to be able to do. You want to construct objects on top of one another? He shows you how. You want to bypass strong typing? He gives you a way. You want to add data and functions to classes as your programs are running? He explains how to do it. Most of the time, you'll want to steer clear of the techniques he describes, but sometimes they provide just the solution you need for a tricky problem you're facing. Furthermore, it's illuminating just to see what kinds of things can be done with C++. This book may frighten you, it may dazzle you, but when you've read it, you'll never look at C++ the same way again. ¤ MEC++ Rec Reading, P27
If you have anything to do with the design and implementation of C++ libraries, you would be foolhardy to overlook ¤ MEC++ Rec Reading, P28
- Celfin's ACM training . . . . 18 matches
|| 1 || 1 || 110101/100 || The 3n+1 Problem || . || [3n 1/Celfin] ||
|| 3 || 1 || 110103/10137 || The Trip || . || [The Trip/Celfin] ||
|| 6 || 6 || 110606/10254 || The Priest Mathmatician || . || [http://165.194.17.5/wiki/index.php?url=zeropage&no=4132&title=ThePriestMathematician/하기웅&login=processing&id=&redirect=yes The Priest Mathmatician/Celfin] ||
|| 11 || 10 || 111007/10249 || The Grand Dinner || 1 hour || [http://165.194.17.5/wiki/index.php?url=zeropage&no=4188&title=TheGrandDinner/하기웅&login=processing&id=celfin&redirect=yes The Grand Dinner/Celfin] ||
|| 16 || 13 || 111303/10195 || The Knights of the Round Table || 1 hour || [http://165.194.17.5/wiki/index.php?url=zeropage&no=4263&title=TheKnightsOfTheRoundTable/하기웅&login=processing&id=&redirect=yes TheKnightsOfTheRoundTable/Celfin] ||
|| 17 || 13 || 111306/10215 || The Largest/Smallest Box || 40 mins || [http://165.194.17.5/wiki/index.php?url=zeropage&no=4264&title=TheLagestSmallestBox/하기웅&login=processing&id=&redirect=yes TheLargestSmallestBox/Celfin] ||
|| 20 || 1 || 110107/10196 || Check the Check || 4 hours || [CheckTheCheck/Celfin] ||
- DataCommunicationSummaryProject/Chapter8 . . . . 15 matches
= The Air Link =
=== The Home Location Register(HLR) ===
=== The Visitors' Location Register(VLR) ===
=== The Equipment Identity Register(EIR) ===
=== The Authentication Center(AuC) ===
=== The Messaging Center ===
* The Gateway Mobile Switching Center (GMSC)는 스위칭 체계의 최 상위에 있다.
== The GPRS Backbone ==
== The Gateway Node ==
* The Point-to-Multipoint Service Center(PTM SC), Qos 문제를 다루는 서버이다. 돈을 더 많이 낸 고객에게 통신에서 우선권을 준다. 그리고 소리와 그림과 같이 데이터의 종류에 따라 우선권을 달리 준다.(소리가 더 속도에 민감하다.)
* The Border Gateway(BG), roaming을 다룬다. 이것은 주로 필터링을 통해서 원하지 않는 연결을 막는 방화벽에 연결되어 있다.
* The GPRS Charging Gateway(GCG), 요금 지불 옵션을 전문적으로 하기 위해서 필요하다.
* The Lawful Interception Gateway(LIG), 당국이 GPRS 네트워크에 있는 이동 데이터를 중간에서 엿보는것을 허락한다.
= The Internet =
== The IP Address Shortage ==
- RSSAndAtomCompared . . . . 15 matches
feed formats. As of mid-2005, the two
The purpose of this page is to summarize, as clearly and simply as possible, the differences between the RSS 2.0 and Atom 1.0 syndication languages.
The RSS 2.0 specification is copyrighted by Harvard University and is frozen. No significant changes can be made and it is intended that future work be done under a different name; Atom is one example of such work.
The Atom 1.0 specification (in the course of becoming an
IETF standards track RFC) represents the consensus of the
within the [http://www.ietf.org/ IETF], as reviewed and approved by the IETF community and the
[http://www.ietf.org/iesg.html Internet Engineering Steering Group]. The specification is structured in such a way that the IETF could conceivably issue further versions or revisions of this specification without breaking existing deployments, although there is no commitment, nor currently expressed interest, in doing so.
See the Extensibility section below for how each can be extended without changing the specifications themselves.
There are two popular protocols widely used with RSS, [http://www.xmlrpc.com/metaWeblogApi MetaWeblog]
and [http://www.blogger.com/developers/api/ Blogger]. There are frequent
The Atompub working group is in the late stages of developing the
[http://ietfreport.isoc.org/idref/draft-ietf-atompub-protocol/ Atom Publishing Protocol], which is closely integrated with the Atom feed format and is based on the experience with the existing protocols.
RSS 2.0 requires feed-level title, link, and description. RSS 2.0 does not require that any of the fields of individual items in a feed be present.
RSS 2.0 may contain either plain text or escaped HTML, with no way to indicate which of the two is provided. Escaped HTML is ugly (for example, the string AT&T would be expressed as “AT&T”) and has been a source of difficulty for implementors. RSS 2.0 cannot contain actual well-formed XML markup, which reduces the re-usability of content.
* plain text, with no markup (the default)
* some other XML vocabulary (There is no guarantee that the recipient will be able to do anything useful with such content)
* a pointer to Web content not included in the feed
RSS 2.0 has a “description” element which is commonly used to contain either the full text of an entry or just a synopsis (sometimes in the same feed), and which sometimes is absent. There is no built-in way to signal whether the contents are complete.
Atom has separate “summary” and “content” elements. The summary is encouraged for accessibility reasons if the content is non-textual (e.g. audio) or non-local (i.e. identified by pointer).
[http://diveintomark.org/archives/2002/06/02/important_change_to_the_link_tag autodiscovery] has been implemented several times in different ways and has never been standardized. This is a common source of difficulty for non-technical users.
- [Lovely]boy^_^/EnglishGrammer/Passive . . . . 15 matches
ex) Two hundred people are employed by the company.
B. When we use the passive, who or what causes the action is often unknown or unimportant.(그리니까 행위주체가 누군지 모를때나 별로 안중요할때 수동태 쓴대요)
ex) A lot of money was stolen in the robbery.
If we want to say who does or what causes the action, we use by(수동태에서 누가 했는지 알고 싶으면 by 쓰래요)
ex) This house was built by my grandfather.
active) Somebody will clean the room later.
passive) The room will be cleaned later.
ex) The music was very loud and could be heard from a long way away.
active) Somebody should have cleaned the room.
passive) The room should have been cleaned.
ex) I haven't received the letter yet. It might have been sent to the wrong address.
active) The room looks nice. Somebody has cleaned it.
passive) The room looks nice. It has been cleaned.
active) The room looked nice. Somebody had cleaned it.
passive) The room looked nice. It had been cleaned.
active) Somebody is cleaning the room right now.
passive) The room is being cleaned right now.
active) Somebody was cleaning the room when I arrived.
passive) The room was being cleaned when I arrived.
ex) We gave the police the information. (We gave the information to the police.)
- 영호의해킹공부페이지 . . . . 13 matches
about the way the world works-should be unlimited and total.
Always yield to the Hands-On imperative!
4. Hackers should be judged by their hacking, not bogus criteria such
6. Computers can change (your) life for the better.
manner of exploiting daemons - The Buffer Overflow.
The remote buffer overflow is a very commonly found and exploited bug in badly
coded daemons - by overflowing the stack one can cause the software to execute
a shell equal to its current UID - thus if the daemon is run as root, like
A buffer is a block of computer memory that holds many instances of the same
up over the top, or breaking their boundaries.
A stack has the property of a queue of objects being placed one on top of the
other, and the last object placed on the stack will be the first one to be
to the stack (PUSH) and removed (POP). A stack is made up of stack frames,
The stack pointer (SP) always points to the top of the stack, the bottom of it
is static. PUSH and POP operations manipulate the size of the stack
dynamically at run time, and its growth will either be down the memory
addresses, or up them. This means that one could address variables in the
stack by giving their offsets from SP, but as POP's and PUSH's occur these
offsets change around. Another type of pointer points to a fixed location
within a frame (FP). This can be used for referencing variables because their
- TheKnightsOfTheRoundTable . . . . 12 matches
=== TheKnightsOfTheRoundTable ===
{{| The radius of the round table is: r |}}
{{| The radius of the round table is: 2.828 |}}
|| 하기웅 || C++ || 1시간 || [TheKnightsOfTheRoundTable/하기웅] ||
|| 김상섭 || C++ || 엄청 || [TheKnightsOfTheRoundTable/김상섭] ||
|| 문보창 || C++ || 10분 || [TheKnightsOfTheRoundTable/문보창] ||
|| 허준수 || C++|| ? || [TheKnightsOfTheRoundTable/허준수] ||
- LearningToDrive . . . . 11 matches
I can remeber clearly the day I first began learning to drive. My mother and I were driving up Interstate 5 near Chico, California, a horizon. My mom had me reach over from the passenger seat and hold the steering wheel. She let me get the feel of how motion of the wheel affected the dirction of the car. Then she told me, "Here's how you drive. Line the car up in the middle of the lane, straight toward the horizon."
I very carefully squinted straight down the road. I got the car smack dab in the middle of the lane, pointed right down the middle of the road. I was doing great. My mind wandered a little...
I jerked back to attention as the car hit the gravel. My mom (her courage now amazes me) gently got the car back straight on the road. The she actually taught me about driving. "Driving is not about getting the car goint in the right direction. Driving is about constantly paying attention, making a little correction this way, a little correction that way."
This is the paradigm for XP. There is no such thing as straight and level. Even if things seem to be going perfectly, you don't take your eyes off the road. Change is the only constant. Always be prepared to move a little this way, a little that way. Sometimes maybe you have to move in a completely different direction. That's life as a programmer.
Everythings in software changes. The requirements change. The design changes. The business changes. The technology changes. The team changes. The team members change. The problem isn't change, per se, because change is going to happen; the problem, rather, is the inability to cope with change when it comes.
The driver of a software project is the customer. If the software doesn't do what they want it to do, you have failed. Of course, they don't know exactly what the software should do. That's why software development is like steering, not like getting the car pointed straight down the road. Out job as programmers is to give the customer a steering wheel and give them feedback about exactly where we are on the road.
소프트웨어 개발을 운전을 배우는 것에 비유한 설명이 재미있네요. software project 의 Driver 는 customer 라는 말과.. Programmer 는 customer 에게 운전대를 주고, 그들에게 우리가 정확히 제대로 된 길에 있는지에 대해 feedback 을 주는 직업이라는 말이 인상적이여서. 그리고 customer 와 programmer 와의 의견이 수렴되어가는 과정이 머릿속으로 그려지는 것이 나름대로 인상적인중. 그리고 'Change is the only constant. Always be prepared to move a little this way, a little that way. Sometimes maybe you have to move in a completely different direction. That's life as a programmer.' 부분도.. 아.. 부지런해야 할 프로그래머. --;
- ReadySet 번역처음화면 . . . . 11 matches
Software development projects require a lot of "paperwork" in the form of requirements documents, design documents, test plans, schedules, checklists, release notes, etc. It seems that everyone creates the documents from a blank page, from the documents used on their last project, or from one of a handful of high-priced proprietary software engineering template libraries. For those of us who start from a blank page, it can be a lot of work and it is easy to forget important parts. That is not a very reliable basis for professional engineering projects.
'''* What is the goal of this project?'''
ReadySET is an open source project to produce and maintain a library of reusable software engineering document templates. These templates provide a ready starting point for the documents used in software development projects. Using good templates can help developers work more quickly, but they also help to prompt discussion and avoid oversights.
'''* What are some key features that define the product?'''
'''*What makes this product different from others?'''
This is an open source project that you are welcome to use for free and help make better. Existing packages of software engineering templates are highly costly and biased by the authorship of only a few people, by vendor-client relationships, or by the set of tools offered by a particular vendor.
These templates are in pure XHTML with CSS, not a proprietary file format. That makes them easier to edit and to track changes using freely available tools and version control systems. The templates are designed to always be used on the web; they use hyperlinks to avoid duplicating information.
The templates are not burdened with information about individual authorship or document change history. It is assumed that professional software developers will keep all project documents in version control systems that provide those capabilities.
These templates are not one-size-fits-all and they do not attempt to provide prescriptive guidance on the overall development process. We are developing a broad library of template modules for many purposes and processes. The templates may be filled out in a suggested sequence or in any sequence that fits your existing process. They may be easily customized with any text or HTML editor.
'''*What is the scope of this project?'''
'''*What are the high-level assumptions or ground rules for the project?'''
I assume that the user takes ultimate responsibility for the content of all their actual project documents. The templates are merely starting points and low-level guidance.
This project does not attempt to provide powerful tools for reorganizing the templates, mapping them to a given software development process, or generating templates from a underlying process model. This project does not include any application code for any tools, users simply use text editors to fill in or customize the templates.
Yes. It is part of the Tigris.org mission of promoting open source software engineering. It is also the first product in a product line that will provide even better support to professional software developers. For more information, see [http://www.readysetpro.com ReadySET Pro] .
'''*What is the status of this project?'''
These templates are based on templates originally used to teach software engineering in a university project course. They are now being enhanced, expanded, and used more widely by professionals in industry.
The template set is fairly complete and ready for use in real projects. You can [http://readyset.tigris.org/servlets/ProjectDocumentList download] recent releases. We welcome your feedback.
For the latest news, see the [http://readyset.tigris.org/servlets/ProjectNewsList Project Announcements].
ReadySET is aimed at software engineers who wish that their projects could go more smoothly and professionally. ReadySET can be used by anyone who is able to use an HTML editor or edit HTML in a text editor.
*2. [http://readyset.tigris.org/servlets/ProjectDocumentList Download] the templates and unarchive
- TwistingTheTriad . . . . 11 matches
http://www.object-arts.com/Papers/TwistingTheTriad.PDF
http://www.esug.org/summerschools/2000_Southampton/twistingTheTriad/twistingTheTriad.pdf
with a widget-based system it is easy to avoid having to think about the (required) separation between the user interface and the application domain objects, but it is all too easy to allow one's domain code to become inextricably linked with the general interface logic.
it was much more that the widget system was just not flexible enought. We didn't know at the time, but were just starting to realise, that Smalltalk thrives on plugability and the user interface components in out widget framework were just not fine-grained enough.
One example of this deficiency surfaced in SmalltalkWorkspace widget. This was originally designed as a multiline text-editing component with additional logic to handle user interface commands such as Do-it, Show-it, Inspect-it etc. The view itself was a standard Windows text control and we just attached code to it to handle the workspace functionality. However, we soon discovered that we also wanted to have a rich text workspace widget too. Typically the implementation of this would have required the duplication of the workspace logic from the SmalltalkWorkspace component or, at least, an unwarranted refactoring session. It seemed to us that the widget framework could well do with some refactoring itself!
In MVC, most of the application functionality must be built into a model class known as an Application Model. It is the reponsibility of the application model to be the mediator between the true domain objects and the views and their controllers. The views are responsible for displaying the domain data while the controller handle the raw usr gestures that will eventually perform action on this data. So the application model typically has method to perform menu command actions, push buttons actions and general validation on the data that it manages. Nearly all of the application logic will reside in the application model classes. However, because the application model's role is that of a go-between, it is at times necessary for it to gain access to the user interface directly but, because of the Observer relationship betweeen it and the view/controller, this sort of access is discouraged.
For example, let's say one wants to explicitly change the colour of one or more views dependent on some conditions in the application model. The correct way to do this in MVC would be to trigger some sort of event, passing the colour along with it. Behaviour would then have to be coded in the view to "hang off" this event and to apply the colour change whenever the event was triggered. This is a rather circuitous route to achieving this simple functionality and typically it would be avoided by taking a shoutcut and using #componentAt : to look up a particular named view from the application model and to apply the colour change to the view directly. However, any direct access of a view like this breaks the MVC dictum that the model should know nothing about the views to which it is connected. If nothing else, this sort of activity surely breaks the possibility of allowing multiple views onto a model, which must be the reason behind using the Observer pattern in MVC in the first place.
=== TwistingTheTriad : ModelViewPresenter ===
This is the data upon which the user interface will operate. It is typically a domain object and the intention is that such objects should have no knowledge of the user interface. Here the M in MVP differs from the M in MVC. As mentioned above, the latter is actually an Application Model, which holds onto aspects of the domain data but also implements the user interface to manupulate it. In MVP, the model is purely a domain object and there is no expectation of (or link to) the user interface at all.
The behaviour of a view in MVP is much the same as in MVC. It is the view's responsibility to display the contents of a model. The model is expected to trigger appropriate change notification whenever its data is modified and these allow the view to "hang off" the model following the standard Observer pattern. In the same way as MVC does, this allows multiple vies to be connected to a single model.
One significant difference in MVP is the removal of the controller. Instead, the view is expected to handle the raw user interface events generated by the operating system (in Windows these come in as WM_xxxx messages) and this way of working fits more naturally into the style of most modern operating systems. In some cases, as a TextView, the user input is handled directly by the view and used to make changes to the model data. However, in most cases the user input events are actually routed via the presenter and it is this which becomes responsible for how the model gets changed.
While it is the view's responsibility to display model data it is the presenter that governs how the model can be manipulated and changed by the user interface. This is where the heart of an application's behaviour resides. In many ways, a MVP presenter is equivalent to the application model in MVC; most of the code dealing with how a user interface works is built into a presenter class. The main difference is that a presenter is ''directly'' linked to its associated view so that the two can closely collaborate in their roles of supplying the user interface for a particular model.
Compared with our orignnal widget framework, MVP offers a much greater separation between the visual presentation of an interface and the code required to implement the interface functionality. The latter resides in one or more presenter classes that are coded as normal using a standard class browser.
- [Lovely]boy^_^/EnglishGrammer/PresentAndPast . . . . 10 matches
This means) She is driving now, at the time of speaking. The action is not finished.
B. I am doing something = I'm in the middle of doing something; I've started doing it and I haven't finished yet.
Often the action is happening at the time of speaking.
But the action is not necessarily happening at the time of speaking.
ex) I'm reading an interesting book at the moment. I'll lend it to you when I've finished it.
This means) Tom is not reading the book at the time of speaking.
He means that he has started it but has not finished it yet. He is in the middle of reading it.
C. We use the present continuous when we talk about things happening in a period around now. (today / this week / tonight, etc..)
We use the present contunuous when we talk about changes happening now or around now.
ex) The population of the world is rising very fast.
B. We use the simple present to talk about things in general. We use it to say that something happens all the time
or repeateldy or that something is true in general. It is not important whether the action is happening at the time of speaking
In the following examples do is also the main verb( do가 메인 동사로 쓰일때도 있다. )
D. We use the simple present when we say how often we do things ( 빈도를 나타내는 문장을 만들때는 단순 현재를 쓴다. )
ex) In the summer Hohn usually plays tennis once or twice a week.
Note the position of always/never/usually, etc... (before the main verb, after be verb) ( 위치 주의 )
We use the present continuous for something that is happening at or around the time of speaking.
The action is not finished. sometimes, Use the Present continuous for temporary situations.
We use the simple present for things in general or things that happen repeatedly.
Sometimes, Use the simple present for permanent situations.
- Garbage collector for C and C++ . . . . 8 matches
# This causes the collector to assume that all inaccessible
# Finalization and the test program are not usable in this mode.
# (Clients should also define GC_SOLARIS_THREADS and then include
# -DALL_INTERIOR_POINTERS allows all pointers to the interior
# -DSMALL_CONFIG tries to tune the collector for small heap sizes,
# -DLARGE_CONFIG tunes the collector for unusually large heaps.
# causes all objects to be padded so that pointers just past the end of
# an object can be recognized. This can be expensive. (The padding
# -DDONT_ADD_BYTE_AT_END disables the padding.
# the GC process. This is no less correct than many malloc
# -DNO_EXECUTE_PERMISSION may cause some or all of the heap to not
# code from the heap. Currently this only affects the incremental
# -DGC_NO_OPERATOR_NEW_ARRAY declares that the C++ compiler does not support
# the new syntax "operator new[]" for allocating and deleting arrays.
# See gc_cpp.h for details. No effect on the C part of the collector.
# Unless the following macros are defined, realloc is also redirected
# Calloc and strdup are redefined in terms of the new malloc. X should
# be either GC_malloc or GC_malloc_uncollectable, or
# GC_debug_malloc_replacement. (The latter invokes GC_debug_malloc
# It requires that the following two macros also be used.)
- OperatingSystemClass/Exam2002_2 . . . . 8 matches
4. Consider a paging system with the page table stored in memory.
* If we add associative registers and 75 percent of all page-table references are found in the associative regsters, what is the effective memory time? (Assume that finding a page-table entry in the associative registers takes zero time, if the entry is there)
5. Consider the following page reference string:
How many page faults would occur for the following replacement algorithm, assuming one, three, five, seven frames? Remember all frames are initially empty, so your first unique pages will all cost one fault each.
6. Consider a file currently consisting of 100 blocks. Assume that the file control block(and the index block, in the case of indexed allocation) is already in memory, Calculate how many disk I/O operations are required for contiguous, linked and indexed (single-level) allocation strategies, if for one block, the following conditions hold. In the contiguous allocation case, assume that there is no room to grow in the beginning, but there is room to grow in the end. Assume that the block information to be added in stored in memory.
* The block is added at the beginning.
* The block is added in the middle.
* The block is added at the end.
* The block is removed from the beginning.
* The block is removed from the middle.
* The block is removed from the end.
7. Suppose that a disk drive has 5000 cylinders, numbered 0 to 4999. The drive is currently serving a request at cylinder 143, and the previous requrest was at cylinder 125. The queue of pending requests, in FIFO order, is
Starting from the current head position, what is the total distance (in cylinders) that the disk arm moves to satisfy all the pending requrests, for each of the following disk scheduling algorithms?
- SmalltalkBestPracticePatterns/DispatchedInterpretation . . . . 8 matches
Back in the days when data was separated from computation, and seldom the twain should meet, encoding decisions were critical. Any encoding decision you made was propagated to many different parts of the computation. If you got the encoding wrong, the cost of change was enormous. The longer it took to find the mistake, the more ridiculous the bill.
과거로 돌아가서 데이타가 연산으로부터 불리되었을 때, 그리고 종종 그 둘이 만나야 했을 때, 인코딩 결정은 중대한 것이었다. 너의 어떠한 인코딩 결정은 연산의 많은 다른 부분들을 점차적으로 증가시켜나아갔다. 만약 잘못된 인코딩을 한다면, 변화의 비용은 막대하다. The longer it took to find the mistake, the more ridiculous the bill.
Objects change all this. How you distribute responsibility among objects is the critical decision, encoding is a distant second. For the most part, in well factored programs, only a single object is interested in a piece of information. That object directly references the information and privately performs all the needed encoding and decoding.
Sometimes, however, information in one object must influence the behavior of another. When the uses of the information are simple, or the possible choices based on the information limited, it is sufficient to send a message to the encoded object. Thus, the fact that boolean values are represented as instances of one of two classes, True and False, is hidden behind the message #ifTrue:ifFalse:.
We could encode boolean values some other way, and as long as we provided the same protocol, no client would be the wiser.
Sets interact with their elements like this. Regardless of how an object is represented, as long it can respond to #=and #hash, it can be put in a Set.
Sometimes, encoding decisions can be hidden behind intermediate objects. And ASCII String encoded as eight-bit bytes hides that fact by conversing with the outside world in terms of Characters:
When there are many different types of information to be encoded, and the behavior of clients changes based on the information, these simple strategies won't work. The problem is that you don't want each of a hundred clients to explicitly record in a case statement what all the types of information are.
For example, consider a graphical Shape represented by a sequence of line, curve, stroke, and fill commands. Regardless of how the Shape is represented internally, it can provide a message #commandAt: anInteger that returns a Symbol representing the command and #argumentsAt: anInteger that returns an array of arguments. We could use these messages to write a PostScriptShapePrinter that would convert a Shape to PostScript:
Every client that wanted to make decisions based on what commands where in a Shape would have to have the same case statement, violating the "once and only once" rule. We need a solution where the case statement is hidden inside of the encoded objects.
* ''Have the client send a message to the encoded object. PAss a parameter to which the encoded object will send decoded messages.''
The simplest example of this is Collection>>do:. By passing a one argument Block(or any other object that responds to #value:), you are assured that the code will work, no matter whether the Collection is encoded as a linear list, an array, a hash table, or a balanced tree.
This is a simplified case of Dispatched Interpretation because there is only a single message coming back. For the most part, there will be several messages. For example, we can use this pattern with the Shape example. Rather than have a case statement for every command, we have a method in PostScriptShapePrinter for every command, For example:
Rather than Shapes providing #commandAt: and #argumentsAt:, they provide #sendCommantAt: anInteger to: anObject, where #lineFrom:to: is one of the messages that could be sent back. Then the original display code could read:
This could be further simplified by giving Shapes the responsibility to iterate over themselves:
The name "dispatched interpretation" comes from the distribution of responsibility. The encoded object "dispatches" a message to the client. The client "interprets" the message. Thus, the Shape dispatches message like #lineFrom:to: and #curveFrom:mid:to:. It's up to the clients to interpret the messages, with the PostScriptShapePrinter creating PostScript and the ShapeDisplayer displaying on the screen.
- DesignPatternsAsAPathToConceptualIntegrity . . . . 7 matches
During our discussions about the organization of design patterns there was a comment about the difficulty of identifying the “generative nature” of design patterns. This may be a good property to identify, for if we understood how design patterns are used in the design process, then their organization may not be far behind. Alexander makes a point that the generative nature of design patterns is one of the key benefits. In practice, on the software side, the generative nature seems to have fallen away and the more common approach for using design patterns is characterized as “when faced with problem xyz…the solution is…” One might say in software a more opportunistic application of design patterns is prevalent over a generative use of design patterns.
The source of this difference may be the lack of focus on design patterns in the design process. In fact, we seldom see discussions of the design process associated with design patterns. It is as though design patterns are a tool that is used independent of the process. Let’s investigate this further:
· The existence of an architecture, on top of any object/class design
· The internal regularity (….or conceptual integrity) of the architectural design
This is what Brooks wrote 25 years ago. "… Conceptual integrity is the most important consideration in system design."[Brooks 86] He continues: “The dilemma is a cruel one. For efficiency and conceptual integrity, one prefers a few good minds doing design and construction. Yet for large systems one wants a way to bring considerable manpower to bear, so that the product can make a timely appearance. How can these two needs be reconciled?”
One approach would be to identify and elevate a single overriding quality (such as adaptability or isolation of change) and use that quality as a foundation for the design process. If this overriding quality were one of the goals or even a specific design criteria of the process then perhaps the “many” could produce a timely product with the same conceptual integrity as “a few good minds.” How can this be accomplished and the and at least parts of the “cruel dilemma” resolved?
The following summary is from “Design Patterns as a Litmus Paper to Test the Strength of Object-Oriented Methods” and may provide some insight:
1. Some O-O design methodologies provide a systematic process in the form of axiomatic steps for developing architectures or micro-architectures that are optimality partitioned (modularized) according to a specific design criteria.
2. The following methodologies are listed according to their key design criteria for modularization:
a. Booch in OOSE relies heavily on expert designers and experience to provide the system modularization principle.
b. OMT, Coad-Yourdon, Shaer-Mellor are data driven and as such raise data dependency as the system modularization principle.
c. Wirfs-Brock with Responsibility Driven Design (RDD) raises contract minimization as the system modularization principle.
d. Snoeck with Event Driven Design (EDD) raises existence dependency as the system modularization principle.
3. According to the authors only RDD and EDD have axiomatic rules for OO design and therefore are strong OO design methods.
4. Design patterns provide guidance in designing micro-architectures according to a primary modularization principle: “encapsulate the part that changes.”
5. EDD and RDD will generate different design patterns that meet the primary modularization principle “encapsulate the part that changes.” in different ways when applied according to their axiomatic rules. For example RDD generates Mediator, Command, Template Method and Chain of responsibility (mostly behavior) where as EDD generates Observer, Composite, and Chain of responsibility (mostly structure).
Now putting this together with the earlier discussion about conceptual integrity we can propose some questions for discussion:
· Will strong O-O design methods produce results for the “many” with the same conceptual integrity as “a few good minds.”
· Does the product have conceptual integrity?
· Along what principle (experience, data, existence dependency, contract minimization, or some unknown principle) is the application partitioned?
- SolarSystem/상협 . . . . 7 matches
// Calculate The Aspect Ratio Of The Window
glMatrixMode(GL_MODELVIEW); // Select The Modelview Matrix
MessageBox(NULL,"Failed To Register The Window Class."
if(MessageBox(NULL,"The Requested FUllscreen Mode is Not Supported By\n Your video Card. Use Windowed Mode Instead?","NeHeGl",MB_YESNO|
MessageBox(NULL,"Can't Set The PixelFormat"
MessageBox(NULL,"Can't Activate The GL Rendering Context"
- UML/CaseTool . . . . 7 matches
''Diagramming'' in this context means ''creating'' and ''editing'' UML [[diagram]]s; that is diagrams that follow the graphical notation of the Unified Modeling Language.
The diagramming part of the Unified Modeling Language seems to be a lesser debated part of the UML, compared to code generation.
The UML diagram notation evolved from elderly, previously competing notations. UML diagrams as a means to draw diagrams of - mostly - [[Object-oriented programming|object oriented]] software is less debated among software developers. If developers draw diagrams of object oriented software, there is widespread consensus ''to use the UML notation'' for that task. On the other hand, it is debated, whether those diagrams are needed at all, on what stage(s) of the software development process they should be used and whether and how (if at all) they should be kept up-to date, facing continuously evolving program code.
''[[Code generation]]'' in this context means, that the user creates UML diagrams, which have some connoted model data, from which the UML tool derives (through a conversion process) parts or all of the [[source code]] for the software system that is to be developed. Often, the user can provide some skeleton of the program source code, in the form of a source code [[template]] where predefined tokens are then replaced with program source code parts, emitted by the UML tool during the code generation process.
There is some debate among software developers about how useful code generation as such is. It certainly depends on the specific problem domain and how far code generation should be applied. There are well known areas where code generation is an established practice, not limited to the field of UML. On the other hand, the idea of completely leaving the "code level" and start "programming" on the UML diagram level is quite debated among developers, and at least, not in such widespread use compared to other [[software development]] tools like [[compiler]]s or [[Configuration management|software configuration management systems]]. An often cited criticism is that the UML diagrams just lack the detail which is needed to contain the same information as is covered with the program source. There are developers that even state that "the Code ''is'' the design" (articles [http://www.developerdotstar.com/mag/articles/reeves_design_main.html] by Jack W. Reeves [http://www.bleading-edge.com/]).
''Reverse engineering'' in this context means, that the UML tool reads program source code as input and ''derives'' model data and corresponding graphical UML diagrams from it (as opposed to the somewhat broader meaning described in the article "[[Reverse engineering]]").
Reverse engineering encloses the problematic, that diagram data is normally not contained with the program source, such that the UML tool, at least in the initial step, has to create some ''random layout'' of the graphical symbols of the UML notation or use some automatic ''layout algorithm'' to place the symbols in a way that the user can understand the diagram. For example, the symbols should be placed at such locations on the drawing pane that they don't overlap. Usually, the user of such a functionality of an UML tool has to manually edit those automatically generated diagrams to attain some meaningfulness. It also often doesn't make sense to draw diagrams of the whole program source, as that represents just too much detail to be of interest at the level of the UML diagrams. There are also language features of some [[programming language]]s, like ''class-'' or ''function templates'' of the programming language [[C plus plus|C++]], which are notoriously hard to convert automatically to UML diagrams in their full complexity.
There are UML tools that use the attribute ''round trip'' (sometimes also denoted as ''round trip engineering'') to connote their ability to keep the ''source code'', the ''model data'' and the corresponding ''UML diagrams'' ''in sync''.
This means that the user should be able to change either the ''model data'' (together with the corresponding diagrams) or the ''program source code'' and then the UML tool updates the other part automatically.
Rational Software Architect, Together가 유명하고, 오픈 소스로는 Argo, Violet 이 유명하다.
- LawOfDemeter . . . . 6 matches
within our class can we just starting sending commands and queries to any other object in the system will-
nilly? Well, you could, but that would be a bad idea, according to the Law of Demeter. The Law of Demeter
What that means is that the more objects you talk to, the more you run the risk of getting broken when one
of them changes. So not only do you want to say as little as possible, you don't want to talk to more
objects than you need to either. In fact, according to the Law of Demeter for Methods, any method of an
any parameters that were passed in to the method.
Specifically missing from this list is methods belonging to objects that were returned from some other
()). Direct access of a child like this extends coupling from the caller farther than it needs to be. The
caller is depending on these facts:
Now the caller is only depending on the fact that it can add a foo to thingy, which sounds high level
The disadvantage, of course, is that you end up writing many small wrapper methods that do very little but
delegate container traversal and such. The cost tradeoff is between that inefficiency and higher class
The higher the degree of coupling between classes, the higher the odds that any change you make will break
Depending on your application, the development and maintenance costs of high class coupling may easily
Now back to to the ask vs. tell thing. To ask is a query, to tell is a command. I subscribe to the notion
of maintaining these as separate methods. Why bother?
It helps to maintain the "Tell, Don't Ask" principle if you think in terms of commands that perform a very
tossing data out, you probably aren't thinking much in the way of invariants).
If you can assume that evaluation of a query is free of any side effects, then you can:
use queries from within a debugger without affecting the process under test.
- NamedPipe . . . . 6 matches
A named pipe is a named, one-way or duplex pipe for communication between the pipe server and one or more pipe clients. All instances of a
named pipe share the same pipe name, but each instance has its own buffers and handles, and provides a separate conduit for client-server communication. The use of instances enables multiple pipe clients to use the same named pipe simultaneously.
Any process can access named pipes, subject to security checks, making named pipes an easy form of communication between related or unrelated processes. Named pipes can be used to provide communication between processes on the same computer or between processes on different computers across a network.
Any process can act as both a server and a client, making peer-to-peer communication possible. As used here, the term pipe server refers to a process that creates a named pipe, and the term pipe client refers to a process that connects to an instance of a named pipe.
// The main loop creates an instance of the named pipe and
// then waits for a client to connect to it. When the client
// with that client, and the loop is repeated.
// Wait for the client to connect; if it succeeds, // 클라이언트를 연결을 기다린다.
// the function returns a nonzero value. If the function returns // 접속이 될 경우 0 아닌 값이 리턴 되며
// The client could not connect, so close the pipe.
// The thread's parameter is a handle to a pipe instance.
// Read client requests from the pipe.
// Write the reply to the pipe.
// Flush the pipe to allow the client to read the pipe's contents
// before disconnecting. Then disconnect the pipe, and close the
// Break if the pipe handle is valid.
// Exit if an error other than ERROR_PIPE_BUSY occurs.
// The pipe connected; change to message-read mode.
// Send a message to the pipe server.
// Read from the pipe.
- 알고리즘3주숙제 . . . . 6 matches
from [http://www.csc.liv.ac.uk/~ped/teachadmin/algor/d_and_c.html The university of liverpool of Computer Science Department]
Consider the following problem: one has a directory containing a set of names and a telephone number associated with each name.
The directory is sorted by alphabetical order of names. It contains n entries which are stored in 2 arrays:
Given a name and the value n the problem is to find the number associated with the name.
A set of n points in the plane.
The distance between the two points that are closest.
Note: The distance DELTA( i, j ) between p(i) and p(j) is defined by the expression:
The (2n)-digit decimal representation of the product x*y = z
Note: The algorithm below works for any number base, e.g. binary, decimal, hexadecimal, etc. We use decimal simply for convenience.
- DPSCChapter2 . . . . 5 matches
Before launching into our descriptions of specific design patterns, we present a case study of sorts, involving multiple patterns. In the Design Pattern preface, the Gang of Four speak about moving from a "Huh?" to an "Aha!" experience with regard to understanding design patterns. We present here a little drama portraying such a transition. It consists of three vignettes: three days in the life of two Smalltalk programmers who work for MegaCorp Insurance Company. We are listening in on conversations between Don (an object newbie, but an experienced business analyst) and Jane (an object and pattern expert). Don comes to Jane with his design problems, and they solve them together. Although the characters are fictitious, the designs are real and have all been part of actual systems written in Smalltalk. Our goal is to demonstrate how, by careful analysis, design patterns can help derive solutions to real-world problems.
Jane : That's all right. I don't mind at all. What's the problem?
Don : It's this claims-processing workflow system I've been asked to design. I just can't see how the objects will work together. I think I've found the basic objects in the system, but I don't understand how to make sense from their behaviors.
Don : Here, let me show you the section of the requirements document I've got the problem with:
1. Data Entry. This consists of various systems that receive health claims from a variety of different sources. All are logged by assigning a unique identifier. Paper claims and supporting via OCR (optical character recognition) to capture the data associated with each form field.
2. Validation. The scanned and entered forms are validated to ensure that the fields are consistent and completely filled in. Incomplete or improperly filled-in forms are rejected by the system and are sent back to the claimant for resubmittal.
3. Provider/Plan Match. An automated process attempts to mach the plan (the contract unser which the claim is being paid) and the health care provider (e.g., the doctor) identified on the claim with the providers with which the overall claim processing organization has a contract. If there is no exact match, the program identifies the most likely matches based on soundex technology (an algorithm for finding similar-sounding words). The system displays prospective matches to knowledge workers in order of the likeinhood of the match, who then identify the correct provider.
4. Automatic Adjudication. The system determines whether a claim can be paid and how much to pay if and only if there are no inconsistencies between key data items associated with the claim. If there are inconsistencies, the system "pends" the claim for processing by the appropriate claims adjudicator.
5. Adjudication of Pended Claims. The adjudicator can access the system for a claim history or a representation of the original claim. The adjudicator either approves the claim for payment, specifying the proper amount to pay, or generates correspondence denying the claim.
- EffectiveC++ . . . . 5 matches
* ''생성자 및 소멸자와 적절히 상호동작하기 때문에. they are clearly the superior choice.''
=== Item 5: Use the same form in corresponding uses of new and delete ===
* ''Initialization of the pointer in each of the constructors. If no memory is to be allocated to the pointer in a particular constructor, the pointer should be initialized to 0 (i.e., the null pointer). - 생성자 각각에서 포인터 초기화''
* ''Deletion of the existing memory and assignment of new memory in the assignment operator. - 포인터 멤버에 다시 메모리를 할당할 경우 기존의 메모리 해제와 새로운 메모리의 할당''
* ''Deletion of the pointer in the destructor. - 소멸자에서 포인터 삭제''
// fails, call the global
// (if there is one)
X::set_new_handler(0); // set the X-specific
// immediately. (There is
size = 1; // by treating them as
if (the allocation was successful)
return (a pointer to the memory);
if (rawMemory == 0) return; // do nothing if the null
// deallocate the memory pointed to by rawMemory;
return; // delete handle the request
// deallocate the memory pointed to by rawMemory;
=== Item 9: Avoid hiding the "normal" form of new ===
String s = "The Truth Is Out There";
=== Item 13: List members in an initialization list in the order in which they are declared ===
The C++ language standard is unusually clear on this topic. 베이스 클래스에 대한 포인터를 사용해서 계승된 클래스를 [[BR]]
- RSS . . . . 5 matches
The technology behind RSS allows you to subscribe to websites that have provided RSS feeds, these are typically sites that change or add content regularly. To use this technology you need to set up some type of aggregation service. Think of this aggregation service as your personal mailbox. You then have to subscribe to the sites that you want to get updates on. Unlike typical subscriptions to pulp-based newspapers and magazines, your RSS subscriptions are free, but they typically only give you a line or two of each article or post along with a link to the full article or post.
The RSS formats provide web content or summaries of web content together with links to the full versions of the content, and other meta-data. This information is delivered as an XML file called RSS feed, webfeed, RSS stream, or RSS channel. In addition to facilitating syndication, RSS allows a website's frequent readers to track updates on the site using a news aggregator.
Before RSS, several similar formats already existed for syndication, but none achieved widespread popularity or are still in common use today, and most were envisioned to work only with a single service. For example, in 1997 Microsoft created Channel Definition Format for the Active Channel feature of Internet Explorer 4.0. Another was created by Dave Winer of UserLand Software. He had designed his own XML syndication format for use on his Scripting News weblog, which was also introduced in 1997 [1].
RDF Site Summary, the first version of RSS, was created by Dan Libby of Netscape in March 1999 for use on the My Netscape portal. This version became known as RSS 0.9. In July 1999 Netscape produced a prototype, tentatively named RSS 0.91, RSS standing for Rich Site Summary, this was a compromise with their customers who argued the complexity introduced (as XML namespaces) was unnecessary. This they considered a interim measure, with Libby suggesting an RSS 1.0-like format through the so-called Futures Document [2].
Soon afterwards, Netscape lost interest in RSS, leaving the format without an owner, just as it was becoming widely used. A working group and mailing list, RSS-DEV, was set up by various users to continue its development. At the same time, Winer posted a modified version of the RSS 0.91 specification - it was already in use in their products. Since neither side had any official claim on the name or the format, arguments raged whenever either side claimed RSS as its own, creating what became known as the RSS fork. [3]
The RSS-DEV group went on to produce RSS 1.0 in December 2000. Like RSS 0.9 (but not 0.91) this was based on the RDF specifications, but was more modular, with many of the terms coming from standard metadata vocabularies such as Dublin Core. Nineteen days later, Winer released RSS 0.92, a minor and (mostly) compatible revision of RSS 0.91. The next two years saw various minor revisions of the Userland branch of RSS, and its adoption by major media organizations, including The New York Times.
Winer published RSS 2.0 in 2002, emphasizing "Really Simple Syndication" as the meaning of the three-letter abbreviation. RSS 2.0 remained largely compatible with RSS 0.92, and added the ability to add extension elements in their own namespaces. In 2003, Winer and Userland Software assigned ownership of the RSS 2.0 specification to his then workplace, Harvard's Berkman Center for the Internet & Society.
- User Stories . . . . 5 matches
User stories serve the same purpose as use cases but are not the same. They are used to create time estimates for the release planning meeting. They are also used instead of a large requirements document. User Stories are written by the customers as things that the system needs to do for them. They are similar to usage scenarios, except that they are not limited to describing a user interface. They are in the format of about three sentences of text written by the customer in the customers terminology without techno-syntax.
User stories also drive the creation of the acceptance tests. One or more automated acceptance tests must be created to verify the user story has been correctly implemented.
One of the biggest misunderstandings with user stories is how they differ from traditional requirements specifications. The biggest
difference is in the level of detail. User stories should only provide enough detail to make a reasonably low risk estimate of how long the story will take to implement. When the time comes to implement the story developers will go to the customer and receive a detailed description of the requirements face to face.
Developers estimate how long the stories might take to implement. Each story will get a 1, 2 or 3 week estimate in "ideal development time". This ideal development time is how long it would take to implement the story in code if there were no distractions, no other assignments, and you knew exactly what to do. Longer than 3 weeks means you need to break the story down further. Less than 1 week and you are at too detailed a level, combine some stories. About 80 user stories plus or minus 20 is a perfect number to create a release plan during release planning.
Another difference between stories and a requirements document is a focus on user needs. You should try to avoid details of specific technology, data base layout, and algorithms. You should try to keep stories focused on user needs and benefits as opposed to specifying GUI layouts.
- ACM_ICPC . . . . 4 matches
* [http://icpckorea.org/2019/regional/scoreboard/ 2019년 스탠딩] - TheOathOfThePeachGarden Rank 81(CAU - Rank 52, including Abroad team)
* team 'TheOathOfThePeachGarden' 본선 81위(학교 순위 52위) : [한재현], [김영기], [오준석]
- BookShelf/Past . . . . 4 matches
1. [TheElementsOfProgrammingStyle] - 20051018
1. [TheElementsOfStyle] - 20060304
1. [IntroductionToTheTheoryOfComputation]
- MoinMoinBugs . . . . 4 matches
Tables don't work right if there are trailing spaces.
''Yes, by design, just like headings don't accept trailing spaces. In the case of headings, it is important because "= x =" is somewhat ambiguous. For tables, the restriction could be removed, though.''
And as a fun sidenote, the UserPreferences cookie doesn't seem to work. The cookie is in my ~/.netscape/cookies file still. My EfnetCeeWiki and XmlWiki cookies are duplicated!? It is kind of like the bug you found when I, ChristianSunesson, tried this feature with netscape just after you deployed it.
Hehe, and my changes are not logged to the RecentChanges database, I'll hope you find these changes this year. :) BUG BUG BUG!
''Well, Netscape suxx. I send the cookies with the CGI'S path, w/o a hostname, which makes it unique enough. Apparently not for netscape. I'll look into adding the domain, too.''
Hmmm...I use NetScape, MsIe, MoZilla and Galeon. I haven't had a problem but some other's using MoinMoin 0.8 have intermittently lost cookies. Any ideas?
* Solve the problem of the Windows filesystem handling a WikiName case-indifferent (i.e. map all deriatives of an existing page to that page).
* Check whether the passed WikiName is valid when editing pages (so no pages with an invalid WikiName can be created); this could also partly solve the case-insensitive filename problem (do not save pages with a name only differing in case)
* InterWiki links should either display the destination Wiki name or generate the A tag with a TITLE attribute so that (at least in IE) the full destination is displayed by floating the cursor over the link. At the moment, it's too hard to figure out where the link goes. With that many InterWiki destinations recognised, we can't expect everyone to be able to recognise the URL.
* Hover over the interwiki icon and you'll already get a tooltip, I'll look into the title attribute stuff.
* RecentChanges can tell you if something is updated, or offer you a view of the diff, but not both at the same time.
* If you want the ''latest'' diff for an updated page, click on "updated" and then on the diff icon (colored glasses) at the top.
* That's what I'm doing for the time being, but by the same rationale you don't need to offer diffs from RecentChanges at all.
* The intent is to not clutter RecentChanges with functions not normally used. I do not see a reason you want the lastest diff when you have the much better diff to your last visit.
* It'd be really nice if the diff was between now and the most recent version saved before your timestamp (or, failing that, the oldest version available). That way, diff is "show me what happened since I was last here", not just "show me what the last edit was."
* Hmmm, that '''is''' so. :) Take a look at the message at the top of the diff page after clicking on "updated", it'll often show text like "spanning x versions". You need the current CVS version for that, though.
* Oh, okay. Is this MoinMoin CVS enabled? Reason being: I did a few updates of a page, and was only being shown the last one. I'll try that some more and get back to you.
* Not CVS, but versioning all the same. I mean you have to get the most recent code from the SourceForge CVS archive for some features to work, if you test on a ''local'' wiki.
With 0.3, TitleIndex is broken if first letter of Japanese WikiName is multibyte character. This patch works well for me but need to be fixed for other charsets.
''Differently broken. :) I think we can live with the current situation, the worst edges are removed (before, chopping the first byte out of an unicode string lead to broken HTML markup!). It will stay that way until I buy the [wiki:ISBN:0201616335 Unicode 3.0] book.''
- MoniWikiPo . . . . 4 matches
msgid "Upload new Attachment \"%s\" on the \"%s\""
msgid "<b>horizontal rule</b> ---- is not applied on the blog mode."
msgid "Difference between yours and the current"
msgid "Difference between r%s and the current"
msgid "There are no changes found"
msgid "Update with these Keywords"
msgid "These pages share a similar word..."
msgid "These pages share an initial or final title word..."
msgid "Others"
"your email address in the UserPreferences."
msgid "Please contact the system administrator for htaccess based logins."
"If you want to subscribe this page please contact the WikiMaster to activate "
"the e-mail notification"
"email address in the UserPreferences."
#: ../plugin/theme.php:23
msgid "Theme cleared. Goto UserPreferences."
#: ../plugin/theme.php:63
msgid "Please select a theme properly."
msgid "Send TrackBack Ping to another Blog:"
msgid "not acceptable character found in the password!"
- MoniWikiTheme . . . . 4 matches
=== 임의의 Theme 설정 및 지원 ===
http://chemie.skku.ac.kr/wiki/wiki.php/TwinPages?action=theme&theme=kz
http://chemie.skku.ac.kr/wiki/wiki.php/TwinPages?action=theme&theme=blog
http://chemie.skku.ac.kr/wiki/wiki.php/TwinPages?action=theme&theme=samplehome
{{{[[Theme]]}}}매크로를 이용하여 지원 가능한 Theme목록을 볼 수 있다.
[[Theme]]
- MoreEffectiveC++/Miscellany . . . . 4 matches
== Item 32: Program in the Future tense ==
원문:As software developers, we may not know much, but we do know that things will change. We don't necessarily know what will change, how the changes will be brought about, when the changes will occur, or why they will take place, but we do know this: things will change.
좋은 소프트웨어는 변화를 잘 수용한다. 새로운 기능을 수용하고, 새로운 플랫폼에 잘 적용되고, 새로운 요구를 잘 받아 들이며, 새로운 입력을 잘 잡는다. 이런 소프트웨어는 유연하고, 강하고, 신뢰성있고, 돌발 상황(사고)에 의해 죽지 않는다. 이런 소프트웨어는 미래에 필요한 요소를 예상하고, 오늘날 구현시에 포함시키는 프로그래머들에 의해서 디자인된다. 이러한 종류의 소프트웨어는-우아하게 변화하는 소프트웨어- ''program in the future tens''(매래의 프로그램:이하 영문 직접 사용)을 감안하는 사람들이 작성한다.
"변화한다.", 험난한 소프트웨어의 발전에 잘 견디는 클래스를 작성하라. (원문:Given that things will change, writeclasses that can withstand the rough-and-tumble world of software evolution.) "demand-paged"의 가상 함수를 피하라. 다른 이가 만들어 놓지 않으면, 너도 만들 방법이 없는 그런 경우를 피하라.(모호, 원문:Avoid "demand-paged" virtual functions, whereby you make no functions virtual unless somebody comes along and demands that you do it) 대신에 함수의 ''meaning''을 결정하고, 유도된 클래스에서 새롭게 정의할 것인지 판단하라. 그렇게 되면, 가상(virtual)으로 선언해라, 어떤 이라도 재정의 못할지라도 말이다. 그렇지 않다면, 비가상(nonvirtual)으로 선언해라, 그리고 차후에 그것을 바꾸어라 왜냐하면 그것은 다른사람을 편하게 하기 때문이다.;전체 클래스의 목적에서 변화를 유지하는지 확신을 해라.
== Item 34: Understand how to combine C++ and C in the same program ==
== Item 35: Familiarize yourself with °the language standard. ==
출반된 1990년 이후, ''The Annotated C++ Reference Manual''은 프로그래머들에게 C++에 정의에 참고문서가 되어 왔다. ARM기 나온 이후에 몇년간 ''ISO/ANSI committe standardizing the language'' 는 크고 작게 변해 왔다. 이제 C++의 참고 문서로 ARM은 더 이상 만족될수 없다.
''The Design and Evolution of C++''에 거의 모든 변화가 언급되어 있다. 현재 C++ 참고서(1994년 이후에 쓰여진것들)도 이 내용을 포함하고 있을 것이다. (만약 당신이 찾지 못하면 그거 버려라) 덧붙여 ''More Effective C++''(이책이다.)는 이러한 새로운 부분에 관한 대부분의 사용 방법이 언급되어 있다. 만약 당신이 이것에 리스트를 알고 싶다면, 이 책의 인덱스를 살펴보아라.
표준 라이브러리에 일어나는 것들에 대한것에서 C++의 정확한 규정의 변화가 있다. 개다가 표준 라이브러리의 개선은 언어의 표준 만큼이나 알려지지 않는다. 예를 들어서 ''The Design and Evolution of C++'' 거의 표준 라이브러리에 관한 언급이 거의 없다. 그 책의 라이브러리에 과한 논의라면 때때로 있는 데이터의 출력이다. 왜냐하면, 라이브러리는 1994년에 실질적으로 변화되었기 때문이다.
Fortunately, this syntactic administrivia is automatically taken care of when you #include the appropriate headers.
=== The Standard Template Library : 표준 템플릿 라이브러리 ===
int *firstFive = find(values, // search the range
5); // for the value 5
int *firstValue = find(values+10, // search the range
age); // for the value in age
그렇지만 이 템플릿은 좋다, 개다가 일반화 까지 할수 있다. 시작과 끝에 연산자를 보아라. 사용된 연산자는 다르다는 것, dereferencing, prefix증가(Item 6참고), 복사(함수의 반환 값을 위해서? Item 9참고)를 위해서 쓰였다. 모든 연산자는 우리가 overload할수 있다. (DeleteMe 모호) 그래서 왜 포인터 사용하여 찾기를 제한하는가? 왜 허용하지 않는가 포인터 추가에서 이러한 연산자를 지원하기 위한 어떤 객체도 허용할수 없을까? (hy not allow any object that supports these operations to be used in addition to pointers?) 그래서 이렇게 하는것은 포인터 연산자의 built-in 의미를 찾기함수(find function)을 자유롭게 할것이다. 예를 들어서 우리는 리스트 에서 다음 리스트로의 이동을 해주는 prefix increment 연산자의 linked list객체와 비슷한 pointer를 정의할수 있다.
- NSIS/예제2 . . . . 4 matches
ComponentText "This will install the less simple example2 on your computer. Select which optional things you want installed."
; The text to prompt the user to enter a directory
; Set output path to the installation directory.
; The text to prompt the user to enter a directory
; It will install notepad.exe into a directory that the user selects,
ComponentText "This will install the less simple example2 on your computer. Select which optional things you want installed."
; The text to prompt the user to enter a directory
; The stuff to install
; Set output path to the installation directory.
ComponentText: "This will install the less simple example2 on your computer. Select which optional things you want installed." "" ""
- Robbery/조현태 . . . . 4 matches
이전의 경우 도둑이 특정시간에 존재할 수 없는경우 "The robber has escaped." 를 출력했으나, 지금은 모든 시간의 움직임을 고려해서 존재하지 않으면 "The robber has escaped."를 출력하도록 수정하였다. (사실 소스상에선 그다지 바뀐건 없다..^^)
cout << "The robber has escaped." << endl;
cout << "Time step " << i + 1 << ": The robber has been at " << g_maxPoints[0][i].x + 1 << "," << g_maxPoints[0][i].y + 1 << "." << endl;
- eXtensibleStylesheetLanguageTransformations . . . . 4 matches
Extensible Stylesheet Language Transformations, or XSLT, is an XML-based language used for the transformation of XML documents. The original document is not changed; rather, a new document is created based on the content of an existing one. The new document may be serialized (output) by the processor in standard XML syntax or in another format, such as HTML or plain text. XSLT is most often used to convert data between different XML schemas or to convert XML data into web pages or PDF documents.
XSLT was produced as a result of the Extensible Stylesheet Language (XSL) development effort within W3C during 1998–1999, which also produced XSL Formatting Objects (XSL-FO) and the XML Path Language, XPath. The editor of the first version (and in effect the chief designer of the language) was James Clark. The version most widely used today is XSLT 1.0, which was published as a Recommendation by the W3C on 16 November 1999. A greatly expanded version 2.0, under the editorship of Michael Kay, reached the status of a Candidate Recommendation from W3C on 3 November 2005.
- 데블스캠프2009/목요일/연습문제/MFC/서민관 . . . . 4 matches
// IDM_ABOUTBOX must be in the system command range.
// Set the icon for this dialog. The framework does this automatically
// when the application's main window is not a dialog
return TRUE; // return TRUE unless you set the focus to a control
// If you add a minimize button to your dialog, you will need the code below
// to draw the icon. For MFC applications using the document/view model,
// this is automatically done for you by the framework.
// Draw the icon
// The system calls this to obtain the cursor to display while the user drags
// the minimized window.
// NOTE: the ClassWizard will add member initialization here
// NOTE: the ClassWizard will add DDX and DDV calls here
// IDM_ABOUTBOX must be in the system command range.
// Set the icon for this dialog. The framework does this automatically
// when the application's main window is not a dialog
return TRUE; // return TRUE unless you set the focus to a control
// If you add a minimize button to your dialog, you will need the code below
// to draw the icon. For MFC applications using the document/view model,
// this is automatically done for you by the framework.
// Draw the icon
- 임인택/내손을거친책들 . . . . 4 matches
* The Haskell School of Expression
* IPv6, The New Internet Protocol
* TheElementsOfStyle + TheElementsOfProgrammingStyle
- AOI/2004 . . . . 3 matches
|| [TheTrip] || . || X || O || O || O || O || . || O ||
|| [CheckTheCheck] || . || . || O || . || . || . || . || O ||
|| [TheArcheologist'sDilemma]|| . || . || X || . || . || . || . || . ||
- ErdosNumbers/차영권 . . . . 3 matches
bool isThere(Author *p, int n);
if (isThere(author[i], saveBound[i]))
bool isThere(Author *author, int n)
- LIB_3 . . . . 3 matches
/* Init The Scheduler List
/* Create The Task
// Init The Stack
// Init the TCB by argument <----- 함수에서 얻은 변수들로... 초기화...ok???
/* Delete the Task
/* Find Ready Task & Run the Task
- Linux/필수명령어/용법 . . . . 3 matches
The Oct 1 15:57:23 KST 1996
- $ echo "The RedHat !"
- The RedHat !
- $ ln project theplan ,,두 개의 이름은 같은 문서를 의미한다.
- then
- echo "It's changed to the blade.room"
- ModelViewPresenter . . . . 3 matches
TwistingTheTriad
ConnectingTheDots
Model-View-Presenter or MVP is a next generation programming model for the C++ and Java programming languages. MVP is based on a generalization of the classic MVC programming model of Smalltalk and provides a powerful yet easy to understand design methodology for a broad range of application and component development tasks. The framework-based implementation of these concepts adds great value to developer programs that employ MVP. MVP also is adaptable across multiple client/server and multi-tier application architectures. MVP will enable IBM to deliver a unified conceptual programming model across all its major object-oriented language environments.
- MoinMoinTodo . . . . 3 matches
This is a list of things that are to be implemented. If you miss a feature, have a neat idea or any other suggestion, please put it on MoinMoinIdeas.
To discuss the merit of the planned extensions, or new features from MoinMoinIdeas, please use MoinMoinDiscussion.
A list of things that are added to the current source in CVS are on MoinMoinDone.
MoinMoinRelease describes how to build a release from the SourceForge repository.
Things to do in the near future:
* add a nice progress page, while the dictionary cache is built
* add a means to build the dict.cache file from the command line
* Macro that lists all users that have an email address; a click on the user name sends the re-login URL to that email (and not more than once a day).
* Send a timestamp with the EditPage link, and then compare to the current timestamp; warn the user if page was edited since displaying.
* Now that we can identify certain authors (those who have set a user profile), we can avoid to create a backup copy if one author makes several changes; we have to remember who made the last save of a page, though.
* Implement the update script (copying new images etc.) described elsewhere on this page or MoinMoinIdeas.
* Replace SystemPages by using the normal "save page" code, thus creating a backup copy of the page that was in the system. Only replace when diff shows the page needs updating.
* Other things like color, icons, menu?
* On request, send email containing an URL to send the cookie
* a CSS switch (needs more work on the formatter issue to really work)
* create a dir per page in the "backup" dir; provide an upgrade.py script to adapt existing wikis
* or go all the way, and store pages as data/pages/<firstletter>/<pagename>/(current|meta|...|<timestamp>)
* Add a link to Wiki:EditThePageSimultaneously (or a link to a local copy) to the edit conflict message.
* [[SiteMap]]: find the hotspots and create a hierarchical list of all pages (again, faster with caching)
* Remember when someone starts to edit a page, and warn when someone else opens the same page for editing
- PersonalHistory . . . . 3 matches
* [TheJavaMan] - 2004년 3월 2일 종료
* [TheJavaMan/비행기게임] - 2004년 3월 2일 종료
* [TheJavaMan/숫자야구] - 2004년 1/26일 종료
- PythonForStatement . . . . 3 matches
These represent finite ordered sets indexed by non-negative numbers. The built-in function len() returns the number of items of a sequence. When the length of a sequence is n, the index set contains the numbers 0, 1, ..., n-1. Item i of sequence a is selected by a[i].
{{|There are six sequence types: strings, Unicode strings, lists, tuples, buffers, and xrange objects|}}
- SmallTalk/문법정리 . . . . 3 matches
* 모든 스몰토크 표현식이 다음과 같은 양식을 따른다.All Smalltalk expressions follow the form:
"The message sent is #squared"
"The message sent is #asUppercase"
"The message sent is #factorial"
* 선택자는 단일 식별자이며, 인수는 없다.(the selector is a single Identifier, there are no arguments)
* 선택자는 특정한 기호(하나나 둘이상의 문자, 숫자가 아님)이고, 인수가 딱 하나만 있다.(the selector is one or two non-alphanumeric characters, followed by exactly one argument object)
"argument is the Integer object 5"
"argument is the String 'xyz'"
"argument is the Integer object 20"
* 각 키워드에 인수가 있을 때, 선택자는 하나 이상의 키워드이다.(the selector is one or more keywords, when called each keyword is followed by an argument object) -> 세번째 예시 참고
Point x: 4 y: 200. "receiver is the object Point"
* Unary 메세지는 가장 높은 우선 순위를 가진다. messages have the highest precedence.
* Binary 메세지는 그 다음의 우선 순위를 가진다. Binary message have the next precedence.
* Keyword 메세지는 가장 낮은 우선 순위를 가진다.Keyword message have the lowest precedence.
- TAOCP . . . . 3 matches
* Title : TheArtOfComputerProgramming
* TheArtOfComputerProgramming(TAOCP) vol1. FundamentalAlgorithms을 읽는다.
[TAOCP/NotesOnTheExercises]
- TheWarOfGenesis2R . . . . 3 matches
[TheWarOfGenesis2R/일지]
[TheWarOfGenesis2R/ToDo]
|| ["TheWarOfGenesis2R/Temp"] ||
- WindowsTemplateLibrary . . . . 3 matches
{{|The Windows Template Library (WTL) is an object-oriented Win32 encapsulation C++ library by Microsoft. The WTL supports an API for use by programmers. It was developed as a light-weight alternative to Microsoft Foundation Classes. WTL extends Microsoft's ATL, another lightweight API for using COM and for creating ActiveX controls. Though created by Microsoft, it is unsupported.
In an uncharacteristic move by Microsoft—an outspoken critic of open source software—they made the source code of WTL freely available. Releasing it under the open-source Common Public License, Microsoft posted the source on SourceForge, an Internet open-source repository. The SourceForge version is 7.5.
Being an unsupported library, WTL has little formal documentation. However, most of the API is a direct mirror of the standard Win32 calls, so the interface is familiar to most Windows programmers.|}}
- 프로젝트 . . . . 3 matches
* [TheJavaMan] - 2004년 3월 2일 종료
* [TheJavaMan/비행기게임] - 2004년 3월 2일 종료
* [TheJavaMan/숫자야구] - 2004년 1/26일 종료
- ActiveTemplateLibrary . . . . 2 matches
{{|The Active Template Library (ATL) is a set of template-based C++ classes that simplify the programming of Component Object Model (COM) objects. The COM support in Visual C++ allows developers to easily create a variety of COM objects, Automation servers, and ActiveX controls.
- Ajax . . . . 2 matches
* The Document Object Model manipulated through JavaScript to dynamically display and interact with the information presented
* The XMLHttpRequest object to exchange data asynchronously with the web server. (XML is commonly used, although any text format will work, including preformatted HTML, plain text, and JSON)
Like DHTML, LAMP, or SPA, Ajax is not a technology in itself, but a term that refers to the use of a group of technologies together. In fact, derivative/composite technologies based substantially upon Ajax, such as AFLAX are already appearing.
Ajax applications use web browsers that support the above technologies as a platform to run on. Browsers that support these technologies include Mozilla Firefox, Microsoft Internet Explorer, Opera, Konqueror and Apple Safari.
- Boost/SmartPointer . . . . 2 matches
// The original code for this example appeared in the shared_ptr documentation.
// argument, so would not work as intended. At that point the code was
// The application will produce a series of
// This example demonstrates the handle/body idiom (also called pimpl and
// several other names). It separates the interface (in this header file)
// from the implementation (in shared_ptr_example2.cpp).
// is still valid because the type is complete where it counts - in the
- BoostLibrary/SmartPointer . . . . 2 matches
// The original code for this example appeared in the shared_ptr documentation.
// argument, so would not work as intended. At that point the code was
// The application will produce a series of
// This example demonstrates the handle/body idiom (also called pimpl and
// several other names). It separates the interface (in this header file)
// from the implementation (in shared_ptr_example2.cpp).
// is still valid because the type is complete where it counts - in the
- C++ . . . . 2 matches
C++ (pronounced "see plus plus") is a general-purpose computer programming language. It is a statically typed free-form multi-paradigm language supporting procedural programming, data abstraction, object-oriented programming, and generic programming. During the 1990s, C++ became one of the most popular commercial programming languages.
Bell Labs' Bjarne Stroustrup developed C++ (originally named "C with Classes") during the 1980s as an enhancement to the C programming language. Enhancements started with the addition of classes, followed by, among many features, virtual functions, operator overloading, multiple inheritance, templates, and exception handling. The C++ programming language standard was ratified in 1998 as ISO/IEC 14882:1998, the current version of which is the 2003 version, ISO/IEC 14882:2003. New version of the standard (known informally as C++0x) is being developed.
In C and C++, the expression x++ increases the value of x by 1 (called incrementing). The name "C++" is a play on this, suggesting an incremental improvement upon C.|}}
- CarmichaelNumbers/문보창 . . . . 2 matches
Carmichael Numbers를 찾는 Theorem이 있는 듯하다. 그러나 때려맞추기(?)로 문제를 풀어도 풀린다. 그러나 속도는 떨어진다.
cout << "The number " << n << " is a Carmichael number.\n";
- EdsgerDijkstra . . . . 2 matches
* [http://www.cs.utexas.edu/users/EWD/ewd03xx/EWD340.PDF TheHumbleProgrammer]
위의 Stepwise Program Construction과 The Humble Programmer는 초강력 추천. 감동의 물결. 아마 그 글을 읽고 몇 주 동안은 여러가지 실험을 해보며 흥미진진하게 보내게 될 것이며, 몇 몇은 프로그래밍에 획기적인 전환점을 맞이할 수 있을 것이라 믿음. --김창준
- EightQueenProblemDiscussion . . . . 2 matches
def testIsAttackableOthers (self):
self.assertEquals (self.bd.IsAttackableOthers (3,3),1)
self.assertEquals (self.bd.IsAttackableOthers (7,1),0)
self.assertEquals (self.bd.IsAttackableOthers (4,4),1)
자신에게 항상 "What is the simplest thing that could possibly work?"라는 질문을 하면서 TestDrivenDevelopment를 했나요? 테스트/코드 사이클을 진행하면서 스텝을 작게 하려고 노력했나요? 중간에 진척이 별로 없는 경우, 어떤 액션을 취했나요? 그 때 테스트 사이클의 스텝을 더 작게하려고 했나요? 만약 다시 같은 문제를 새로 푼다면 어떤 순서로 테스트를 하고 싶나요? (직접 다시 한번 새로 시작하는 것도 강력 추천) 왜 다른 사람들에 비해 시간이 상대적으로 많이 걸렸을까요? 테스트 코드를 사용한 것이 그 시간만큼의 이득이 있었나요? TestDrivenDevelopment를 해내가면서 현재 패스하려고 하는 테스트 케이스에서 무엇을 배웠나요? 켄트벡이 말하는 것처럼 사고의 도구가 되어 주었나요? 참고로 저는 EightQueenProblem을 파이썬으로 약 30분 정도 시간에 50 라인 이내로(테스트 코드 제외) 풀었습니다. TestDrivenDevelopment로요. --김창준
사고의 도구로써는 연습장과 TFP 둘 다 이용했지만, 순수하게 적용하지는 않았습니다. (위의 Queen을 놓는 부분에 대한 재귀호출부분에서는 적용못함) 테스트작성시간/코드작성시간 등에 대한 관리는 하지 않았습니다. (이 부분에 대해서는 반성을. ^^;) 흠.. 그리고 'The Simplest Thing'을 찾아나갔다기 보다도, 이미 해당 문제에 대해서 의사코드를 생각하고, 해당 코드에 대해 Top-Down 형태로 모듈을 나눈뒤에 모듈에 대해 테스트를 만들어갔다는 생각이 드네요. --석천
When the program is run, one has to give a number n (smaller than 32), and the program will return in how many ways n Queens can be put on a n by n board in such a way that they cannot beat each other.
Note that the d=(e-=d)&-e; statement can be compiled wrong on certain compilers. The inner assignment should be executed first. Otherwise replace it with e-=d,d=e&-e;.
- Expat . . . . 2 matches
Expat is a stream-oriented XML 1.0 parser library, written in C. Expat was one of the first open source XML parsers and has been incorporated into many open source projects, including the Apache HTTP Server, Mozilla, Perl, Python and PHP.
James Clark released version 1.0 in 1998 while serving as technical lead on the XML Working Group at the World Wide Web Consortium. Clark released two more versions, 1.1 and 1.2, before turning the project over to a group led by Clark Cooper, Fred Drake and Paul Prescod in 2000. The new group released version 1.95.0 in September 2000 and continues to release new versions to incorporate bug fixes and enhancements. Expat is hosted as a SourceForge project. Versions are available for most major operating systems.
To use the Expat library, programs first register handler functions with Expat. When Expat parses an XML document, it calls the registered handlers as it finds relevant tokens in the input stream. These tokens and their associated handler calls are called events. Typically, programs register handler functions for XML element start or stop events and character events. Expat provides facilities for more sophisticated event handling such as XML Namespace declarations, processing instructions and DTD events.
Expat's parsing events are similar to the events defined in the Simple API for XML (SAX), but Expat is not a SAX-compliant parser. Projects incorporating the Expat library often build SAX and DOM parsers on top of Expat.
- GDBUsage . . . . 2 matches
The GNU Debugger, usually called just GDB, is the standard debugger for the GNU software system. It is a portable debugger that runs on many Unix-like systems and works for many programming languages, including C, C++, and FORTRAN.
GDB is free software, covered by the GNU General Public License, and you are
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
Editing targets can be specified in these ways:
FUNCTION, to edit at the beginning of that function,
*ADDRESS, to edit at the line containing that address.
Dynamically load FILE into the running program, and record its symbols
Execute the rest of the line as a shell command.
- HowToStudyRefactoring . . . . 2 matches
* Separate The What From The How : "어떻게"와 "무엇을"을 분리하도록 하라. 어떤 리팩토링이 창발하는가?
- HowToStudyXp . . . . 2 matches
* The Timeless Way of Building : 패턴 운동을 일으킨 Christopher Alexander의 저작. On-site Customer, Piecemeal Growth, Communication 등의 아이디어가 여기서 왔다.
* The Psychology of Computer Programming (Gerald M. Weinberg) : 프로그래밍에 심리학을 적용한 고전. Egoless Programming이 여기서 나왔다.
*Michael Feathers
- InvestMulti - 09.22 . . . . 2 matches
print '3. Move to another Nation '
print '3. Move to another Nation '
print 'This Nation has these items :: ' ,items.keys()[0] ,' , ', items.keys()[1]
print 'The Market price is ' , nation[user[NATION]] , ' bytes '
print 'This Nation has these items :: ' ,items.keys()[0] ,' , ', items.keys()[1]
print '3. Move to another Nation '
print 'This Nation has these items :: ' ,items.keys()[0] ,' , ', items.keys()[1]
print 'The Market price is ' , nation[user[NATION]]
print 'This Nation has these items :: ' ,items.keys()[0] ,' , ', items.keys()[1]
- MoinMoinDone . . . . 2 matches
* Strip closing punctuation from URLs, so that e.g. (http://www.python.org) is recognized properly. Closing punctuation is characters like ":", ",", ".", ")", "?", "!". These are legal in URLs, but if they occur at the very end, you want to exclude them. The same if true for InterWiki links, like MeatBall:InterWiki.
* Check for a (configurable) max size in bytes of the RecentChanges page while building it
* Inline code sections (triple-brace open and close on the same line, {{{~cpp like this}}} or {{{~cpp ThisFunctionWhichIsNotaWikiName()}}})
* SGML-Entities were replaced when saving them a second time, i.e. & #160; without the space had a problem.
* Added a means to add meta tags to the page header, like: {{{~cpp
- NetworkDatabaseManagementSystem . . . . 2 matches
The network model is a database model conceived as flexible way of representing objects and their relationships. Its original inventor was Charles Bachman, and it was developed into a standard specification published in 1969 by the CODASYL Consortium. Where the hierarchical model structures data as a tree of records, with each record having one parent record and many children, the network model allows each record to have multiple parent and child records, forming a lattice structure.
The chief argument in favour of the network model, in comparison to the hierarchic model, was that it allowed a more natural modeling of relationships between entities. Although the model was widely implemented and used, it failed to become dominant for two main reasons. Firstly, IBM chose to stick to the hierarchical model in their established products such as IMS and DL/I. Secondly, it was eventually displaced by the relational model, which offered a higher-level, more declarative interface. Until the early 1980s the performance benefits of the low-level navigational interfaces offered by hierarchical and network databases were persuasive for many large-scale applications, but as hardware became faster, the extra productivity and flexibility of relational systems won the day.
- PreviousFrontPage . . . . 2 matches
A WikiWikiWeb is a collaborative hypertext environment, with an emphasis on easy access to and modification of information. This wiki is also part of the InterWiki space.
MoinMoin is a Python WikiClone, based on PikiPiki. The name is a common German slang expression explained on the MoinMoin page. If you run a Wiki using MoinMoin, please add it to the MoinMoinWikis page.
You are encouraged to add to the MoinMoinIdeas page, and edit the WikiSandBox whichever way you like. Please try to restrain yourself from adding unrelated stuff, as I want to keep this clean and part of the project documentation.
You can edit any page by pressing the link at the bottom of the page. Capitalized words joined together form a WikiName, which hyperlinks to another page. The highlighted title searches for all pages that link to the current page. Pages which do not yet exist are linked with a question mark: just follow the link and you can add a definition.
To learn more about what a WikiWikiWeb is, read about WhyWikiWorks and the WikiNature. Also, consult the WikiWikiWebFaq.
* MoinMoinTodo: discussion about the improvement of MoinMoin
* FindPage: search or browse the database in various ways
- RoboCode . . . . 2 matches
||[TheJavaMan/로보코드]|| 휘동 ||
[TheJavaMan/로보코드]와 [JavaStudy2004/로보코드]를 여기로 합치면 좋지 않을까요?--[Leonardong]
- TheKnightsOfTheRoundTable/김상섭 . . . . 2 matches
cout << "The radius of the round table is: 0.000" << endl;
cout << "The radius of the round table is: " << temp << endl;
- TheKnightsOfTheRoundTable/하기웅 . . . . 2 matches
cout << "The radius of the round table is: 0.000"<<endl;
cout << "The radius of the round table is: " << 1.0*sqrt(halfSum*(halfSum-a)*(halfSum-b)*(halfSum-c))/halfSum << endl;
- TheOthers . . . . 2 matches
PL 마지막 팀 프로젝트 "The Others"팀의 프로젝트 페이지
-- TheOthers
- ThePriestMathematician/문보창 . . . . 2 matches
// 10254 - The Priest Mathematician
[ThePriestMathematician]
- TheTrip/Leonardong . . . . 2 matches
class TheTripTestCase(unittest.TestCase):
[TheTrip], [AOI]
- TheTrip/문보창 . . . . 2 matches
// no10137 - The Trip
[TheTrip] [문보창]
- ToyProblems . . . . 2 matches
ToyProblems를 풀게 하되 다음 방법을 이용한다. Seminar:TheParadigmsOfProgramming [http://www.jdl.ac.cn/turing/pdf/p455-floyd.pdf (pdf)]을 학습하게 하는 것이다.
* The Art and Craft of Problem Solving
- TugOfWar/강희경 . . . . 2 matches
def InputTheWeight(aN):
print MakeTwoTeams(InputTheWeight(InputPeopleNumber()))
- VMWare/OSImplementationTest . . . . 2 matches
[ORG 0x7C00] ; The BIOS loads the boot sector into memory location
lgdt [gdt_desc] ; Load the GDT descriptor
mov eax, cr0 ; Copy the contents of CR0 into EAX
mov cr0, eax ; Copy the contents of EAX into CR0
mov ds, ax ; Move a valid data segment into the data segment register
mov ss, ax ; Move a valid data segment into the stack segment register
mov esp, 090000h ; Move the stack pointer to 090000h
gdt: ; Address for the GDT
gdt_end: ; Used to calculate the size of the GDT
gdt_desc: ; The GDT descriptor
dd gdt ; Address of the GDT
times 510-($-$$) db 0 ; Fill up the file with zeros
- [Lovely]boy^_^/Diary/12Rest . . . . 2 matches
* I read a Programming Pearls Chapter 6 a little, because I can't understand very well--;. So I read Chapter 7,8,9,10 roughly. In my opinion, there is no very serious contents.
* The DInput's message priority is maybe so high... It's very very fast.--; I can't control it.
* I saw a very good sentence in 'The Fighting'. It's "Although you try very hard, It's no gurantee that you'll be success. But All succecssfull man have tried."
- [Lovely]boy^_^/Diary/2-2-16 . . . . 2 matches
* I completely destroy the marriage and family final-exam.--;
* I borrow the Role Playing Game with DirectX.
* I read a novel named the Brain all day. Today's reading amount is about 600 pages. It's not so interesting as much as the price of fame.
* '''When I am given a motive, I can do the things extreme.'''
* '''There is no man nicer than a man who has a target, and rushs towards it.'''
* I studied Grammar in Use Chapter 39,40. I have not done study this book since then summer.--;
* I read a little Power Reading. Today's reading's principle content is using a regulator(ex) pen, pinger. etc). but this method is what I have used all the time.--; I should read a lot more.
* I studied ProgrammingPearls chapter 3. When I was reading, I could find familiar book name - the Mythical Man Month, and Code Complete.
* '''The more general problem may be easier to solve.'''
* '''Keeping the code simple is usually the key to correctness.'''
- 강희경/도서관 . . . . 2 matches
|| 4 || NoSmoke:TheArtOfComputerProgramming || 카누스 || [강희경] || [TAOCP] ||
|| 1 || NoSmoke:TheArtOfComputerProgramming || 카누스 || [강희경] || [TAOCP] ||
- 데블스캠프2009/목요일/연습문제/MFC/정종록 . . . . 2 matches
// IDM_ABOUTBOX must be in the system command range.
// Set the icon for this dialog. The framework does this automatically
// when the application's main window is not a dialog
return TRUE; // return TRUE unless you set the focus to a control
// If you add a minimize button to your dialog, you will need the code below
// to draw the icon. For MFC applications using the document/view model,
// this is automatically done for you by the framework.
// Draw the icon
// The system calls this to obtain the cursor to display while the user drags
// the minimized window.
// TODO: If this is a RICHEDIT control, the control will not
// send this notification unless you override the CDialog::OnInitDialog()
// with the ENM_CHANGE flag ORed into the mask.
- 새싹교실/2013/케로로반/실습자료 . . . . 2 matches
Social Executive of Computer Science and Engineering will hold a bar event. There are many pretty girls and handsome guys. It will be great day for you. Just come to the bar event and drink. There are many side dishes and beer. Please enjoy the event. but DO NOT drink too much, or FBI will come to catch you. Thank you.
- 알고리즘8주숙제 . . . . 2 matches
Given the denominations of coins for a newly founded country, the Dairy Republic, and some monetary amount, find the smallest set of coins that sums to that amount. The Dairy Republic is guaranteed to have a 1 cent coin.
Give a greedy method, which is heuristic, to solve the 0/1 knapsack problem and also give an example to show that it does not always yield an optimal solution.
The kanpsack problem is defined as follows:
Give a greedy method to find an optimal solution of the knapsack problem and prove its correctness.
Consider the problem of scheduling n jobs on one machine. Describe an algorithm to find a schedule such that its average completion time is minimum. Prove the correctness of your algorithm.
alph 3 beta 7 theta 10 |}}
{{| alph beta theta
- 오페라의유령 . . . . 2 matches
소설이 먼저였지만, 개인적으로 Webber 와 Sarah 의 노래를 엄청나게 좋아하는 관계로. 소설을 읽는 내내 머릿속에서 Think of Me, The Music of Night, Wishing you were somehow here again 가 배경음악으로 깔리었다.
웨버아저씨에게 상상력을 선사해준 소설이란? 원작에 상관없이 자신스타일로 작품을 만들어내는 웨버아저씨여서 (그래봤자 본건 하나뿐이지만; 한편은 대본읽음). 개인적인 결론은 해당 소설로부터 자신의 주제의식을 뽑아낸 웨버아저씨 멋져요 이긴 하지만, 이 소설이 태어나지 않았더라면 Phantom of the opera 가 나타나지 않았을 것이란 생각이 들기에. (소설의 구성 등을 떠나서, Phantom 이라는 캐릭터를 볼때)
뮤지컬의 이미지때문인지 (한번도 안본 뮤지컬에 대해 이미지를 떠올리는것도 우스운 일이다. OST와 Sarah 의 뮤직비디오는 많이 보긴 했지만) 크리스틴을 볼때마다 사라아주머니의 젊었을때의 사진을 떠올렸고, Phantom 이 등장할때엔 그 Main Theme (Phantom 의 그 멋진 웃음소리와도 같게 들리는...) 를 떠올렸다.
* EBS 에선가 Joseph and the Amazing Technicolor Dreamcoat를 방영해줬던 기억이 난다. 성경에서의 요셉이야기를 이렇게 표현할 수 있을까; 형 왈 '아마 성경을 이렇게 가르친다면 교회에서 조는 사람들 없을꺼야;' 어떻게 보면 '아아 꿈많고 성공한 사람. 우리도 요셉처럼 성공하려면 꿈을 가져야해;' 이런식이였지만, 아주 신선했던 기억이 난다.
* 암튼 Phantom of the opera 에서 가장 멋진 목소리는 Phantom 이라 생각. 그리고 당근 Sarah 아주머니; Phantom 이라는 캐릭터 이미지가 맘에 들어서. 그리고 노래도.
* 소설에서의 Angle of the music 은 Phantom 을 이야기하는것 같은데, 왜 Webber 의 노래에선 크리스틴을 지칭할까.
- 정모/2011.7.18 . . . . 2 matches
* 해결이 안 된 PIGS와 The lazy programmer를 다같이 풀기로 함.
* Free talking과 Theme talking으로 나누어 진행.
- 프로그래밍언어와학습 . . . . 2 matches
The fatal metaphor of progress, which means leaving things behind us, has utterly obscured the real idea of growth, which means leaving things inside us.
--G. K. Chesterton (1874-1936), British author. Fancies Versus Fads, "The Romance of Rhyme" (1923).
- 1002/TPOCP . . . . 1 match
Seminar:ThePsychologyOfComputerProgramming 맡은 챕터 정리궁리중.
Variations in the programming task
What the programmer is trying to do
- 2011년독서모임 . . . . 1 match
* 이와 관련해서 외국 음악이랑 외국 영화에 나오는 한국에 대해 찾아보려 했는데요,, 급 귀차니즘 때문에 외국 음악에 나오는 한국 관련된 것만 찾았다는...; 뭐,, 그래서 찾은 것이 Gary Moore의 Murder in the skies 라는 노래인데, 이 노래는 1983년 9월 1일에 뉴욕에서 출발한 한국행 비행기가 소련의 영공에 침범 했나(? -_-;; 죄송;;) 그래서 소련의 전투기가 Kal기를 격추시키는 일이 발생하였는데, 그것을 내용으로 소련의 만행으로 무고한 사람들이 죽음을 당했다는 것을 비판한 노래라 소개 했었고, 또 하나 찾아봤었던게 Deftones의 Korea라는 노래인데... 알고보니까 그냥 노래 내용이 어떤 소녀에 대한 이야기인데 그 소녀의 이름이 한국인 성과 비슷해서 그냥 그렇게 썻다고 해서 패스했습니다.
* [송지원] - 선물 The Present
- 2012년독서모임 . . . . 1 match
* [박한기] - The Goal
- 2dInDirect3d/Chapter2 . . . . 1 match
== Present The Scene ==
- 3N 1/김상섭 . . . . 1 match
4358392 2006-02-24 00:56:30 Accepted 2.207 4360 28565 C++ 100 - The 3n + 1 problem
- 3N+1/김상섭 . . . . 1 match
4358392 2006-02-24 00:56:30 Accepted 2.207 4360 28565 C++ 100 - The 3n + 1 problem
- 3N+1Problem/문보창 . . . . 1 match
// no100 - The 3n+1 Problem
- ACM_ICPC/2013년스터디 . . . . 1 match
* dynamic programming - [http://211.228.163.31/30stair/eating_together/eating_together.php?pname=eating_together 끼리끼리]
* [http://stackoverflow.com/questions/2631726/how-to-determine-the-longest-increasing-subsequence-using-dynamic-programming Time Complexity O(n log n) 의 Up Sequence]
* Consonants, Pogo, The Great Wall
then 겹침
- AcceleratedC++/Chapter11 . . . . 1 match
== 11.1 The Vec class ==
== 11.2 Implementing the Vec class ==
iterator data; // first element in the `Vec'
iterator avail; // (one past) the last element in the `Vec'
iterator limit; // (one past) the allocated memory
// allocate and initialize the underlying array
// destroy the elements in the array and free the memory
// destroy (in reverse order) the elements that were constructed
// return all the space that was allocated
// reset pointers to indicate that the `Vec' is empty again
// allocate new space and copy existing elements to the new space
// return the old space
// reset pointers to point to the newly allocated space
// free the array in the left-hand side
// copy elements from the right-hand to the left-hand side
// destroy (in reverse order) the elements that were constructed
// return all the space that was allocated
// reset pointers to indicate that the `Vec' is empty again
// allocate new space and copy existing elements to the new space
// return the old space
- AcceleratedC++/Chapter9 . . . . 1 match
== 9.4 The Student_info class ==
// clear the stream so that input will work for the next student
== 9.6 Using the Student_info class ==
// read and store the data
// alphabetize the student records
// write the names and grades
cout << students[i].name() // this and the next line changed
- ActiveXDataObjects . . . . 1 match
{{|Microsoft ADO (ActiveX Data Objects) is a Component object model object for accessing data sources. It provides a layer between programming languages and databases, which allows a developer to write programs which access data, without knowing how the database is implemented. No knowledge of SQL is required to access a database when using ADO, although one can use ADO to execute arbitrary SQL commands. The disadvantage of this is that this introduces a dependency upon the database.
{{|In the newer programming framework of .NET, Microsoft also present an upgraded version of ADO called ADO.NET, its object structure is quite different from that of traditional ADO. But ADO.NET is still not quite popular and mature till now.
- AnalyzeMary . . . . 1 match
주변에서 남들과 비슷하게 일을 하는 듯 하면서 늘 더 나은 성과를 보이는 사람들이 있다. 대부분은 "메리에겐 뭔가 특별한 것이 있다"(There is something about Mary) 수준의 감탄사를 외치는 데에서 끝난다. 그러면서 나는 왜 그들처럼 될 수 없을까 한탄하고, 곧 까맣게 잊는다.
- Athena . . . . 1 match
|| http://zeropage.org/~mulli2/Athena/Logo.bmp ||
DeleteMe 이름은 좋습니다. 하지만 ["Athena"] 라는 이름의 페이지에는 여신 아테나에 대한 정의와 소개가 들어 있는 것이 올바른 것이겠지요. 그래서 ["ProjectPrometheus"], ["ProjectZephyrus"] 라고 한거랍니다. ;; --["neocoin"]
* 5.6.2 Thereshold
- BaysianFiltering . . . . 1 match
그리고 PatternClassification 관련한 여러 알고리즘에도 BayesTheory 를 기본으로 하는게 상당히 많다.
- CauGlobal/Interview . . . . 1 match
* 수업이 한국에서와의 다른점은? ( ex Theory 위주인지? Practical 위주인지? )
- CheckTheCheck/곽세환 . . . . 1 match
[CheckTheCheck]
- Classes . . . . 1 match
[http://www.yes24.com/Goods/FTGoodsView.aspx?goodsNo=1949638&CategoryNumber=002001026004 Advanced Engineering Mathematics 9/E]
[http://www.xper.org/wiki/seminar/TheDragonBook]
[http://ocw.mit.edu/OcwWeb/Mathematics/18-06Spring-2005/CourseHome/index.htm Linear Algebra]
[http://kangcom.com/common/bookinfo/bookinfo.asp?sku=200302180005 Understanding the Linux Kernel (2nd Edition)]
- CleanCode . . . . 1 match
* [http://oddpoet.net/blog/2010/08/02/a-new-look-at-test-driven-development-kr/ BDD, Given/When/Then]
var array = stringObject.match(/regexp/); // if there is no match, then the function returns null, if not returns array.
var array = stringObject.match(/regexp/) || []; // if the function returns null, then substitute empty array.
- CompilerTheory/ManBoyTest . . . . 1 match
if k <= 0 then A := x4 + x5 else B
[CompilerTheory]
- ConstructorMethod . . . . 1 match
static Point* makeFromRnTheta(int r, int theta)
return makeFromXnY(r*cos(theta),r*sin(theta));
- CuttingSticks/문보창 . . . . 1 match
cout << "The minimum cutting is " << result << ".\n";
- DebuggingSeminar_2005/DebugCRT . . . . 1 match
// include crtdbg.h after all other headers.
//turn on the full heap checking
참조) [http://zeropage.org/wiki/AcceleratedC_2b_2b_2fChapter11#line287 The rule of Three]
- DocumentObjectModel . . . . 1 match
Document Object Model (DOM) is an application programming interface to access HTML and XML documents. It is programming language and platform independent. Behind the interface the document is represented with an object-oriented model.
Different variants of DOMs were initially implemented by web browsers to manipulate elements in an HTML document. This prompted the World Wide Web Consortium (W3C) to come up with a series of standard specifications for DOM (hence called W3CDOM).
DOM puts no restrictions on the document's underlying data structure. A well-structured document can take the tree form using DOM.
Most XML parsers (e.g., Xerces) and XSL processors (e.g., Xalan) have been developed to make use of the tree structure. Such an implementation requires that the entire content of a document be parsed and stored in memory. Hence, DOM is best used for applications where the document elements have to be randomly accessed and manipulated. For XML-based applications which involve a one-time selective read/write per parse, DOM presents a considerable overhead on memory. The SAX model is advantageous in such a case in terms of speed and memory consumption.
- English Speaking/The Simpsons/S01E04 . . . . 1 match
= There's no disgrace like home =
Homer : Another beer, Moe.
Moe : What's-a matter, Homer? Bloodiest fight of the year.
You're sitting there like a thirsty bump on a log.
who's been terrorizing the neighborhood.
Let the nice people enjoy their beers.
Ah, don't worry. This dog has the scent.
Homer : You can't talk that way about my kids! Or at least two of them.
- EnglishSpeaking/TheSimpsons . . . . 1 match
[[pagelist(^EnglishSpeaking/TheSimpsons/S01)]]
- EnglishSpeaking/TheSimpsons/S01E01 . . . . 1 match
Marge : Hmm. I get the feeling there's something you haven't told me, Homer.
Marge : You tell me that all the time.
Homer : Well, I would- I- I wanna do the Christmas shopping this year.
[EnglishSpeaking/TheSimpsons]
- EnglishSpeaking/TheSimpsons/S01E04 . . . . 1 match
= There's no disgrace like home =
Homer : Another beer, Moe.
Moe : What's-a matter, Homer? Bloodiest fight of the year.
You're sitting there like a thirsty bump on a log.
who's been terrorizing the neighborhood.
Let the nice people enjoy their beers.
Ah, don't worry. This dog has the scent.
Homer : You can't talk that way about my kids! Or at least two of them.
- ExtremeProgrammingExplained . . . . 1 match
ExtremeProgramming 의 철학을 소개한 서적. 저자 KentBeck. TheThreeExtremos 중 한명. 얼마전에 2판이 나왔다.
- FromDuskTillDawn/변형진 . . . . 1 match
else echo "There is no route Vladimir can take.<br>";
- FromDuskTillDawn/조현태 . . . . 1 match
cout << "There is no route Vladimir can take." << endl;
- Functor . . . . 1 match
A function object, often called a functor, is a computer programming construct allowing an object to be invoked or called as if it were an ordinary function, usually with the same syntax. The exact meaning may vary among programming languages. A functor used in this manner in computing bears little relation to the term functor as used in the mathematical field of category theory.
- Gof/Command . . . . 1 match
Command Pattern은 request 를 객체화함으로서 toolkit 객체로 하여금 불특정한 어플리케이션 객체에 대한 request를 만들게 한다. 이 객체는 다른 객체처럼 저장될 수 있으며 pass around 가능하다. 이 pattern의 key는 수행할 명령어에 대한 인터페이스를 선언하는 추상 Command class에 있다. 이 인터페이스의 가장 단순한 형태에서는 추상적인 Execute operation을 포함한다. 구체화된 Command subclass들은 request에 대한 receiver를 instance 변수로 저장하고 request를 invoke하기 위한 Execute operation을 구현함으로서 receiver-action 짝을 구체화시킨다. The receiver has the knowledge required to carry out the request.
- Gof/Composite . . . . 1 match
cout << "The net price is " << chassis->NetPrice () << endl;
Another subclass, RegisterTransferSet, is a Composite class for representing assignments that change several registers at once.
Another example of this pattern occurs in the financial domain, where a portfolio aggregates individual assets. You can support complex aggregations of assets by implementing a portfolio as a Composite that conforms to the interface of an individual asset [BE93].
* FlyweightPattern lets you share components, but they can no longer refer to their parents.
- Gof/Singleton . . . . 1 match
Smalltalk에서 unique instance를 리턴하는 functiond은 Singleton 클래스의 class method로 구현된다. 단일 인스턴스가 만들어지는 것을 보장하기 위해서 new operation을 override한다. The resulting Singleton class might have the following two class methods, where SoleInstance is a class variable that is not used anywhere else:
// Lookup returns 0 if there's no such singleton
static MySingleton theSingleton;
// ... other possible subclasses
POSITION position = m_ContainerOfSingleton->GetHeadPosition();
- GotoStatementConsideredHarmful . . . . 1 match
SeeAlso : PPR:GotoConsideredTheBestProgrammingPracticeEverInvented PPR:GotoStillConsideredHarmful PPR:GotoConsideredHarmful
- KnowledgeManagement . . . . 1 match
* Theoretical
- Lines In The Plane . . . . 1 match
==== Recurrent Problems - Lines In The Plane ====
What is the maximum number L<sub>n</sub> of regions defined by lines("unfolding" or "unwinding") in the plane?
===== mathematical expression =====
- LinuxSystemClass . . . . 1 match
학교 수업공부를 하거나 레포트를 쓰는 경우 위의 학교 교재와 함께 'The Design of the Unix Operating System' 을 같이 보면 도움이 많이 된다. 해당 알고리즘들에 대해서 좀 더 구체적으로 서술되어있다. 단, 책이 좀 오래된 감이 있다.
- MoinMoin . . . . 1 match
"Moin" meaning "Good Morning", and "MoinMoin" being an emphasis, i.e. "A ''Very'' Good Morning". The name was obviously chosen for its WikiWikiNess.
''No! Originally "MoinMoin" does '''not''' mean "Good Morning". "Moin" just means "good" or "nice" and in northern Germany it is used at any daytime, so "Good day" seems more appropriate.'' --MarkoSchulz
Mmmmh , seems that I can enrich so more info: "Moin" has the meaning of "Good Morning" but it is spoken under murmur like "mornin'" although the Syllable is too short alone, so it is spoken twice. If you shorten "Good Morning" with "morn'" it has the same effect with "morn'morn'". --Thomas Albl
We use it all day in the south too. I always thought it just morphed from a morning greeting to an all-day one. -- J
- MoinMoinDiscussion . . . . 1 match
Talk about the things on MoinMoinTodo and MoinMoinIdeas in this space...
'''A''': See the {{{~cpp [[Icon]]}}} macro; besides that, fully qualified URLs to the wiki server work, too.
* '''R''': The Icon macro worked well. I wanted to avoid the fully qualified URL because to access the Wiki in question requires password authentication. Including an image using the full URL caused my webserver (Apache 1.3.19) to reprompt for authentication whenever the page was viewed or re-edited. Perhaps a default {{{~cpp [[Image]]}}} macro could be added to the distribution (essentially identical to {{{~cpp [[Icon]]}}} ) which isn't relative to the data/img directory. (!) I've actually been thinking about trying to cook up my own "upload image" (or upload attachment) macro. I need to familiarize myself with the MoinMoin source first, but would others find this useful?
* '''Note:''' Regarding the upload feature - pls note that the PikiePikie also implemented in Python already has this feature, see http://pikie.darktech.org/cgi/pikie?UploadImage ... so I guess you could borrow some code from there :) -- J
- MoinMoinMailingLists . . . . 1 match
There are two mailing lists for MoinMoin:
- MoinMoinWikis . . . . 1 match
* [http://www.bioinformatics.org/piperwiki/moin.cgi Wiki for the Piper project]
* [http://compsoc.dur.ac.uk/~tsp/cgi-bin/triki.cgi TrikiWiki] (private wiki for the Transformers holiday - uses a mildly hacked MoinMoin)
* [http://lightingwiki.com/FrontPage The Lighting Wiki]
For more wikis, see the InterWiki list.
- MySQL . . . . 1 match
위의 PHP 버전은 어떻게 만들었을까? 바로.. MySQL 코드를 보고 만들었다고 한다.- UseTheSourceLuke --[1002]
- NSIS/예제1 . . . . 1 match
; The text to prompt the user to enter a directory
DirText "This will install the very simple example1 on your computer. Choose a directory"
Section "ThisNameIsIgnoredSoWhyBother?"
DirText: "This will install the very simple example1 on your computer. Choose a directory" "" ""
Section: "ThisNameIsIgnoredSoWhyBother?"
- NumberBaseballGame/jeppy . . . . 1 match
printf("You lose~\nThe answer is %c%c%c", hidden_num[0], hidden_num[1], hidden_num[2]);
- OOP . . . . 1 match
Object-oriented programming is based in the principle of recursive design.
2. Objects perform computation by making requests of each other through the passing of messages.
3. Every object has it's own memory, which consists of other objects.
5. The class is the repository for behabior associated with an object.
Program consists of objects interacting with eachother Objects provide services.
- OurMajorLangIsCAndCPlusPlus/string.h . . . . 1 match
|| void * memmove(void * dest, const void * scr, size_t count) || Moves one buffer to another. ||
|| char * strncpy(char * strDestination, const char * strSource, size_t count) || Copy characters of one string to another ||
|| int strcmpi(const char *stirng1, const char *string2) || Compares two strings to determine if they are the same. The comparison is not case-sensitive. ||
|| size_t strlen(const char *string) || Get the length of a string. ||
|| char * strrchr(const char *string, int c) || Scan a string for the last occurrence of a character. ||
|| size_t strspn(const char *string, const char *strCharSet) || Find the first substring. 포함개수?||
|| char * strtok(char *strToken, const char *strDelimit) || Find the next token in a string. ||
- ParserMarket . . . . 1 match
This is a marketplace for your parsers. Please state your name, your email, and the release your parser is developed for (if you used a CVS snapshot, also state the revision number).
Use a special pagename {{{~cpp ["parser/yourParser.py"]}}} and start your parser with the line {{{~cpp
This way, the parser can directly be put on the page without any modification, and as easily copied from that page. See the examples below.
There are also some UtilityScripts.
If you are not familiar with Python and/or the MoinMoin code base, but have a need or an idea for a parser, this is the place to ask for it. Someone might find it useful, too, and implement it.
- PragmaticVersionControlWithCVS/HowTo . . . . 1 match
|| [PragmaticVersionControlWithCVS/Getting Started] || [PragmaticVersionControlWithCVS/AccessingTheRepository] ||
- PragmaticVersionControlWithCVS/UsingTagsAndBranches . . . . 1 match
== Merging The Experimental Branch ==
- ProgrammingLanguageClass/Report2002_2 . . . . 1 match
1. To find out the maximum length of a variable name
1. To assess the type-compatibility rule adopted by the Compilers;
1. To evaluate the security of pointers in the Compilers;
1. To check the evaluation order of operands in the Compilers by raising the functional side-effects if possible;
1. To identify a situation in which the “add” operator would not be associative;
1. To determine the largest and smallest positive floating point number in Intel Pentium processor.
The output should be a sequence of test programs with the results generated from them. Your grade will be highly dependent on the quality of your test programs.
As usual, you shall submit a floppy diskette with a listing of your program and a set of test data of your own choice, and the output from running your program on your test data set.
Be sure to design carefully your test data set to exercise your program completely. You are also recommended in your documentation to include the rationale behind your test programs.
In order words, explain why you design them in such a way and what you intend to demonstrate
- ProgrammingPartyAfterwords . . . . 1 match
* NoSmok:TheArtOfComputerProgramming 에 나온 어셈블리어로 구현된 엘리베이터 시뮬레이션 (NoSmok:DonaldKnuth 가 직접 엘리베이터를 몇 시간 동안 타보고, 관찰하면서 만든 알고리즘이라고 함. 자기가 타고 다니는 엘리베이터를 분석, 고대로 시뮬레이션 해보는 것도 엄청난 공부가 될 것임)
- ProjectPrometheus/BugReport . . . . 1 match
Prometheus 의 버그 보고 페이지
* WAR 알아보기. ProjectPrometheus 배포가 편하도록.
* '''The Goal''' View Book 시 DB에 들어가지 않음.
우리는 여기에서 frequent release(give workable system to the customer every week)가 얼마나 중요한가 새삼 확인할 수 있다. --JuNe
- ProjectSemiPhotoshop/요구사항 . . . . 1 match
* Thereshold Binary Image (O 흑백)
- ProjectZephyrus/간단CVS사용설명 . . . . 1 match
# description: The cvspsever serves CVS Passowrd Server sessions; it uses \
# unencrypted username/password pairs for authentication.
- REFACTORING . . . . 1 match
특별히 때를 둘 필요는 없다. 틈나는 대로. Don Robert 의 The Rule of Three 원칙을 적용해도 좋을 것 같다.
- Refactoring/ComposingMethods . . . . 1 match
* You have a code fragment that can be grouped together.[[BR]]''Turn the fragment into a method whose name explains the purpose of the method.''
* A method's body is just as clear as its name. [[BR]] ''Put the method's body into the body of its callers and remove the method.''
* You have a temp that is assigned to once twith a simple expression, and the temp is getting in the way of other refactorings. [[BR]] ''Replace all references to that temp with the expression.''
* You have a complicated expression. [[BR]] ''Put the result of the expression, or parts of the expression,in a temporary variagle with a name that explains the purpose.''
* The code assigns to a parameter. ''Use a temporary variagle instead.''
''Turn the method into ints own object so that all the local variagles become fields on that object. You can then decompose the method into other methods on the same object.''
* You want to replace an altorithm with one that is clearer. [[BR]] ''Replace the body of the method with the new altorithm.''
- Refactoring/SimplifyingConditionalExpressions . . . . 1 match
* You have a complicated conditional (if-then-else) statement. [[BR]] ''Extract methods from the condition, then part, and else parts.''
* You have a sequence of conditional tests with the same result. [[BR]]''Combine them into a single conditional expression and extract it.''
// compute the disability amount
// compute the disability amount;
* The same fragment of code is in all branches of a conditional expression. [[BR]]''Move it outside of the expression.''
* A method has conditional behavior that does not make clear the normal path of execution [[BR]] ''Use guard clauses for all the special cases.''
* You have a conditional that chooses different behavior depending on the type of and object [[BR]] ''Move each leg of the conditional to an overriding method in a subclass. Make the orginal method abstract.''
* You have repeated checks for a null value[[BR]] ''Replace the null value with a null object.''
* A section of code assumes something about the state of the program. [[BR]]''Make the assumption explicit with an assertion.''
- STL/참고사이트 . . . . 1 match
The Code Project, C++/STL/MFC 에 대한 소개 http://www.codeproject.com/cpp/stlintroduction.asp
C++ Standard Template Library, another great tutorial, by Mark Sebern http://www.msoe.edu/eecs/cese/resources/stl/index.htm
- SeminarHowToProgramItAfterwords . . . . 1 match
* '테스트코드의 보폭을 조절하라. 상황에 따라 성큼성큼 보폭을 늘릴수도 있지만, 상황에 따라서는 보폭을 좁혀야 한다. 처음 TDD를 하는 사람은 보폭을 좁혀서 걸어가기가 오히려 더 힘들다' wiki:Wiki:DoTheSimplestThingThatCouldPossiblyWork. 이것이 훈련이 아직 덜된, TDD를 하는 사람에게는 얼마나 힘든지는 이번 RDP 짜면서 느꼈었는데. 열심히 훈련하겠습니다.
- StringOfCPlusPlus/상협 . . . . 1 match
String Test("The reverse function work well in English");
- TAOCP/BasicConcepts . . . . 1 match
C - 명령어 코드(the poeration code)
F - 명령어의 변경(a modification of the operation code). (L:R)이라면 8L+R = F
±AA - 메모리 주소(the address)
I - 인덱스(the index specification). 값이 1~6으로 rI1~rI6에 있는 내용과 메모리 주소를 더함
M이 가리키는 메모리 셀로 점프한다. JSJ를 빼면 점프를 하면서 점프 명령어 다음 위치를 rJ에 저장한다. the comparison indicator를 이용하거나(JL, JE, JG, JGE, JLE, JNE) , 레지스터(JrN, JrZ, JrP, JrNN, JrNZ, JrNP)를 이용한다.
HLT 명령은 기계를 멈춘다(The machine stops.)
=== Another Approach(Algorithm B) ===
- TestFirstProgramming . . . . 1 match
ex) ["TFP예제/Omok"], ["TFP예제/Queue"], ["TFP예제/WikiPageGather"]
wiki:Wiki:DoTheSimplestThingThatCouldPossiblyWork
- The Tower of Hanoi . . . . 1 match
==== Recurrent Problems - The Tower of Hanoi ====
T<sub>n</sub> is the minimum number of moves that will transfer n disks from one peg to another under Lucas's rules.
===== mathematical expression =====
- TheJavaMan/스네이크바이트 . . . . 1 match
buff=createImage(getWidth(), getHeight());
gb.clearRect(0,0, getWidth(), getHeight());
TheJavaMan
- TheLargestSmallestBox/허준수 . . . . 1 match
[TheLargestSmallestBox]
- ThePragmaticProgrammer . . . . 1 match
SeeAlso : PPR:ThePragmaticProgrammer
- TheWarOfGenesis2R/ToDo . . . . 1 match
[TheWarOfGenesis2R]
- TheWarOfGenesis2R/일지 . . . . 1 match
[TheWarOfGenesis2R]
- ThinkRon . . . . 1 match
aka {{{~cpp WhatTheyWouldDoInMyShoes}}}
Let me tell a brief story about how that came about. Our president, at the time was Bob Doherty. Doherty came from General Electric via Yale, and had been one of the bright young men who were taken under the wing of the famous engineer Stiglitz. Every Saturday, Stiglitz would hold a session with these talented young men whom General Electric had recruited and who were trying to learn more advanced engineering theory and problem-solving techniques. Typically, Bob Doherty would sometimes get really stuck while working on a problem. On those occasions, he would walk down the hall, knock on Stiglitz’s door, talk to him — and by golly, after a few minutes or maybe a quarter of an hour, the problem would be solved.
One morning Doherty, on his way to Stiglitz’s office, said to himself, "Now what do we really talk about? What’s the nature of our conversation?" And his next thought was, "Well Stiglitz never says anything; he just asks me questions. And I don’t know the answer to the problem or I wouldn’t be down there; and yet after fifteen minutes I know the answer. So instead of continuing to Stiglitz’s office, he went to the nearest men’s room and sat down for a while and asked himself, "What questions would Stiglitz ask me about this?" And lo and behold, after ten minutes he had the answer to the problem and went down to Stiglitz’s office and proudly announced that he knew how to solve it.
- UglyNumbers/JuNe . . . . 1 match
print "The 1500'th ugly number is",ugly(1500)[-1]
- UglyNumbers/이동현 . . . . 1 match
System.out.println("The 1500'th ugly number is "+new BigDecimal(((Double)arr.get(0)).doubleValue()));// + " " + arr.size());
- ViImproved/설명서 . . . . 1 match
▶Vi 저자 vi와 ex는 The University of California, Berkeley California computer Science Division, Department of Electrical Engineering and Computer Science에서 개발
- WikiWikiWebFaq . . . . 1 match
'''A:''' A set of pages of information that are open and free for anyone to edit as they wish. The system creates cross-reference hyperlinks between pages automatically. See WikiWikiWeb for more info.
- ZeroPageHistory . . . . 1 match
* AOI, The Art Of Computer Programming
* C, C++, Java, Data Structure, Engineering Mathematics, ACM, 3D, Lucene, 영상처리
* OS, MIDI, Engineering Mathematics, AI, Algorithm, PHP, MySQL
- [Lovely]boy^_^/Diary/2-2-11 . . . . 1 match
* 선호랑 ["TheWarOfGenesis2R"]의 일환으로 타일 에디터를 만들었다. BMP 파일 약간 개조해서 뒤에다가 타일 데이터를 덧붙였다.
- eXtensibleMarkupLanguage . . . . 1 match
The Extensible Markup Language (XML) is a W3C-recommended general-purpose markup language for creating special-purpose markup languages, capable of describing many different kinds of data. In other words XML is a way of describing data and an XML file can contain the data too, as in a database. It is a simplified subset of Standard Generalized Markup Language (SGML). Its primary purpose is to facilitate the sharing of data across different systems, particularly systems connected via the Internet. Languages based on XML (for example, Geography Markup Language (GML), RDF/XML, RSS, Atom, MathML, XHTML, SVG, and MusicXML) are defined in a formal way, allowing programs to modify and validate documents in these languages without prior knowledge of their form.
- ljh131 . . . . 1 match
- 항상 마들만 사귀는 The O
- pragma . . . . 1 match
Each implementation of C and C++ supports some features unique to its host machine or operating system. Some programs, for instance, need to exercise precise control over the memory areas where data is placed or to control the way certain functions receive parameters. The #pragma directives offer a way for each compiler to offer machine- and operating-system-specific features while retaining overall compatibility with the C and C++ languages. Pragmas are machine- or operating-system-specific by definition, and are usually different for every compiler.
- 겨울과프로젝트 . . . . 1 match
= Theread =
- 데블스캠프2009/화요일 . . . . 1 match
|| 변형진 || The Abstractionism || 컴퓨터공학의 발전과 함께한 노가다의 지혜 || attachment:/DevilsCamp2009/Abstractionism.ppt ||
- 레밍딜레마 . . . . 1 match
* Title : 레밍 딜레마 ( The Lemming Dilemma )
- 문원명 . . . . 1 match
* [TheJavaMan]
- 박성현 . . . . 1 match
* [http://wiki.kldp.org/wiki.php/DocbookSgml/Ask-TRANS How To Ask Questions The Smart Way]
- 새싹교실/2011/學高/4회차 . . . . 1 match
* The sum of your integers plus 7 is 19
- 새싹교실/2011/앞반뒷반그리고App반 . . . . 1 match
* [The C Programming Language]. 일단은.
- 시간관리하기 . . . . 1 match
'''The Simplest Thing That Could Possibly Work'''
- 위시리스트 . . . . 1 match
* [http://books.google.co.kr/books?id=oowq_6bAgloC&printsec=frontcover&dq=go+lang&hl=ko&sa=X&ei=5f-WU8rTCM_-8QXu5oGwAw&redir_esc=y#v=onepage&q=go%20lang&f=false the way to go]
The art of computer programming 1 ~ 4A
- 정모/2004.1.20 . . . . 1 match
* TheJavaMan 모임 일요일 2시로 변경
- 정모/2004.2.3 . . . . 1 match
* TheJavaMan 은 프로젝트 참여자 전원이 참여하는 프로젝트인 비행기 게임 만들기를 새로 시작
- 졸업논문/요약본 . . . . 1 match
Web environment has became a standalone platform. Object-oriented languages, such as python, are suitable for web. Django is a web application framework written by python, and helps web developers writting web application more agile by abstracting database. Django provides high level abstraction on database, higher than CLI which uses ODBC. Django, for instance, creates database tables when developer writes classes in python, and modifies tables when developer modifies classes in python. In addition, django helps developers using database on host-language(python) level by abstracting insertion, deletion, update, retrieving of recodes to class method. Therefore, web developers make programs more agile.
- 지금그때2006/홍보 . . . . 1 match
Upload:NowThen2006ContactList.xls
- 최대공약수/허아영 . . . . 1 match
printf("The GCD of %d and %d is %d\n", x, y, x2);
- 컴퓨터고전스터디 . . . . 1 match
* 2004년 여름방학 현재 TheArtOfComputerProgramming으로 진행
- 프로그래밍은습관이다 . . . . 1 match
프로그래밍은 습관이다. 그래서 학습과 반(反)학습 모두 쉽지 않다. 특히 NoSmok:UnlearnTheLearned 가 어렵다. 세살 버릇 여든 가기에, 나쁜 프로그래밍 습관은 프로그래밍 언어가 바뀌어도 유지된다.
- 허아영 . . . . 1 match
[TheTrip/허아영]
Found 182 matching pages out of 7555 total pages (2100 pages are searched)
You can also click here to search title.
