text:
User:Cspurrier/monobook.css

.navpopup { background-color: #FFBE20 !important; font-family:     serif    !important; color:           #404     !important; font-size:       medium   !important; }

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: User:Cspurrier/monobook.css


text:
Reconstruction/Mold Treatment/Mold Test

'Mold Testing'
 * There are many methods to mold testing which enables detection in the air, on surfaces and in dust. Testing for mold in many cases is unnecessary. Simply identifying if mold is present is inexpensive and allows for more money for mold removal.

'Mold Identification Process'

 * Select an spot where the mold is boldly spotted, wall, cabinet, ceiling.
 * Check the color of the Mold, some colors represent different species, black, red, green.
 * Look at the texture to see if is lumpy, hard, grainy.
 * Mold should be also checked on diff growth surfaces, such as drywall room, and painted areas.
 * Make sure you use visible lighting area to spot mold.

title: Reconstruction/Mold Treatment/Mold Test


text:
C Sharp Programming/Keywords/partial

The special identifier is used to allow developers to build classes from different files and have the compiler generate one class, combining all the partial classes. This is mostly useful for separating classes into separate blocks. For example, Visual Studio 2005 separates the UI code for forms into a separate partial class that allows you to work on the business logic separately.

/Keywords

title: C Sharp Programming/Keywords/partial


text:
Talk:Beginning Mathematics/Algebra

Traditionally, arithmetic is described as using variables to solve equations, where a variable just represents some number. Algebra is traditionally regarded as the generalization and abstraction of such arithmetic, such as using those arithmetic operations on the complex numbers, or using "clock arithmetic" on the integers modulo some number.

The beginer has no idea what is meant here by groups!

title: Talk:Beginning Mathematics/Algebra


text:
File:Shortest applescript.png

Summary
a screenshot of a short applescript.

Licensing
/Images

title: File:Shortest applescript.png


text: Urdu/Vocabulary/Emergency

title: Urdu/Vocabulary/Emergency


text: Urdu/Vocabulary/Shopping

title: Urdu/Vocabulary/Shopping


text: Urdu/Vocabulary/Restaurant

title: Urdu/Vocabulary/Restaurant


text:
Reconstruction/Reconstruction/Door Instalation

'Materials/Tools'

 * measuring tape
 * pry bar
 * hammer
 * chisel
 * hammer
 * screwdrivers
 * drill, with drill bits and driver bits
 * utility knife
 * circular saw
 * hacksaw or reciprocating saw with metal-cutting blade
 * miter saw
 * wooden shims
 * caulk gun with butyl caulk
 * pre-hung door
 * exterior trim
 * weather stripping
 * safety glasses
 * work gloves


text: User talk:Fang Aili

title: User talk:Fang Aili


text:
Announcing/About this book

What is a Wikibook?
At the risk of stating the utterly obvious, let's begin with a simple definition: A wikibook is a book made with a wiki. Like most simple definitions, this one would benefit from some clarification, so let's break it down into three parts. A wikibook is:

 * 1) ...a book...  You are probably reading this on a computer screen right now, or perhaps a portable device like a tablet or "smart phone."  So it may not feel like you are reading a book, at least not a traditional one with paper pages that you turn as you read it.  But really, isn't a book much more than just paper and printer's ink?  Isn't the important part of a book—the reason why you read a book—contained in the book's message, and the meaning you derive from that message? So broadly defined, a book doesn't have to be a physical object you buy in a bookstore or borrow from a library.  Indeed, many books today are available in alternative formats, such as audiobooks and e-books.  Granted, the book you are reading now is presented differently than a traditional book.  But give it a chance.  You might find you like reading wikibooks.  You might even want to help write a wikibook someday.  Which brings us to the second part of the definition...
 * 2) ...made...  When we make something, we take things that already exist and combine them to fashion a new thing.  When we make a book, we take things that already exist in our heads—ideas, thoughts and concepts—and combine them in an organized, systematic way to create a new thing—a coherent, sustained message expressed in language.  That's pretty much what happens when we make a wikibook as well, but with at least two important differences.  First, a wikibook is an open collaborative effort.  That means that authorship is not fully embedded in one author, or even a group of identified authors.  Rather, a wikibook reflects the entire community of people who write, edit, discuss or otherwise contribute to the development of it.  Second, a wikibook is never really finished in the sense of a tradition book.  A wikibook remains continually available for anyone to add to, update and correct.  It is, by design, a "work in progress."  Both of these distinctive qualities of wikibooks are enabled by the technology used to create them, which brings us to the last part of the definition...[[Image:wikipedia-logo.png|thumb|right|With well over a million articles, [[w:|Wikipedia]] may be the world's largest encyclopedia.]]
 * 3)  ...with a wiki. A wiki is a kind of collaborative website.  That is, it is a website where multiple people can easily add to or change the content on the site.  Most wikis, including this one, are open, in the sense that anyone that visits the web site can participate in its development.  And most wikis, including this one, have content that can be freely used and redistributed, released to the public under the terms of some kind of "open source" licence such as the GNU Free Documentation License and the various Creative Commons Licenses.  In a sense, a wiki is a kind of social networking website, like Facebook and Twitter, but with more of a focus on the shared structuring and organizing of information. Perhaps the most famous wiki is Wikipedia, which bills itself as "the free encyclopedia that anyone can edit."  Wikipedia, as well as Wikibooks, the wiki you are now using, are projects of the Wikimedia Foundation.

The wikibook you are now reading could also be called a Wikibook, with a capital "W," because it is hosted on the Wikibooks wiki. Some might prefer to call it a "WikiBook," using the CamelCase style common to earlier wikis, or even a Wiki Book. But whatever you call it, it's still a book made with a wiki. And hopefully, it's a book you'll want to read...and perhaps help write.

How do I use this Wikibook?
This may seem like a silly question, since if you're reading this, you're already using this wikibook. But to get the most out of this wikibook, you should be aware of a few things:

 * 1) Navigation.   To help you "turn the pages" of this wikibook, some navigational aids are provided.  Near the top right corner of every page is a set of two links, one that links to the previous page and one that links to the next page.  Near the bottom of every page is another set of links, which includes the previous and next links, as well as a third link that takes you directly to the table of contents page.  There is also a link to the table of contents page near the top left corner of every page (just below the phrase "From Wikibooks, the open-content textbook collection."
 * 2) Links.  Many of the words in this wikibook are clickable links.  Some links take you to other pages in this book, and some links take you to other pages on this wiki that are not part of this book (like this link: Wikibooks).  Some links take you to pages on Wikipedia: for example, announcer takes you to the Wikipedia entry about announcers.  Some links take you to pages on other web sites; these have a small arrow symbol after the link.  And there are a few special purpose links, like the ISBN number links below, which take you to a page where you can search for that book online.  You don't have to follow every link, of course, but you might want to follow some to learn more about a topic.  Just remember that if a link takes you outside of this wikibook, you may need to use your browser's back button to return back to this wikibook.  Many browsers allow you to open links in a new window or tab, which can be a useful feature when reading a wikibook.
 * 3) Discussion.   Each page in this wikibook has a discussion page (also called a talk page).  If you want to make a comment about something on a page, here's where you can do it.  If you would like to make a suggestion, argue a point, offer a criticism or give a compliment, the talk page is the place to do so.  The talk page can also serve as a kind of "guestbook," where readers can "sign" their names (using three or four tilde characters). And the talk pages can be a tool for courses that use this wikibook as a textbook.  For example, instructors could post activities related to the wikibook on the talk pages.  They could also include quiz or discussion questions that can help students review the material.
 * 4) Editing.   If you find a typo in this book, please feel free to fix it!  You can edit every page in this book, simply by clicking the "edit this page" tab near the top of the book.  This will open the entire page in an editing window where you can make changes.  At the bottom of that window are buttons to "save page" (to save your changes), "show preview" (to show you what your changes will look like without saving) and "show changes" (to show you a comparison of the original version with your edited one).  The editing window also has a tool bar above it to help you do things like add bold or italic text, as well as add links to other pages or other web sites.  You can even add pictures and sound files, although if you do so, please make sure they don't violate the terms of the Wikibooks license.  Tip: because it's often easier to edit just a section of a page, each section of each page has its own "edit" link near the right edge of the top of each section.  In most cases, it's a lot easier to correct a typo or make a quick edit by clicking on a section's edit link than to open the entire page in the editing window.

Why a Wikibook on Announcing?
That's a good question. After all, as of August 2011, there are at least three well-established textbooks on announcing published by the major textbook publishers:

 * 1) Television and Radio Announcing (11th edition), by Stuart W. Hyde ISBN 020556304X.  The 11th edition of this text was published by Allyn & Bacon in 2008. Hyde's book is a classic, and has been used in broadcast performance courses for decades; his first edition was published in 1959.
 * 2) Announcing : Broadcast Communication Today (5th edition), by Carl Hausman, Philip Benoit, Frank Messere and Lewis B. O'Donnell ISBN 0534563104.  The 5th edition of this text was published by Wadsworth in 2004.  This book has also been around a long time; the first edition was published in 1987.
 * 3) Broadcast Announcing Worktext: Performing for Radio, Television, and Cable (3rd edition) by Alan R. Stephenson, David E. Reese and Mary Beadle ISBN 0240810589.  The 3rd edition of this text was published by Focal Press in 2009.  It is a relatively recent addition to the literature on announcing; its first edition was published in 2000.

There are also books related to specific announcing skills and specializations. For example, Broadcast Voice Handbook (4th edition) by Ann S. Utterback and Michael G. Freedman ISBN 1566252725 provides an in-depth examination of voice development for broadcasters. Another notable book, and a fun read, is How to Make a Million Dollars With Your Voice (or Lose Your Tonsils Trying) by Gary Owens and Jeff Lenburg ISBN 0071424105.

All of these are fine books, and each has its unique strengths. But none of them have four qualities that this wikibook has:

 * 1) This book is free.
 * 2) This book can include hyperlinks.
 * 3) This book can be updated continuously.
 * 4) This book can include contributions by anyone.

Now the first point is hard to quibble with. It's hard to beat free. The second point is also a big advantage of a wikibook, since you can embed in the text itself links to other web pages, including other wikibooks and entries in other wikis (like Wikipedia entries). The third advantage can be a bit iffy, as a wikibook is only as good as the community of contributors who help keep it current. There's no guarantee that this wikibook will stay current, of course, but the more people that get involved, the more likely it is that at least some of them will stick with it and keep the text fresh and current...at least until the "next generation" of contributors take over.

But this last point may seem like a disadvantage to some people. After all, shouldn't textbooks be written by experts? If you let anyone contribute to a book, doesn't that make it less credible? Maybe, but maybe not. You see, while it is true that wikibooks (and wikis in general) can and do suffer from occasional "vandalism," it's not something that can't be fixed. Any edit can be reversed. Any contribution can be removed. And every version of every page can be seen by anyone. Just click on the "View History" tab at the top of each page, and you'll see a list of every version of that page. This list also shows when each version was submitted, and by whom—either identified by their registered username, or by their IP address if they prefer to edit anonymously (or just forget to log in). If you like, you can even compare different versions to see what was changed.

So while the fact that anyone can contribute to this wikibook may seem like a disadvantage, it's actually one of its greatest strengths. (Maybe not as great as the fact that it's free, but close). Because when you let anyone help write a book, the people who are most likely to contribute, and the people who are most likely to prevail in an "edit war" are the people who care the most about the book and its content. The community of writers and readers serve as a built-in review system. It isn't a perfect system, but it's a pretty good one. And if you don't agree, you are free to edit this page right now and change it. And if you do, anyone is free to change it back.

What is the purpose of this Wikibook?
The fundamental purpose of this wikibook is to provide a free, open-content textbook on announcing. In particular, it is hoped that this wikibook will be a valuable resource for those who seek to become announcers, or who seek to improve their announcing skills.

Another purpose is to serve as a textbook for a course taught by Philip A. Thompsen, Ph.D. at West Chester University. I'm going to revert to writing in first person just to make this clearer, and to keep from writing about "Dr. Thompsen" when...well, that's me. (In general, writing in first person is not good Wiki etiquette, but perhaps the reader will grant me some grace to make a point in this section.) I've been teaching broadcast performance courses for many years, and at many different universities. I've used all three of the textbooks I mentioned above in past semesters. They are all fine books. And they are all expensive books (although the Focal book is the most reasonably priced). None of them are perfect. None cover everything I want in a textbook for my course. So back in 2006, when I was faced with the decision as to what book to adopt for my course that fall, I couldn't decide. I didn't really want to use any of them. I wanted to write my own textbook.

And then in July 2006, I taught a graduate course on communication technology where the students and I worked together on building a wiki about communication. We called it ComWiki: The Communication Studies Wiki. It was a small class, but in just a few weeks of work, we built a pretty decent little wiki, with over a hundred articles. Not amazing, perhaps, but certainly a good start to what could potentially become a more active wiki in the future.

This experience peaked my interest in attending a conference on wikis called Wikimania 2006. It was a great conference, and I got to see firsthand what others were doing with wiki technology. And after spending three days listening to the people behind much of Wikipedia and the other Wikimedia projects, I was hooked. I had already contributed quite a bit to Wikipedia, and I had started my own wiki, but now I wanted to do more. I wanted to write a wikibook. So that's what I'm doing.

I don't know what the "finished product" will look like, or even if it will ever be considered finished enough to warrant a printable version (like some of the other wikibooks on this wiki). This is a wikibook, after all, so it will always be a work in progress. But if my effort to get this wikibook started helps just a few people learn about a profession I once called my own (and still do to some extent), then I think the effort will be worth it.

How can I contribute to this Wikibook?
That's easy. Click on the "edit this page" tab at the top of any page and add, change, correct, delete or update as much (or as little) as you like. You don't even have to be a registered user to do so. But if you are going to be making some major contributions, it would be nice to know at least a little bit about you. Please consider registering for an account if you don't already have one, and log in as that user when you edit so that everyone can see what you did. No need to be bashful.

Comments and suggestions are also welcome. If you have something you would like to say about something in this wikibook, consider posting a comment. Every page has its own "talk page," a place to discuss what's on the module page. Just click on the discussion tab at the top of any page to see what, if anything, has been added to the talk page. To add something to the discussion, just click the "+" tab that appears near the top of the talk page. If you are logged in, and would like to sign your comment, you can do so easily by putting three tilde characters (~) after what you've written (or four tilde characters if you also want to include a time stamp).

By the way, this use of tilde characters to add your signature is an example of using wikitext. It's easy to learn, but you don't need to know it to contribute. Still, if you want to learn just a little wikitext, a good place to start is with the w:Wikipedia:Quick Guide.

Also consider adding your name to the contributors section below.

Who is contributing to this Wikibook?
This Wikibook was started on August 13, 2006, by Philip A. Thompsen, Ph.D. Dr. Thompsen has taught broadcast performance classes at the university level for over two decades. Prior to his academic career, he worked as a professional broadcast announcer. You can read more about him at his user profile page.

If you contribute to this wikibook, please consider adding a brief biographic sketch on the contributors page.

It is hoped that over time, a growing number of professional announcers will contribute to the development of this wikibook. If you are reading this, and would like to help but don't know where to start, please look at this list of wanted modules.

title: Announcing/About this book


text:
Talk:Announcing

Here's where you can add your comments and suggestions about the Table of Contents for this Wikibook. Anyone is welcome to join the discussion! Just click the "+" tab above to add your comment. If you like, you can also sign your comments by putting three or four tilde characters (~) at the bottom of your comment.

Please note that every page in this Wikibook has a discussion section (commonly called a "talk page"). While you're welcome to post a comment here, if your comment relates to a specific section, it may be more helpful to post your comment on that section's talk page.

Return to the Table of Contents

Pthompsen 19:53, 14 August 2006 (UTC)

title: Talk:Announcing


text:
User:Dylanwhs~enwikibooks

Dylan Sung

Hi my name is Dylan, and I use fortran77 to program. I've used it to output HTML code which appears in my websites here and here. I'm a meat eater and grow vegetables too.

I shall be adding to some of the books here soon. Dylanwhs 20:48, 26 August 2006 (UTC)

title: User:Dylanwhs~enwikibooks


text:
Practical Electronics/ICs

Integrated Circuits, also called ICs or informally, "microchips" or just "chips", are miniature electronic circuits built onto a single (very small) piece of silicon embedded in a package that allows it to be connected to a circuit. They can fulfill many functions, ranging from simple logic gates and other simple devices such as counters and shift registers, to computer processors.

Any device built on a single "chip" of silicon is said to be "monolithic", from the Greek for "single stone".

Advantages of ICs
When ICs were introduced, they represented a revolutionary paradigm shift in the construction of electronic device. Rather than everything having to be made from basic components, certain standard modules could be plugged in in the form of a "microchip".

This reduces cost (a simple IC of the kind used in this Wikibook costs between 10p and £1), as opposed to the equivalent cost of potentially upwards of tens, or more likely, hundreds, of discrete components.

Also, as the devices are highly miniaturised, they take up less space, use less power, and operate faster with less noise, due to the components inside being very close together.

Modern ICs can fit up to 1,000,000 transistors onto a piece of silicon with an area of 1mm².

Form of an IC
All ICs have the same basic parts. At the heart of the IC is the die. This is the piece of silicon that the circuit is built on. It is generally smaller than 1mm on a side and is usually located in the geometric centre of the device.

The die is connected by fine wires (generally 20μm or thinner) to the pins. Pins are metal protrusions that are used to make contact with the outside circuitry. Pins usually take to form of the "legs" seen sticking out from the sides on most common microchips. Pins can also be vertical pins or tiny solder balls on the bottom surface of the IC.

The dies and the pins are set into the carrier. This is the body of the IC and is generally made of plastic or ceramic. To orientate the device, a notch, dot, or cut-off corner is usually included on the carrier.

For more information on IC package designs, see "Practical Electronics Packages" and "Howto identify integrated circuit(IC) chip packages".

Scales of Integration
The number of transistors in an IC determines the scale of integration of the IC. The higher the scale, the more complex the IC. The table below shows a rough outline of the division between scales. Bear in mind that there is no hard-and-fast rule governing the naming of the scales, and as semiconductor technology grows, the number of transistors seen as "very large" today will seem small.

Logic families
The layout of the components in ICs has changed dramatically since ICs were first introduced. As more modern processes have allowed smaller and more precise components to be etched in the die, different kinds of electronics could be used, resulting in continuously changing and improving performance from the ICs. Below is a very brief summary of the main IC families. For more information on the specifics of each family, visit the linked pages.

The earliest ICs used resistors and transistors, in a form called resistor-transistor logic (RTL). This was very prone to noise with more than three inputs, and as such was only suitable for very small-scale devices.

Next came diode-transistor logic (DTL). This used diodes to supplement the resistors used in RTL, but still suffered many problems, including a very long propagation delay (the time taken to change state).

Transistor-transistor logic (TTL) was a very popular format for ICs and is still in use in places today. This basically uses only transistors to fulfil its function.

Most ICs today are CMOS which have a very low quiescent current usage, high noise immunity, and flexible voltage supply requirements.

Other families include Emitter-coupled logic (ECL) and Integrated Injection logic (I2L).

title: Practical Electronics/ICs


text:
Talk:Haskell/Type declarations

tuples and types
Up to this point, the reader has encountered tuples and some basic motivation for types. Seems like we need to make the connection between tuples and what we're doing here, something along the lines of "well, you already know how to make your own types; just combine things with lists and tuples; but it's still not very convenient... sometimes you want to name a type; and sometimes you have two things that look like they're the same, but for some reason or another, you want to enforce that they are of different types." We could start off with type synonyms, actually, just make synonyms for tuples... and eventually discover that it's not quite good enough. Then data... and then flip back and point out that synonyms can also be used on data. -- Kowey 03:15, 30 December 2006 (UTC)

 * This was the first section that I don't feel very comfortable with. Your comment helped actually. I didn't start to realize the possible usefulness of creating your own Types until I was well into the section. I am also a little confused by constructor functions. I see now how they can be used but I feel like I'm missing the bigger picture or the logic behind some of the syntax.--Jberryman (talk) 02:15, 4 March 2008 (UTC)

 * In the spirit of these commentaries I wrote a brief introduction. Ideally it should be a natural follow-up to the introduction of Haskell/Type basics - I even considered referring directly to the phone book example, but it would get too verbose. Also, it is maybe a little too abstract... The ideal approach would likely be a didactic step-by-step example as Kowey suggested above, but given my lack of Haskell experience I didn't feel compelled to try pulling that off.

 * By the way, I believe it would be good to swap this sub-chapter with the Simple IO one. Not only because this topic is a natural continuation of Type basics, but also because having this comparatively short section at the end of the chapter and placed after the long and conceptually tricky introduction to actions makes it easy for readers to miss the point due to lack of context. --Duplode (talk) 05:50, 29 April 2010 (UTC)

 * Concerning the oder of chapters, I'm not sure whether it's a good idea to put the Simple IO after the type declarations. How about the following:
 * At the moment, the wikibook is still kinda messy. In particular, the structure behind the division of the beginner's track into four separate parts is not clear (except for the monads, those are clear). Ideally, however, I envision the following structure:
 * Part 1 - "Minimal Haskell", enables the reader to write Haskell programs, in the sense that he can encode any functionality he dreams of in Haskell, albeit restricted to a subset of the syntax.
 * Part 2 - "Elementary Haskell", enables the reader to read most Haskell programs and write better ones.
 * Part 3 - "Haskell with Class", enables the reader to write Haskell libraries, using modules, type classes and so on.
 * Part 4 - Monads

 * From this, it follows that the type declarations should go into part 2 and only type synonyms should be mentioned in part 1. Simple IO has to stay in part 1, though, because it's clearly required for doing IO stuff.
 * -- apfeλmus 14:01, 3 May 2010 (UTC)

CFG looking types
I was just wondering why this doesn't work: data BalancedParen = OpenParen CloseParen | OpenParen BalancedParen CloseParen | BalancedParen BalancedParen it gives: $ ghci ___        ___ _  / _ \ /\  /\/ __(_) / /_\// /_/ / /  | |      GHC Interactive, version 6.4.2, for Haskell 98. / /_\\/ __ / /___| |      http://www.haskell.org/ghc/ \____/\/ /_/\____/|_|     Type :? for help.

Loading package base-1.0 ... linking ... done. Prelude> :l varfun.hs Compiling Main            ( varfun.hs, interpreted )

varfun.hs:1:46: Multiple declarations of `Main.OpenParen' Declared at: varfun.hs:1:22 varfun.hs:1:46 Failed, modules loaded: none. Prelude>

I also tried this text in varfun.hs: data Palindrome = A Palindrome A | B Palindrome B | A | B | A A | B B It gave: $ ghci ___        ___ _  / _ \ /\  /\/ __(_) / /_\// /_/ / /  | |      GHC Interactive, version 6.4.2, for Haskell 98. / /_\\/ __ / /___| |      http://www.haskell.org/ghc/ \____/\/ /_/\____/|_|     Type :? for help.

Loading package base-1.0 ... linking ... done. Prelude> :l varfun.hs Compiling Main            ( varfun.hs, interpreted )

varfun.hs:1:60: Multiple declarations of `Main.A'   Declared at: varfun.hs:1:52 varfun.hs:1:60

varfun.hs:1:60: Multiple declarations of `Main.A'   Declared at: varfun.hs:1:18 varfun.hs:1:60

varfun.hs:1:66: Multiple declarations of `Main.B'   Declared at: varfun.hs:1:56 varfun.hs:1:66

varfun.hs:1:66: Multiple declarations of `Main.B'   Declared at: varfun.hs:1:35 varfun.hs:1:66 Failed, modules loaded: none. Prelude>

Answer
Well, one thing is as the compiler complains: you can't have multiple declarations of the same type using the same constructor, so this is bad: data MyWonderfulType = Bar Int | Bar Char -- bad: too many Bars Whereas this is ok data MyWonderfulType = Foo Int | Bar Char

Note incidentally that this too is bad... data MyNiceType = Foo data MyOtherType = Foo -- too many Foos

The basic intuition for this is that when you say  in some piece of code, not the type declaration itself, but simply trying to use , you want the Haskell compiler to know what you're talking about. In the case above, we have an ambiguity... was that a  you wanted or a  ?

The other issue is simply a question of syntax, in that a type declaration looks like this... data MyType = Constructor TypeArg1 TypeArg2 ... TypeArgN where TypeArg1..TypeArgN are themselves types. (Incidentally, it's ok if the constructor and the type have the same name)

The implications being that a type like the below...

data Palindrome = A Palindrome A

You've got a constructor, followed by arguments   and. That's all well and good, except that
 * 1) It's probably not what you had in mind
 * 2) ... The type   isn't defined anywhere else in your code

Here's something which would probably work better

data A = A data B = B data Palindrome = P1 A Palindrome A | P2 B Palindrome B | P3 A A

Note how I give a constructor (P1...P3) for each alternative in the CFG, and that each constructor is different (can't have multiple declarations, remember? Now, you might be tempted to do something like this... -- not going to work data Alphabet = A | B | C data Palindrome = P1 A Palindrome A | P2 B Palindrome B | P3 A A

Because what comes after the constructor has to be a type, whereas,  in this case, is NOT a type (  is a type, as is  ). You could try something like this: data Alphabet = A | B | C data Palindrome = P1 Alphabet Palindrome Alphabet | P3 Alphabet Alphabet

But then we'd no longer be dealing with a CFG, would we?

Hope this helps. For more questions, please try the haskell mailing list (or perhaps haskell-cafe), or the #haskell IRC channel on irc.freenode.net -- Kowey 06:57, 15 August 2006 (UTC)

Error
johnSmith = Birthday { name = "John Smith", date = Date 7 3 1986}'

name and date are not in scope here (unless i missed something) -- should they read anniName and anniDate? 82.70.93.66 13:32, 2 September 2006 (UTC)

 * Fixed, thanks. -- Kowey 20:33, 2 September 2006 (UTC)

newtype
data X = Y Char newtype X' = Y' Char

X' has 257 possible values while X has 258.

showAnniversary
showAnniversary didn't work the way the text is implying it should have (I think). I got the impression it should somehow magically tie in with show, so you could just type. But instead you have to type showAnniversary smithWedding. I find this chapter a tad confusing.... 24.65.49.167 (talk) 04:36, 20 March 2008 (UTC) (aka user:Bawolff)

 * Well, you absolutely could. Just add a deriving (Show) clause to the data declaration, and it'll work like you expect.
 * But the problem is, that requires two advanced ideas: typeclasses, and instance derivation. And I'm pretty sure those topics don't get covered for a while yet. Having the reader work through things the hard way serves the useful purpose of demonstrating the drudgery we can automate and abstract away later. --Gwern (contribs)
 * As a C/C++ programmer trying to learn elementary Haskell, I have to agree with the original poster. Just because it's too early to teach classes and derivation in general doesn't mean you can't use them in this case to aid this tutorial. K&R doesn't have a problem with showing how to print literal text with printf even though the concepts of how to really take advantage of or write your own printf-style function don't come until much later. At the very least, mentioning this issue and giving a pointer toward the later subject that provides the solution would be useful. 24.4.188.251 (talk) 06:50, 9 April 2008 (UTC)
 * It's not exactly relevant to answer messages from two years ago, but I felt like commenting anyway. I would rather strongly disagree with the "C/C++ programmer" above in that I can't see how mentioning deriving (Show) at this very early stage could aid the tutorial. One of the key roles of this module is introducing constructor functions in an easy to understand way for an absolute newbie - and, as far as that purpose is concerned, the less distracting syntactic sugar and advanced functionality the better. In fact, I would even consider moving the discussion about type synonyms to some other place... --Duplode (talk) 06:35, 2 May 2010 (UTC)

Additional exercise...
I think the following exercise would be good to be added:

Define the following

I could add it by myself, but I am not really sure about the proper answers. My guess would be:

 * 1) The values True and False are already bound to the data structure  . Therefore a second bind of the same (True resp. False) lets the compiler question which True it should take, either from the Prelude or the newly defined.
 * 2) no real clue
 * 3) I think it could look like   or   . But to be honest, I have no clue, what the difference between the two definition is.

 * A year and a half later... (sorry, this page was missing from my watchlist.)

 * 1. Yup, that's it.

 * 2 and 3. You have a few options:
 * (define a wholly new data type using different names for the constructors from the ones in the Prelude) and then ;
 * (define a type synonym, which is exactly equivalent to  except in name) and then  ; and
 * (define a new data type which is merely a wrapper for ) and then  . Incidentally, that is a case in which you normally would use   in real code. That might look like
 * I suspect you originally had the first option in mind for your test.

 * Duplode (discuss • contribs) 15:00, 13 July 2015 (UTC)

title: Talk:Haskell/Type declarations


text:
Talk:Basic Book Design

Merging chapter sections?
What does everyone think about merging sections of each chapter together? Each section seems too short to me right now. --hagindaz 22:12, 14 August 2006 (UTC)

PDF version vs wikimarkup version
The PDF version of this document seems to be fairly poorly typeset, which is kind of ironic for a book on book design. It also contains sections whose pages linked from the main module don't seem to exist anymore. Why is the former true, and how did the latter inconsistencies come to exist? --Drake Wilson 03:41, 1 October 2006 (UTC)

 * Concur, came here because of many errors in the PDF, was looking to attempt edits, found TOC, and... just about done looking to try to fix things.

The Chicago Manual Of Style
The text seems to constantly refer to The Chicago Manual Of Style which is worrying. Is the author around to verify that this book hasn't just been cribbed from The Chicago Manual Of Style. Is there anyway to check that there isn't a copyvio. -Axon 18:03, 17 October 2006 (UTC)

 * References to books aren't copyright violations. The wiki websites generally encourage referencing articles.--Thomas David Kehoe 18:56, 17 October 2006 (UTC)

 * That isn't what I asked: references aren't copyvio, but the content of the book bears close resemblance to the content of The Chicago Manual Of Style, both dealing with written style. How exactly did you go about writing this? Did you crib at all from the Chicago Manual of Style? If so, by how much? For example, you sentence here:
 * Question marks and exclamation marks go inside or outside quotations, depending on whether the quoted text used the punctuation mark.
 * Bears close resemblance to this sentence :
 * Question marks and exclamation marks go inside or outside quotation marks, depending on their use in the sentence.
 * Similarly, a google for your sentence "always put periods and commas inside quotation marks" returns quiet a few hits. How do you explain this? -Axon 09:37, 18 October 2006 (UTC)

Change title to Book Design?
Can we change the title from Basic Book Design to Book Design? The latter fits in the style of naming other wikibooks by their subject matter only.--Thomas David Kehoe 19:04, 17 October 2006 (UTC)

Heading Case
This book uses title case in its headings, in preference over sentence case, all caps, and small caps. --Dan Polansky (talk) 10:23, 9 June 2008 (UTC)

title: Talk:Basic Book Design


text: Java Programming/Applets

title: Java Programming/Applets


text:
Physics Study Guide/Normal Force and Friction

The Normal Force
Why is it that we stay steady in our chairs when we sit down? According to the first law of motion, if an object is translationally in equilibrium (velocity is constant), the sum of all the forces acting on the object must be equal to zero. For a person sitting on a chair, it can thus be postulated that a normal force is present balancing the gravitational force that pulls the sitting person down. However, it should be noted that only some of the normal force can cancel the other forces to zero like in the case of a sitting person. In Physics, the term normal as a modifier of the force implies that this force is acting perpendicular to the surface at the point of contact of the two objects in question. Imagine a person leaning on a vertical wall. Since the person does not stumble or fall, he/she must be in equilibrium. Thus, the component of his/her weight along the horizontal is balanced or countered (opposite direction) by an equal amount of force -- this force is the normal force on the wall. So, on a slope, the normal force would not point upwards as on a horizontal surface but rather perpendicular to the slope surface.

The normal force can be provided by any one of the four fundamental forces, but is typically provided by electromagnetism since microscopically, it is the repulsion of electrons that enables interaction between surfaces of matter. There is no easy way to calculate the normal force, other than by assuming first that there is a normal force acting on a body in contact with a surface (direction perpendicular to the surface). If the object is not accelerating (for the case of uniform circular motion, the object is accelerating) then somehow, the magnitude of the normal force can be solved. In most cases, the magnitude of the normal force can be solved together with other unknowns in a given problem.

Sometimes, the problem does not warrant the knowledge of the normal force(s). It is in this regard that other formalisms (e.g. Lagrange method of undetermined coefficients) can be used to eventually solve the physical problem.

Friction
When there is relative motion between two surfaces, there is a resistance to the motion. This force is called friction. Friction is the reason why people may have trouble accepting Newton's first law of Motion, that an object tends to keep its state of motion. Friction acts opposite to the direction of the original force The frictional force is equal to the frictional coefficient times the normal force

In order to set a body into a state of motion, the forward force or the thrust force exerted upon the body must be greater in magnitude than the maximum frictional value encountered upon the surface with which the body is in contact with. If the thrust force does not exceed in magnitude over the maximum frictional value or limiting value of motion then the body shall not be set into motion.

Friction is caused due to attractive forces between the molecules near the surfaces of the objects. If two steel plates are made really flat and polished and cleaned and made to touch in a vacuum, it bonds together. It would look as if the steel was just one piece.The bonds are formed as in a normal steel piece. This is called cold welding. And this is the main cause of friction.

The above equation is an empirical one — in general, the frictional coefficient is not constant. However, for a large variety of contact surfaces, there is a well characterized value. This kind of friction is called Coulomb friction. There is a separate coefficient for both static and kinetic friction. This is because once an object is pushed on, it will suddenly jerk once you apply enough force and it begins to move.

Also, the frictional coefficient varies greatly depending on what two substances are in contact, and the temperature and smoothness of the two substances. For example, the frictional coefficients of glass on glass are very high. When you have similar materials, in most cases you don't have Coulomb friction.

For static friction, the force of friction actually increases proportionally to the force applied, keeping the body immobile. Once, however, the force exceeds the maximum frictional force, the body will begin to move. The maximum frictional force is calculated as follows:

The static frictional force is less than or equal to the coefficient of static friction times the normal force. Once the frictional force equals the coefficient of static friction times the normal force, the object will break away and begin to move.

Once it is moving, the frictional force then obeys:

The kinetic frictional force is equal to the coefficient of kinetic friction times the normal force. As stated before, this always opposes the direction of motion.

Variables
Definition of Terms

It's important to note that in real life we often have to deal with viscous and turbulent friction - they appear when you move the body through the matter.

Viscous friction is proportional to velocity and takes place at approximately low speeds. Turbulent friction is proportional to $$V^2$$ and takes place at higher velocities.


text:
Physics Study Guide/Print version

Newton's First law of motion :a Body remain at rest or continue moving at a constant velocity unless an unbalanced force acts on it

Newton's second law of motion :when an unbalanced force acts on an object ,the object will accelerate the direction of the net force ,Acceleration is directly proportional to the net force and inversely proportional to the mass of the object

=Section Two=

=Section Three=

=Appendices=

= GNU Free Documentation License =

title: Physics Study Guide/Print version


text:
Wikijunior:United States Charters of Freedom/Federalist Papers

The Federalist Papers are a series of 85 articles arguing for the ratification of the United States Constitution. They were first published serially from October 1787 to August 1788 in New York City newspapers. A compilation, called The Federalist, was published in 1788. The Federalist Papers serve as a primary source for interpretation of the ../Constitution/, as they outline the philosophy and motivation of the proposed system of government. The authors of the Federalist Papers were not above using the opportunity to provide their own "spin" on certain provisions of the constitution to (i) influence the vote on ratification and (ii) influence future interpretations of the provisions in question.

The articles were written by James Madison, Alexander Hamilton, and John Jay, under the pseudonym "Publius," in honor of Roman consul Publius Valerius Publicola. Madison is generally credited as the father of the Constitution and became the fourth President of the United States. Hamilton was an influential delegate at the Constitutional Convention, and later the first Secretary of the Treasury. John Jay would become the first Chief Justice of the United States. Hamilton penned the majority and Madison made several significant contributions to the series. Jay, who fell ill early in the project, wrote only five.

Federalist No. 10 and Federalist No. 51 are generally regarded as the most influential of the 85 articles; 10 advocates for a large, strong republic and includes discussion on factions, 51 explains the need for separation of powers. Federalist No. 84 is also notable for its opposition to what later became the ../Bill of Rights/.

Origins
The ../Constitution/ was sent to the states for ratification in late September 1787. Immediately, it was the target of a substantial number of articles and public letters written by Anti-Federalists and other opponents of the Constitution. For instance, the important Anti-Federalist authors "Cato" and "Brutus" debuted in New York papers on September 27 and October 18, respectively. Hamilton began the Federalist Papers project as a response to the opponents of ratification, a response that would explain the new Constitution to the residents of New York and persuade them to ratify it. He wrote in Federalist No. 1 that the series would "endeavor to give a satisfactory answer to all the objections which shall have made their appearance, that may seem to have any claim to your attention."

Hamilton recruited collaborators for the project. He enlisted Jay, who fell ill and was unable to contribute much to the series. Madison, in New York as a delegate to the Congress, was recruited by Hamilton and Jay and became Hamilton's major collaborator.

Hamilton also chose "Publius" as the pseudonym under which the series would be written. While many other pieces representing both sides of the constitutional debate were written under Roman names, Albert Furtwangler contends that "'Publius' was a cut above 'Caesar' or 'Brutus' or even 'Cato.' Publius Valerius was not a late defender of the republic but one of its founders. His more famous name, Publicola, meant 'friend of the people.'" It was not the first time Hamilton had used this pseudonym: in 1778, he had applied it to three letters attacking Samuel Chase, an Associate Justice of the United States Supreme Court.

Publication
The Federalist Papers initially appeared in three New York newspapers: the Independent Journal, the New-York Packet and the Daily Advertiser, beginning on October 27, 1787. Between them, Hamilton, Madison and Jay kept up a rapid pace, with at times three or four new essays by Publius appearing in the papers in a week. Hamilton also encouraged the reprinting of the essay in newspapers outside New York state, and indeed they were published in a number of other states where the ratification debate was taking place.

The high demand for the essays led to their publication in a more permanent form. On January 1, 1788, the New York publishing firm J. & A. McLean announced that they would publish the first thirty-six essays as a bound volume; that volume was released on March 2 and was titled The Federalist. (Its title page appears at the top right of the article.) New essays continued to appear in the newspapers; Federalist No. 77 was the last number to first appear in that form, on April 2. A second bound volume containing the last forty-nine essays was released on May 28. The remaining eight papers were later published in the newspapers as well.

A number of later publications are worth noting. A 1792 French edition ended the collective anonymity of Publius, announcing that the work had been written by "MM Hamilton, Maddisson E Gay," citizens of the State of New York. In 1802 George Hopkins published an American edition that similarly named the authors. Hopkins wished as well that "the name of the writer should be prefixed to each number," but at this point Hamilton insisted that this was not to be, and the division of the essays between the three authors remained a secret.

The first publication to divide the papers in such a way was an 1810 edition that used a list provided by Hamilton to associate the authors with their numbers; this edition appeared as two volumes of the compiled "Works of Hamilton." In 1818, Jacob Gideon published a new edition with a new listing of authors, based on a list provided by Madison. The difference between Hamilton's list and Madison's form the basis for a dispute over the authorship of a dozen of the essays.

The disputed essays
The authorship of seventy-three of the Federalist essays is fairly certain. Twelve are disputed, though some newer evidence suggests Madison as the author. The first open designation of which essay belonged to whom was provided by Hamilton provided his lawyer with a list detailing the author of each number. This list credited Hamilton with a full sixty-three of the essays (three of those being jointly written with Madison), almost three quarters of the whole, and was used as the basis for an 1810 printing that was the first to make specific attribution for the essays.

Madison did not immediately dispute Hamilton's list, but provided his own list for the 1818 Gideon edition of The Federalist. Madison claimed twenty-nine numbers for himself, and he suggested that the difference between the two lists was "owing doubtless to the hurry in which [Hamilton's] memorandum was made out." A known error in Hamilton's list—Hamilton incorrectly ascribed No. 54 to Jay, when in fact Jay wrote No. 64—has provided some evidence for Madison's suggestion.

Statistical analysis has been undertaken a number of times to try to decide based on word frequencies and writing styles, and nearly all of the statistical studies show that all twelve disputed papers were written by Madison.

Structure and form
In Federalist No. 1, which served as the introduction to the series, Hamilton listed six topics to be covered in the subsequent articles:

 * 1) "The utility of the UNION to your political prosperity" – covered in No. 2 through No. 14
 * 2) "The insufficiency of the present Confederation to preserve that Union"—covered in No. 15 through No. 22
 * 3) "The necessity of a government at least equally energetic with the one proposed to the attainment of this object"—covered in No. 23 through No. 36
 * 4) "The conformity of the proposed constitution to the true principles of republican government"—covered in No. 37 through No. 84
 * 5) "Its analogy to your own state constitution"—covered in No. 85
 * 6) "The additional security which its adoption will afford to the preservation of that species of government, to liberty and to prosperity"—covered in No. 85.

Furtwangler notes that as the series grew, this plan was somewhat changed. The fourth topic expanded into detailed coverage of the individual articles of the Constitution and the institutions it mandated, while the two last topics were merely touched on in the last essay.

Judicial use and interpretation
Federal judges frequently use the Federalist Papers when interpreting the ../Constitution/ as a contemporary account of the intentions of the framers and ratifiers. However, the amount of deference that should be given to the Federalist Papers in constitutional interpretation has always been somewhat controversial. As early as 1819, Chief Justice John Marshall said about the Federalist Papers that "the opinions expressed by the authors of that work have been justly supposed to be entitled to great respect in expounding the Constitution. No tribute can be paid to them which exceeds their merit; but in applying their opinions to the cases which may arise in the progress of our government, a right to judge of their correctness must be retained."

Opposition to the Bill of Rights
The Federalist Papers (specifically Federalist No. 84) are remarkable for their opposition to what later became the ../Bill of Rights/. The idea of adding a bill of rights to the constitution was originally controversial because the constitution, as written, did not specifically enumerate or protect the rights of the people. Alexander Hamilton, in Federalist No. 84, feared that such an enumeration, once written down explicitly, would later be interpreted as a list of the only rights that people had.

However, Hamilton's opposition to the Bill of Rights was far from universal. Brutus, articulated this view point in the so-called Anti-Federalist No. 84, asserting that a government unrestrained by such a bill could easily devolve into tyranny. Other supporters of the Bill argued that a list of rights would not and should not be interpreted as exhaustive; i.e., that these rights were examples of important rights that people had, but that people had other rights as well. People in this school of thought were confident that the judiciary would interpret these rights in an expansive fashion.

List of Federalist Papers
Here is a list of the Federalist Papers:

Text of Federalist Papers
For the text of the Federalist Papers, see the following subpages:
 * 1) /Federalist No. 1-10/
 * 2) /Federalist No. 11-20/
 * 3) /Federalist No. 21-30/
 * 4) /Federalist No. 31-40/
 * 5) /Federalist No. 41-50/
 * 6) /Federalist No. 51-60/
 * 7) /Federalist No. 61-70/
 * 8) /Federalist No. 71-80/
 * 9) /Federalist No. 81-85/

Source
Basically a junior version of the Wikipedia article


text:
Talk:French/Grammar/Tenses/Past imperative

Untitled
Is the past imperative tense really used? Because I can't think of how it can be used.--Caixiaohui 00:19, 15 August 2006 (UTC)


text:
User:Pthompsen

Philip A. Thompsen, Ph.D. is Associate Professor of Communication Studies at West Chester University in West Chester, Pennsylvania, USA. He currently teaches courses in mass communication, broadcasting and communication technology. He advises the university's student-operated radio station, WCUR, as well as the campus newspaper, The Quad. He is also the department's webmaster and educational technology coordinator.

Prior to joining the faculty at West Chester University, Dr. Thompsen taught at William Jewell College in Liberty, Missouri, where he also advised its student-operated campus radio station, KWJC. He has also taught at The University of Utah, Arizona State University, The University of Louisiana at Lafayette, and the Ron Baile School of Broadcasting.

Dr. Thompsen worked as a professional broadcast announcer for 8 years, from 1976 to 1984. He worked at a variety of radio and television stations in Arizona, Louisiana and Missouri. He continues to host a weekly radio program, "The Moldy Oldies Show," on WCUR.

title: User:Pthompsen


text: User:Rmrfstar

title: User:Rmrfstar


text:
Muggles' Guide to Harry Potter/Magic/Mandrake

Overview
The Mandrake is an unremarkable-looking tufty sort of plant that is purple and green in color. When dug up, its root has the shape of a human being.

Extended Description
Mandrake or Mandragora is a powerful restorative and is a vital component in restorative potions; as a result, it is necessary in Harry Potter and the Chamber of Secrets, where it is used to brew a potion that is used to restore those who have been attacked by the monster of the Chamber. The cry of the uprooted Mandrake will kill; Harry's class is repotting them on his first day back in year 2, but these are very young, almost infant mandrakes (their roots look like wrinkled and ugly babies), and their cry will only knock you out for a couple of hours.

Analysis
In Harry Potter and the Chamber of Secrets, a potion based on mandrakes is used to restore those attacked by the Monster of the Chamber. As in many other places in the series, it becomes apparent that the preparation of potions takes time. In this case, before the victims can be restored, so that they can identify the monster, we must wait for the mandrakes to become mature; conveniently, they do so immediately after Harry has vanquished the monster. In this case, the delay in their maturing is used to force Harry and Ron to come up with the solution to the puzzle of the nature and location of monster and the Chamber, with only extremely limited help from Hermione.

Mandrakes appear again in Harry Potter and the Deathly Hallows, where we see Neville and Professor Sprout carrying the potted plants up to the battlements during the preparations for the Battle at Hogwarts. Apparently, they will be cast down upon the attackers, and the cry of the exposed mandrake roots will incapacitate the attacking Death Eaters.

Questions

 * 1) In Harry Potter and the Chamber of Secrets, Mandrakes are seen to take the entire school year to reach maturity. They were, however, needed early in the year as a potion ingredient. Granted that there is an educational reason for growing them on the grounds, why would it not have been possible to buy mature mandrake roots from a supplier, say in Diagon Alley?

Greater Picture
In Harry Potter and the Chamber of Secrets, the author devised humorous descriptions of the maturation steps of the mandrake plants. The phases of plant maturity were analogous to the development of human children. First the plants were described as becoming "moody and secretive" confirming they had reached adolescence. Next the mandrakes started throwing loud parties indicating their teenage phase. Finally the mandrakes were known to be fully matured when they started moving into each others' pots.


text:
Muggles' Guide to Harry Potter/Magic/Venomous Tentacula

Overview
The Venomous Tentacula is a dark red and spiky plant that has long feelers that can reach out and capture prey. Professor Sprout cautions her second year class, "Watch out for the venomous tentacula, it's teething." (Note that in some British / Canadian editions of Harry Potter and the Chamber of Secrets, this is misspelled Venemous Tentacula.)

Extended Description
We never find out much about this plant. Professor Sprout knocks its tentacles away in Harry Potter and the Chamber of Secrets. It is commented that people are allowed to swear loudly (in contrast to the silent spell-casting being required for all other courses) in Harry Potter and the Half-Blood Prince if the Tentacula attacks them. During the final battle near the end of Harry Potter and the Deathly Hallows, Neville brings in a Tentacula that grabs a Death Eater and starts reeling him in.

We do see its seeds: small, shriveled black pods that make a faint rattling noise even when they are completely stationary. In Harry Potter and the Order of the Phoenix, Fred and George need these for their Skiving Snackboxes, but they have to get them from Mundungus Fletcher, because they are a Class C Non-Tradeable Substance.


text:
User:Digivation

I'm Digivation. I peruse the Wikis from time to time learning a little of this or that, with the occasional contribution. While I'm not totally familiar with the system and don't contribute a lot, I do what I can.

I can be found numerous places around the web, usually under "digivation"

You can also find more at my website.

I'll update this later...

title: User:Digivation


text:
Wikijunior:Ancient Civilizations/Tamil

What country did they live in?
South India & North Sri Lanka.

title: Wikijunior:Ancient Civilizations/Tamil


text:
User:The Cunctator

See The Cunctator.

title: User:The Cunctator


text:
User talk:Gametheoryman

Hello! I'm glad to see you here. I've been busy the last few days, and haven't worked further on your project (or any other projects around here, for that matter). I apologize for that. I forget where we are with your book project, exactly. Do you like what you see so far? do you need any changes made? Let me know. --Whiteknight (talk) (projects) 15:16, 15 August 2006 (UTC)

 * There are no ways to import images directly from wikipedia. Unfortunately, images can be used here only if they are uploaded to wikibooks directly, or if they are on commons. Fair use images are acceptable, but it's a touchy subject (and they could be banned in the future). Wikibooks syntax can be a little confusing, but there is a tutorial to be found at Help:Contents. The tutorial isn't 100%, but it should answer most of your questions. As the original author, you really can go about making any changes to the text or formatting you want, and there shouldnt be a problem. Wikibookians are encouraged to be bold in making edits and changes that benefit the project. --Whiteknight (talk) (projects) 16:17, 15 August 2006 (UTC)

 * Fair-use text, so long as it is properly cited, should not be a problem. I can't guarantee that, however. I'll ask around and see if i can find an answer for you. --Whiteknight (talk) (projects) 16:50, 15 August 2006 (UTC)

Decision Theory
Did you mean to load that to two separate spots? -- SB_Johnny | talk 18:07, 19 August 2006 (UTC)

 * No. I don't yet have the syntax down on how to fully describe linked sites. I was looking for a Decision Theory page as part of the Self Interest and Social Behavior wiki. From Whiteknight's reference to another chapter where this is also wanted, that seems to be a page called Self Interest and Social Behavior/Decision Theory. Is that /Decision Theory/ ? (I didn't have the slashes before.)

 * You mean for leaving a link from another page? Yes.
 * You mean something else? Dunno. :)
 * I'll mark the other (non-subpage) one for speecy deletion if it's not what you meant to make (or you can yourself using ).  SB_Johnny  | talk 19:54, 19 August 2006 (UTC)

title: User talk:Gametheoryman


text:
User:Doug (usurped)

Hi, My personal information page will be at Reswik on meta. Doug

title: User:Doug (usurped)


text:
MediaWiki Developer's Handbook/Introduction

This Handbook is intended to allow the reader to be able to learn the Mediawiki software well enough to make tweaks in the core software (or add extensions) which can either be added (committed) to the main branch of the code (if accepted by the development team) or simply used behind the scenes in one's own code.

It seeks to provide a more detailed guide to its structure than the overview file (help.doc) which is included with the software provides and discuss variables, etc. not covered in the PHPDocumentator automated documentation available elsewhere online (I don't see any way that it lists all variables used--that would be a nice enhancement to the Documentor software itself). There is likely much relevant documentation already at Mediawiki sites (e.g., at http://meta.wikimedia.org/ ) but none which really can provide a tutorial for learning how to follow the flow of the code in detail (and to use this to enhance, extend, etc. the software).


text:
MediaWiki Developer's Handbook/Literature

A number of additional books relate to learning how to develop (or hack/extend) Medawiki software. ("Hacking" is used here in the non-pejorative sense of the word. See Hacking/Introduction/The hacker ethic for an explanation.)

 * PHP Programming (see also PHP)
 * SQL (especially MySQL, until wholly free (including free-for-commercial use) databases like PostgreSQL are fully supported, at which point the conversion/migration process is to be described here on this page) (see also SQL or (see also MySQL))
 * Subversion (the system used by many open source projects including Mediawiki) to keep track of changes to its development. This would be useful for those wishing to publish their changes to the code, especially to the main branch of code (i.e., not as much for extensions, though these could be done through SVN as well).
 * MediaWiki Administrator's Handbook


text:
Talk:Technologies for Rural Development/Ways of farming

 * I think Organic farming practices are the most appropriate for this section. --MJBT 09:58, 5 February 2007 (UTC)
 * In the USA, the term "organic" can only be used for produce grown in compliance with the Organic Food Production Act of 1990. You can read it at http://www.ams.usda.gov/nop/NOP/NOPhome.html (click on the Act for the pdf file). State governments authorize certain groups to grant organic certification, based on various criteria. Pennsylvania's group is http://www.paorganic.org/. Per their website, "The United States Department of Agriculture requires that anyone who produces, processes or handles organic agricultural products must be certified by a USDA-accredited certifier in order to sell, label or represent their products as "organic." To become certified, an organic producer, processor or handler must develop, implement and maintain an organic system plan." The site hasn't been updated in two years, but I think it's still considered current. "Organic" in the USA means "certified" -- in which growers pay inspectors for certification. It's a bit of a racket.
 * Related, there's some debate about what should be allowed under the umbrella of "organic" farming. Chlorine is generally considered an acceptable chemical. The use of natural acids such as vinegar for sterilization is not accepted because it hasn't been studied or isolated or whatever.
 * I'm not sure what country you're from, but I thought I'd let you know that "organic" is a legally-defined term in the USA, controlled by political interests, not maybe what you might think it to be. --65.78.214.189 01:32, 8 September 2007 (UTC)


text:
MediaWiki Developer's Handbook/Adding new tags

To create a parser extension for a new tag just requires a few lines of code:  <? php if( !defined( 'MEDIAWIKI' ) ) { die( "This file is part of MediaWiki and is not a valid entry point\n" ); }

$wgExtensionFunctions[] = 'myNewTagInit'; $wgExtensionCredits['myNewTag'][]= array( 'name'         => 'myNewTag Extension',   'version'      => '1.0.0',   'author'       => 'Your Name',   'url'          => 'http://www.your.com/mynewtag/',   'description'  => 'This extension is for demonstration only.');

function myNewTagInit { global $wgParser; $wgParser->setHook( "myNewTag", "myNewTagParse" ); } function myNewTagParse($content, $params, $parser ) { return "My 'fancy' output"; } ?>  For testing create a subdirectory mediawikipath/extensions/mynewtag. Save the coding there as myNewTag.php. Add the following line to LocalSettings.php:  require_once "$IP/extensions/mynewtag/myNewTag.php";  Now create a new mediawiki page   and save it.

The output will look like this: My 'fancy' output


text:
User:SBJohnny/Sandbox1

Things to do (and propagandise)

Policy/guidelines

 * Voting/consensus rules (Wikibooks_talk:General_voting_rules/Proposal)
 * What do we mean by textbook, really?
 * Admin guidelines (Administrators/Proposal)
 * Naming policy
 * Categorisation policy (Categories)
 * Wikibooks for wikipedians
 * Revamp VfD
 * Revamp Speedy Deletion
 * Dispute resolution processes
 * Transwiki guidelines
 * Interpretations of all sorts of good stuff from wikipedia including:
 * w:WP:NOT
 * w:WP:SPAM
 * w:WP:CREEP -- much needed around here, IMO
 * w:WP:ENC -- silly, but useful

Make pretty

 * Wikibooks linking templates on WP

title: User:SBJohnny/Sandbox1


text:
MediaWiki Developer's Handbook/Add Button

if( !defined( 'MEDIAWIKI' ) ) { die( "This file is part of MediaWiki and is not a valid entry point\n" ); } $myRedirectPng = "extensions/myRedirect/myRedirect.png";

$wgHooks['EditPage::showEditForm:initial'][] = 'myRedirectButton'; $wgExtensionCredits['myRedirectButton'][]= array( 'name'         => 'my Redirect Button Extension',   'version'      => '1.0.0',   'author'       => 'Your Name',   'url'          => 'http://www.your.com/myredirectbutton/',   'description'  => 'This extension is for demonstration only.');

// Add a button to the internal editor function myRedirectButton ($editPage) { global $wgOut, $wgScriptPath, $myRedirectPng; // Insert javascript script that hooks up to create button. $wgOut->addScript("\n".      "function myAddButton{\n".       "  addButton('$myRedirectPng','Redirect','#REDIRECT ','','Insert text');".       "  }\n".       "addOnloadHook(myAddButton);\n".       " "); return true; }

To install

 require_once("$IP/extensions/myRedirect/myRedirect.php");
 * Create a directory mediawiki/extensions/myRedirect
 * Save above script as myRedirect.php
 * Save the following picture to the directory as myRedirect.png. [[Image:Button_redirect.png]].
 * Append the following line to LocalSettings.php

Add Button that calls a custom javascript function
<?php

// to install, upload this file as /extensions/myEditbarButton/myEditbarButton.php // then, copy this button image as /extensions/myEditbarButton/myButtonCard.png // // then add the following line to end of LocalSettings.php // //      require_once("$IP/extensions/myEditbarButton/myEditbarButton.php"); // // This is a modification of // https://en.wikibooks.org/wiki/MediaWiki_Developer%27s_Handbook/Add_Button // // Sorry that extension can only add a new button before the other buttons // of the edit bar, instead of after them. I am also not sure if this will work // on other installations of mediawiki ( mine is MediaWiki: 1.16.5, PHP: 5.2.17 // MySQL: 5.1.69 )

if( !defined( 'MEDIAWIKI' ) ) { die( "This file is part of MediaWiki and is not a valid entry point\n" ); } $myButtonPng = "extensions/myEditbarButton/myButtonCard.png";

$wgHooks['EditPage::showEditForm:initial'][] = 'myEditbarButton';

// for $wgExtensionsCredits[$type][] //      $type must be api, media, parserhook, skin //                    specialpage, variable, other

$wgExtensionCredits['other'][] = array(       'name'         => 'my Editbar Button',         'version'      => '1.0.0',         'author'       => 'Your Name',         'url'          => 'http://www.your.com/myredirectbutton/',         'description'  => 'Adds a new button to the old edit bar that calls a custom javascript function.'        );

// Add a button to the internal editor function myEditbarButton ($editPage) { global $wgOut, $wgScriptPath, $myButtonPng; // Insert javascript script that hooks up to create button. $wgOut->addScript("\n".               "function myAddButton{ \n".                        "var toolbar = document.getElementById( 'toolbar' ); \n".                        "var image = document.createElement( 'img' ); \n".                        "image.className = 'mw-toolbar-editbutton'; \n".                        "image.src = '$myButtonPng'; \n".                        "image.border = 0; \n".                        "image.alt = 'speedTip'; \n".                        "image.title = 'speedTip'; \n".                        "image.style.cursor = 'pointer'; \n".                        "image.onclick = function { \n".                                "window.alert('HelloWorld'); \n".                        "} \n".                        "toolbar.appendChild( image ); \n".                "} \n".

"addOnloadHook(myAddButton); \n". " ");       return true; }

?>

Links
http://commons.wikimedia.org/wiki/Category:Button_link


text:
User:Plaicy

see german user site

title: User:Plaicy


text:
Muggles' Guide to Harry Potter/Magic/Devil's Snare

Overview
Devil's Snare is an extremely dangerous plant that will, as suggested by its name, ensnare wizards when disturbed. It strangles those who approach it by wrapping them in its (usually dark, and in a developed plant thick) tendrils. Possibly this is a magical variant of the Muggle Venus Flytrap or pitcher plant, that capture insects for food. We suspect that in the wild it can also capture and consume larger animals such as cows. If this is the case, "playing dead" is not a defence; lying still may prevent it from strangling you, but will trigger the plant's attempts to start growing roots into you, and the strangling will resume as soon as you try to get away.

Extended Description
A plant of the dark and dank, it reacts to heat and light by retreating. When Harry, Ron, and Hermione are trapped in it, in Harry Potter and the Philosopher's Stone, Hermione remembers this sensitivity, and, when prompted by Ron, manages to create fire that makes the plant retreat.

Devil's Snare appears again in Harry Potter and the Order of the Phoenix. Here, Harry, Hermione, Ron, and Ginny see a small specimen delivered as a gift to one Broderick Bode, a long-term spell-damage patient at St. Mungo's Hospital. Hermione later reads in the Daily Prophet that Bode, encouraged to tend this plant as part of his healing, had been strangled by it.

Analysis
Given their previous experience of the plant, one must wonder why Harry, Ron, and Hermione did not recognize it when they saw it delivered to Bode. Harry does admit to being made uneasy by the potted plant's swaying tendrils. It is possible that they had simply been distracted by their encounter with Gilderoy Lockhart.


text:
Control Systems/Common Nonlinearities

There are some nonlinearities that happen so frequently in physical systems that they are called "Common nonlinearities". These common nonlinearities include Hysteresis, Backlash, and Dead-zone.

Hysteresis
Continuing with the example of a household thermostat, let's say that your thermostat is set at 70 degrees (Fahrenheit). The furnace turns on, and the house heats up to 70 degrees, and then the thermostat dutifully turns the furnace off again. However, there is still a large amount of residual heat left in the ducts, and the hot air from the vents on the ground may not all have risen up to the level of the thermostat. This means that after the furnace turns off, the house may continue to get hotter, maybe even to uncomfortable levels.

So the furnace turns off, the house heats up to 80 degrees, and then the air conditioner turns on. The temperature of the house cools down to 70 degrees again, and the A/C turns back off. However, the house continues to cool down, and then it gets too cold, and the furnace needs to turn back on.

As we can see from this example, a bang-bang controller, if poorly designed, can cause big problems, and it can waste lots of energy. To avoid this, we implement the idea of Hysteresis, which is a set of threshold values that allow for overflow outputs. Implementing hysteresis, our furnace now turns off when we get to 65 degrees, and the house slowly warms up to 75 degrees, and doesn't turn on the A/C unit. This is a far preferable solution.

Backlash
•Backlash refers to the angle that the output shaft of a gearhead can rotate without the input shaft moving. Backlash arises due to tolerance in manufacturing; the gear teeth need some play to avoid jamming when they mesh. An inexpensive gearhead may have backlash of a degree or more, while more expensive precision gearheads have nearly zero backlash. Backlash typically increases with the number of gear stages. Some gear types, notably harmonic drive gears (see Section 26.1.2), are specifically designed for near-zero backlash, usually by using flexible elements.

E.g.: Mechanical gear.

Dead-Zone
A dead-zone is a kind of non linearity in which the system doesn't respond to the given input until the input reaches a particular level or it can refer to a condition in which output becomes zero when the input crosses certain limiting value.

title: Control Systems/Common Nonlinearities


text:
Horticulture/Ocimum basilicum

Basil (Ocimum basilicum, family Lamiaceae) is also known as St. Joseph's Wort and Sweet Basil. It is a tender low-growing herb, originally native to tropical Asia. It grows to between 20–60 cm tall, with opposite, light green, silky leaves 1.5–5 cm long and 1–3 cm broad. It tastes somewhat like anise, with a strong, pungent, sweet smell. Basil is very sensitive to cold, with best growth in hot, dry conditions. While most common varieties are treated as annuals, some are perennial, including African Blue and Holy Thai basil.

The word basil comes from the Greek βασιλευς, meaning "king", as it is believed to have grown above the spot where St. Constantine and Helen discovered the Holy Cross. The Oxford English Dictionary quotes speculations that basil may have been used in "some royal unguent, bath, or medicine". Basil is still considered the "king of herbs" by many cookery authors. An alternative etymology has "basil" coming from the Latin word basilicus, meaning dragon and being the root for basilisk, but this likely was a linguistic reworking of the word as brought from Greece.

Basil, the herb
Basil is most commonly recommended to be used fresh, and in cooked recipes, is generally added at the last moment, as cooking destroys the flavour quickly. The fresh herb can be kept for a short time in plastic bags in the refrigerator, or for a longer period in the freezer, after being blanched quickly in boiling water. Place fresh leaves in a dry jar with a pinch of salt, and cover with olive oil. The dried herb also loses most of its flavour, and what little flavour remains tastes very different, with a weak coumarin flavour, like hay. But because most Americans either lack the dedication or resources to maintain a supply of fresh herbs, the most common household use of basil in the US is through containers of dried basil purchased from stores.

Mediterranean, Thai, and Vietnamese cuisines frequently use basil, the former frequently combining it with tomato. Basil is one of the main ingredients in pesto — a green Italian oil-and-herb sauce from the city of Genoa, its other two main ingredients being olive oil and pine nuts. The most commonly used Mediterranean basil cultivars are 'Genovese', 'Purple Ruffles', 'Mammoth', 'Cinnamon', 'Lemon', 'Globe', and 'African Blue'. Chinese cuisine also uses fresh or dried basils in soups and other foods. In Taiwan, people add fresh basil leaves into thick soups (羹湯; gēngtāng). They also eat fried chicken with deep-fried basil leaves.

Basil is sometimes used with fresh fruit and in fruit jams and sauces — in particular with strawberries, but also raspberries or dark-colored plums. Arguably the flat-leaf basil used in Vietnamese cooking, which has a slightly different flavour, is more suitable for use with fruit.

When soaked in water the seeds of several basil varieties become gelatinous, and are used in Asian drinks and desserts such as falooda or sherbet. Such seeds are known variously as sabja, subja, takmaria, tukmaria, or falooda seeds. They are used for their medicinal properties in Ayurveda, the traditional medicinal system of India.

Other basils
Several other basils, including some other Ocimum species, are grown in many regions of Asia. Most of the Asian basils have a clove-like flavour that is generally stronger than the Mediterranean basils. In China, the local cultivar is called 九層塔 (jiǔcéngtǎ; literally "nine-level pagoda"), while the imported varieties are specifically called 羅勒 (luólè) or 巴西里 (bāxīlǐ).

Basil is also very popular in Thai cuisine, which uses cultivars of two different species: the type known in the west as Thai Basil, which is a cultivar of O. basilicum, and Holy Basil (Ocimum sanctum).

'Lemon basil' has a strong lemony smell and flavour very different from those of other varieties, because it contains a chemical called citral. It is widely used in Indonesia, where it is called kemangi and served raw, together with raw cabbage, green beans, and cucumber, as an accompaniment to fried fish or duck. Its flowers, broken up, are a zesty salad condiment.

Cultivation
Basil thrives in hot weather, but behaves as an annual if there is any chance of a frost. In Northern Europe, the northern states of the U.S., and the South Island of New Zealand it will grow best if sown under glass in a peat pot, then planted out in late spring/early summer (when there is little chance of a frost). It fares best in a well-drained sunny spot.

Although basil will grow best outdoors, it can be grown indoors in a pot and, like most herbs, will do best on a south-facing windowsill (in the Northern Hemisphere). It should be kept away from any draughts, and must be able to get plenty of sunlight, therefore a greenhouse or cloche is ideal if available.

If its leaves have wilted from lack of water, it will recover if watered thoroughly and placed in a sunny location. Yellow leaves towards the bottom of the plant are an indication that the plant needs more sunlight or less fertilizer.

In sunnier climates such as Southern Europe, the southern states of the U.S., the North Island of New Zealand, and Australia, basil will thrive when planted outside. It also thrives over the summertime in the central and northern United States, but dies out when temperatures reach the low thirties, to grow again the next year if it was allowed to go to seed. It will need regular watering, but not as much attention as is needed in other climates.

Basil can also be propagated very reliably from cuttings in exactly the same manner as "Busy Lizzie" (Impatiens), with the stems of short cuttings suspended for two weeks or so in water until roots develop.

Leaf production slows or stops on any stem which flowers, so you can pinch off any flower stems to keep the plant in production, or pinch off some stems while leaving others to bloom for decoration or seeds. Once you do let the plant flower, it will produce seed pods containing small black seeds which you can save and plant the following year. Picking the leaves off the plant helps "promote growth", largely because the plant responds by converting pairs of leaflets next to the topmost leaves into new stems.

title: Horticulture/Ocimum basilicum


text:
User talk:Caixiaohui~enwikibooks

Thank you for your French contributions
Thank you for your additions to the French Wikibook. The grammar section should eventually become a complete reference book, so feel free to remove, reorder, and add pages and sections as you see fit. Thanks again! --hagindaz 23:52, 15 August 2006 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Caixiaohui. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Caixiaohui~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:04, 17 March 2015 (UTC)

French impératif passé
You can actually use the impératif in the past when you want somebody have something done by sometime. It's like "Have your homework done by tomorrow" in English. Aie fini tes devoirs jusqu'à demain. --2.245.119.88 (discuss) 23:20, 19 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 04:44, 19 April 2015 (UTC)

title: User talk:Caixiaohui~enwikibooks


text:
Talk:Circuit Theory/Systems of Linear Equations

This module is good. I don't know why it was replaced. I think the two "Systems of linear equations" pages should be blended. The only specific critique I have with this page is that it does not make clear what a homogeneous system is. Is it only when all the constant terms are zero or can it be any system in which the constant terms are all the same?


text: Category:Book:Announcing

title: Category:Book:Announcing


text:
Talk:Organic Chemistry/Alkanes

chaotic
May be we should change the explanantion of methane and ethane to a lower level, where these molecules are once again discussed. Also, indeed, alkanes are relatively useless.... One of their uses is in a cracking reactor; naphta (a mixture of alkanes distilled from crude oil) is literally cracked to give smaller unsaturated, more useful chemicals. 131.174.15.158 13:14, 29 June 2007 (UTC)

Preparation of Alkanes
I am an undergraduate student studying University Sophomore Level Organic Chemistry. Just noticed that nowhere in alkanes was their preperation methods,like wurtz synthesis,kolbe's electrolysis,etc. mentioned. I would like to add these,but I dont know where? If someone could start the section 'Prep of alkanes' I would like to contribute. New here,hope I can help -xC

 * I just looked through two modern organic chemistry textbooks I have and neither reaction is covered. That doesn't mean they shouldn't be, but I think it should probably come later. We'll probably cover conversion of alkyl-halides to alkanes via Grignard reagent in the Haloalkanes section. But generally, alkanes are what you don't want. There's not a lot you can do (at least in a controlled, laboratory way) with them, so they're chemically uninteresting. I'm not dismissing the idea. I'll definitely consider it. And if nothing else, I think the fact that they're not very useful in the laboratory is worth mention as well. But I don't know that adding it this early would make much sense, especially since the reactants in those reactions are more advanced structures that haven't been discussed yet. Perhaps in the chapters where we cover those classes of reactants and their reactions, it would make sense. -- Pete 14:54, 22 November 2006 (UTC)

 * Definitely. Wurtz Synthesis/Kolbe's Electrolysis do deserve mention, partly because they are mentioned in most places. :D Atleast, the more mechanisms we can demonstrate, the more easy it is for us to emphasize that all organic reactions happen in fragments of familiar steps.

---

Definition of Organic
I noticed that the module currently states that for a compound to be organic it must contain both carbon and hydrogen. I just want to point out that the whole concept of organic vs. inorganic arose from a misconception that it was impossible to synthesize "organic" compounds from inorganic ones. We now know this is untrue. One example I can think of offhand is the photosynthesis of glucose, a reaction we probably learned in middle school, whereby water and carbon dioxide (both "inorganic") are used to C6H12O6, a simple sugar that is considered "organic" My point is that the definition of organic vs inorganic is somewhat artificial. My other point is that a few compounds considered "organic" do not contain hydrogen, due to substitution by halogen atoms. Carbon tetrachloride (or tetrachloromethane, if you prefer) comes to mind. I don't know the best way to explain this in the text, I'm just trying to raise the issue. WilliamJenkins09 03:48, 30 March 2007 (UTC)

 * It all goes back to Wohler's 1828 synthesis of urea from ammonium cyanate which demonstrated the organic molecules were nothing special. There's now a 'Journal of Inorganic Biochemistry' - what would the early chemists have made of that?!

 * On the other hand, organic chemicals do have many common properties and reactions which are unusual for inorganic substances, so it makes sense to split chemistry on inorganic/organic lines.

 * The definition of organic chemistry is muddled, but I usually tell students that all organic molecules contain carbon, but that a few carbon compounds are considered inorganic. (Carbon itself, carbonates, cyanide, cyanates, carbides, etc)

 * Ewen 06:06, 30 March 2007 (UTC)

title: Talk:Organic Chemistry/Alkanes


text:
User talk:Saurabhkumar502

Welcome
Hello, Saurabhkumar, and welcome to Wikibooks! You can watch pages by clicking the "watch" button at the top of each page, rather than the "move" button. If you have any questions about using Wikibooks don't hesitate to ask. Enjoy the book! Thanks, hagindaz 05:19, 16 August 2006 (UTC)

title: User talk:Saurabhkumar502


text: MediaWiki Developer's Handbook/Navigation


text: Template:Dynamic navigation

title: Template:Dynamic navigation


text: User:Retropunk/Ja Eng Row Template

title: User:Retropunk/Ja Eng Row Template


text:
User:Retropunk/Ja Eng Footer Template

-|}

title: User:Retropunk/Ja Eng Footer Template


text: Adventist Youth Honors Answer Book/Arts and Crafts/Soap Craft


text:
Adventist Youth Honors Answer Book/Arts and Crafts/Music (General Conference)

3. Know a half-tone, a whole tone, a third, a fifth, and an octave.
A half tone is the same as a half step (1/12 of an octave). It is basically the distance of two notes immediately next to each other, such as C to C# and B to C. A whole tone is the same as a whole step. It is the distance of two notes separated by another, such as C to D (C# is in between) and B to C# (C is in between). A third is an interval of three degrees (C and E). A fifth is an interval of five degrees (C and G). An octave is an interval of eight degrees—the same note eight notes higher or lower (Middle C and C).

11. Do a biographical sketch on a famous hymn writer and orally present it to a group.
Biographies of some hymn writers can be found at the following links.

Wikipedia Christian Hymnwriters

Cyber Hymnal

Christian Biography Resources


text:
User:Abdull

Recipes created

 * Super Foamy milkshake.

X86 Assembly

 * X86 Assembly/X86 Instructions

title: User:Abdull


text:
User:Sebmol

Hello,

I'm sebmol on German and English Wikipedia as well as Wikiversity.

title: User:Sebmol