text:
Spearfish torpedo

The Spearfish torpedo (formally Naval Staff Target 7525) is the heavy torpedo used by the submarines of the Royal Navy. It can be guided by wire or by autonomous active or passive sonar, and provides both anti-submarine warfare (ASW) and anti-surface warfare (ASuW) capability. Spearfish development began in the 1970s, with production starting in 1988, and deployment in 1992. By 2004, the new weapon had completely replaced the older Tigerfish torpedo.

Design
The torpedo is driven by a pump-jet coupled to a Hamilton Sundstrand 21TP04 gas turbine engine using Otto fuel II and hydroxylammonium perchlorate as oxidiser. The addition of an oxidiser improves the specific energy of the fuel by reducing the fuel-richness of the Otto fuel. The Spearfish, which are capable of travelling at 80 knots, were designed to catch high-speed, deep-diving Soviet threats such as the Alfa-class submarine.

A microprocessor enables the torpedo to make autonomous tactical decisions during the attack. It has a powerful blast warhead, triggered by either contact detonation (against a submarine hull) or an acoustic proximity fuse (for under-keel detonation against ships). A standoff detonation under the keel enhances blast effects against surface ships through the amplification of stress resulting from the interaction of the explosion's products and the flexible structure of the ship.

Guidance
In a typical engagement, Spearfish will run out wire-guided to the general vicinity of the target and then conduct a covert passive search. The high-capacity guide wire system, specifically designed to match the Spearfish's manoeuvre and speed envelope, provides two-way data exchange between the torpedo and launch submarine, maximising the submarine's organic sensor and combat control capabilities.

Once at close range the Spearfish uses active sonar to classify and home in on its target. High-power transmissions and sophisticated signal processing enable Spearfish to accurately discriminate targets from background noise and ensure high resistance to acoustic countermeasures and/or evasive manoeuvres.

Should Spearfish fail to hit the target on its first attack, it automatically selects an appropriate re-attack mode until it successfully concludes the engagement.

Testing
Tactical software has been extensively refined through real-time, hardware in the loop simulations and demonstrated in more than 500 in-water trials and exercise firings.

Production
The production contract for the Spearfish Torpedo was placed with GEC-Marconi Underwater Systems Ltd (now BAE Systems) in 1983, following a development programme lasting several years. Spearfish entered full production in 1988.

Deployment
The first Spearfish were deployed in 1992, with deliveries completed in 2003; the number ordered has not been revealed. Spearfish torpedoes are stored and serviced at Beith Ordnance Storage facility in North Ayrshire.

Upgrade
In 2009, an upgrade programme began, leading to further sophisticated advances in Spearfish's homing, warheads, tactical and fuelling systems, as well as an upgraded guidance link. This will last until 2019.

On 15 December 2014, the Ministry of Defence awarded BAE Systems a £270 million contract to upgrade the Spearfish torpedo. The upgrade includes a new insensitive-munition warhead from TDW, a change to the fuel system to improve safety, full digitisation of the weapon and a new fibre optic guidance link to improve performance. The upgraded 'MOD 1' torpedoes will enter service between 2020 and 2024. In February 2021 HMS Talent (S92) test fired 3 upgraded 'MOD 1' specification Spearfish torpedoes as part of their final testing before entry into service with the Royal Navy.

title: Spearfish torpedo


text:
Microsoft Personal Web Server

Microsoft Personal Web Server (PWS) is a scaled-down web server software for Windows operating systems. It has fewer features than Microsoft's Internet Information Services (IIS) and its functions have been superseded by IIS and Visual Studio. Microsoft officially supports PWS on Windows 95-98, Windows 98 SE, and Windows NT 4.0. Prior to the release of Windows 2000, PWS was available as a free download as well as included on the Windows distribution CDs. PWS 4 was the last version and it can be found on the Windows 98 CD and the Windows NT 4.0 Option Pack.

Personal Web Server was originally created by Vermeer Technologies, the same company which created Microsoft FrontPage, before they were acquired by Microsoft. It was installed by FrontPage versions 1.1 to 98 as well.

NT Workstation 4.0 shipped with Peer Web Services, which was based on IIS 2.0 and 3.0. With IIS 4.0, this was renamed Personal Web Server to be consistent with the name used in 95/98.

Since Windows 2000, PWS was renamed the same IIS name used in server versions of Windows as a standard Windows component. Windows ME and Windows XP Home Edition support neither PWS nor IIS, although PWS can be installed on Windows ME. In other editions of Windows XP, IIS is included as standard.

Before Microsoft Visual Studio 2005, PWS was useful in developing web applications on the localhost before deploying to a production web server. The IDE of Visual Studio 2005 (and later versions) now contains a built-in lightweight web server for such development purposes.

FTP, SMTP, HTTP and the usual web languages such as PHP and Perl are supported by PWS. It also supports basic CGI (Common Gateway Interface) conventions and a subset of Classic ASP. Using these technologies, web applications running on PWS are capable of performing and interpreting database queries and results.

Microsoft also produced a version of Personal Web Server for the Macintosh based on code acquired in its acquisition of ResNova Software in November 1996.

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

title: Microsoft Personal Web Server


text:
1909 in literature

This article contains information about the literary events and publications of 1909.

Events

 * January – T. E. Hulme's poems "Autumn" and "A City Sunset" are included in the Poets' Club anthology For Christmas MDCCCCVIII, as the first examples of Imagism.
 * January 15 – Filippo Tommaso Marinetti's drama La donna è mobile opens at the Teatro Alfieri, Turin.
 * February 1 – The first issue appears of La Nouvelle Revue Française, a literary magazine founded in Paris by André Gide, Jacques Copeau, Jean Schlumberger, Gaston Gallimard, and others.
 * February 20 – Filippo Tommaso Marinetti's Futurist Manifesto first appears in the French newspaper Le Figaro.
 * March 2 – Katherine Mansfield, while pregnant by another man, marries the singing teacher George Bowden, whom she barely knows. She leaves him the same evening to resume lesbian relations with Ida Baker.
 * April
 * The opening night of Filippo Tommaso Marinetti's drama Le Roi bombance (The Feasting King, written 1905) is heckled by the audience and the writer himself.
 * The German periodical Die Tat is founded by Ernst Horneffer.
 * April 24 – The Metropolitan Library (京师图书馆, Jīngshī Túshūguǎn) in Beijing, predecessor of the National Library of China, is founded by the Qing government.
 * September 6 – Israel Zangwill's play The Melting Pot opens in New York City.
 * September 23 – Gaston Leroux's novel The Phantom of the Opera (Le Fantôme de l'Opéra) begins serialization in the Paris newspaper Le Gaulois.
 * September 29 – Franz Kafka's short story "The Aeroplanes at Brescia (Die Aeroplane in Brescia)", based on a real event, is published in the Prague newspaper Bohemia, as the first description of airplanes in German literature.
 * November – E. M. Forster's science fiction short story "The Machine Stops" is published in The Oxford and Cambridge Review.
 * unknown date – Babelstornið (The Tower of Babel), by Rasmus Rasmussen, writing as Regin í Líð, becomes the first Faroese language novel to be published.

Fiction

 * Florence Barclay – The Rosary
 * Maurice Barrès – Colette Baudoche
 * André Billy – La Derive
 * Algernon Blackwood
 * The Education of Uncle Paul
 * Jimbo: A Fantasy
 * René Boylesve – La Jeune Fille bien élevée (The Well-raised Girl)
 * Hall Caine – The White Prophet
 * Gilbert Cannan – Peter Homunculus
 * Ion Luca Caragiale – Kir Ianulea
 * Robert W. Chambers – The Danger Mark
 * Herbert Croly – The Promise of American Life
 * Em Kol Chai (Chava Shapiro) – Kovetz Tziurim (קבץ ציורים, A Collection of Sketches)
 * Concha Espina – That Luzmela Girl
 * Charles Hoy Fort – The Outcast Manufacturers
 * Anatole France – Balthazar
 * Jacques Futrelle – Elusive Isabel
 * John Galsworthy – Fraternity
 * Charles Garvice – A Fair Impostor
 * Robert Hichens – Bella Donna
 * Olha Kobylianska – V Nediliu Rano Zillia Kopala (She Gathered Herbs on Sunday Morning)
 * Maurice Leblanc – The Hollow Needle
 * Gaston Leroux – Le fauteuil hanté (The Haunted Chair)
 * Jack London – Martin Eden
 * John Masefield – Multitude and Solitude
 * Silas Weir Mitchell – The Red City
 * Baroness Orczy
 * The Nest of the Sparrowhawk
 * The Old Man in the Corner
 * Randall Parrish – My Lady of the South
 * Eden Phillpotts – The Haven
 * Luigi Pirandello – I vecchi e i giovani (The Old and the Young, part 1)
 * Władysław Reymont – Chłopi (The Peasants; publication completed)
 * Stein Riverton – Jernvognen (The Iron Carriage)
 * Olivia Shakespear – Uncle Hilary
 * Gertrude Stein – Three Lives
 * Gene Stratton-Porter – A Girl of the Limberlost
 * Hermann Sudermann – The Song of Songs
 * Mark Twain – Captain Stormfield's Visit to Heaven (book publication)
 * Edgar Wallace
 * Captain Tatham of Tatham Island
 * The Duke in the Suburbs
 * Robert Walser – Jakob von Gunten
 * Mary Augusta Ward – Daphne
 * H. G. Wells
 * Ann Veronica
 * Tono-Bungay

Children and young people

 * L. Frank Baum
 * The Road to Oz
 * Aunt Jane's Nieces at Work (as Edith Van Dyne)
 * Angela Brazil – The Nicest Girl in the School
 * Lucy Maud Montgomery – Anne of Avonlea
 * Beatrix Potter
 * The Tale of the Flopsy Bunnies
 * The Tale of Ginger and Pickles
 * P. G. Wodehouse – Mike

Drama

 * Paul Armont and Nicolas Nancey – Théodore et Cie
 * Sem Benelli – The Jester's Supper (La cena delle beffe)
 * Clyde Fitch – The City
 * John Galsworthy – Strife
 * Harley Granville-Barker – The Madras House
 * Cicely Hamilton – A Pageant of Great Women
 * Agha Hashar Kashmiri – Khwab-e-Hasti (The Dream World of Existence)
 * Oskar Kokoschka – Murderer, the Hope of Women (Mörder, Hoffnung der Frauen)
 * Else Lasker-Schüler – Die Wupper (published)
 * André de Lorde – L'horrible expérience
 * Ferenc Molnár – Liliom
 * Quintero brothers – El patinillo
 * George Bernard Shaw – The Shewing-Up of Blanco Posnet

Poetry

 * Guillaume Apollinaire – L'Enchanteur pourrissant (The Putrifying Enchanter)
 * François Mauriac – Les Mains jointes (Clasped Hands)
 * John Millington Synge – Poems and Translations

Non-fiction

 * Henry James – Italian Hours
 * William James – A Pluralistic Universe
 * Jane's All the World's Aircraft (first annual edition)
 * Isabella Margaret Elizabeth Blandin - History of Higher Education of Women in the South, Prior to 1860
 * Daniel Jones – The Pronunciation of English
 * C. I. Scofield (ed.) – Scofield Reference Bible
 * Charlotte Fell Smith – John Dee, 1527–1608
 * Eraclie Sterian – În noaptea nunții (On Your Wedding Night)
 * A. E. Waite – The Hidden Church of the Holy Graal
 * Alice Zimmern – Women's Suffrage in Many Lands

Births

 * January 20 – Mae Virginia Cowdery, African American poet (died 1953)
 * January 18 – Oskar Davičo, Serbian novelist and poet (died 1989)
 * January 29 – Phoebe Hesketh (Phoebe Rayner), English poet (died 2005)
 * February 15 – Miep Gies (Hermine Santruschitz), Austrian-born biographer (died 2010)
 * February 24 – August Derleth, American anthologist (died 1971)
 * March 6 – Stanisław Jerzy Lec, Polish aphorist and poet (died 1966)
 * March 17 – Margiad Evans, Anglo-Welsh poet, novelist and illustrator (died 1958)
 * March 22 – Gabrielle Roy, French Canadian author (died 1983)
 * March 28 – Nelson Algren, American novelist (died 1981)
 * March 31 – Robert Brasillach, French author (died 1945)
 * April 8 – John Fante, American novelist (died 1983)
 * May 1 – Yiannis Ritsos, Greek poet (died 1990)
 * May 5 – Miklós Radnóti, Hungarian poet (died 1944)
 * May 9 – Robert Garioch, Scottish poet (died 1981)
 * June 6 – Isaiah Berlin, German-born philosopher (died 1997)
 * June 19 – Osamu Dazai (太宰 治), Japanese author (died 1948)
 * June 28 – Eric Ambler, English spy novelist (died 1998)
 * June 29 – C. Hamilton Ellis, English writer (died 1987)
 * July 1 – Juan Carlos Onetti, Uruguayan writer (died 1994)
 * July 8 – Petar Šegedin, Croatian diplomat, novelist and essayist (died 1998)
 * July 17 – G. P. Wells, English zoologist, son and co-author of H. G. Wells (died 1985)
 * July 28 – Malcolm Lowry, English novelist (died 1957)
 * July 29 – Chester Himes, American writer (died 1984)
 * July 30 – C. Northcote Parkinson, English historian and author (died 1993)
 * August 3 – Walter Van Tilburg Clark, American novelist (died 1971)
 * August 11 – Uku Masing, Estonian religious philosopher, linguist and writer (died 1985)
 * August 19 – Jerzy Andrzejewski, Polish author (died 1983)
 * September 9 – Noel Barber, British novelist (died 1988)
 * October 24 – Sheila Watson (Sheila Doherty), Canadian novelist and critic (died 1998)
 * November 12 – Laxmi Prasad Devkota, Nepali poet, playwright, and novelist (died 1959)
 * November 26 – Eugène Ionesco (Eugen Ionescu), Romanian-born French playwright (died 1994)
 * November 27 – James Agee, American writer (died 1955)
 * December 7 – Alexandru Talex, Romanian journalist, critic and biographer (died 1998)
 * December 14 – Ronald Welch (Ronald Oliver Felton), Welsh novelist and children's writer writing in English (died 1982)
 * December 16 – Edgar Mittelholzer, Guyanese novelist (suicide 1965)

Deaths

 * January 1 – Mollie Evelyn Moore Davis, American poet, writer, and editor (born 1844)
 * January 14 – William à Beckett, English journalist (born 1844)
 * January 22 – Hattie Tyng Griswold, American author (born 1842)
 * February 11 – Russell Sturgis, American art critic (born 1836)
 * March 24 – John Millington Synge, Irish dramatist and poet (born 1871)
 * March 27 (probable) – John Davidson, Scottish poet (born 1857)
 * April 9
 * Francis Marion Crawford, American novelist (born 1854)
 * Paschal Grousset, French journalist and science fiction writer (born 1844)
 * April 12 – Algernon Charles Swinburne, English poet (born 1837)
 * April 21 – Denys Corbet, Guernsey poet writing in Guernsey French and English (born 1826)
 * April 26 – Marcus Dods, Scottish theologian (born 1834)
 * May 18 – George Meredith, English novelist and poet (born 1828)
 * June 11 – Jacob Mikhailovich Gordin, American dramatist (born 1853)
 * June 24 – Sarah Orne Jewett, American writer (born 1849)
 * July 8 – Albert Craig (The Surrey Poet), English cricket writer (born 1850)
 * July 9 – Rosa Nouchette Carey, English children's writer (born 1840)
 * August 15 – Euclides da Cunha, Brazilian writer, shot (born 1866)
 * August 18 – Theodore Martin, Scottish-born writer (born 1816)
 * August 21 – George Cabot Lodge, American poet (born 1873)
 * August 23 – Liu E (劉鶚, Liu O), Chinese scholar, entrepreneur and novelist (born 1857)
 * August 26 – George Manville Fenn, English novelist and educationalist (born 1831)
 * September 4 – Clyde Fitch, American playwright (born 1865)
 * September 19 – József Borovnyák, Slovene writer, politician and priest (born 1826)
 * October 16 – Jakub Bart-Ćišinski, Upper Sorbian poet, writer, playwright and translator (born 1856)
 * October 24 – Henry Charles Lea, American historian (born 1825)
 * November 5 – H. L. Fischer, Pennsylvania German-language writer and translator (born 1822)
 * November 18 – Renée Vivien, English-born French-language Symbolist poet (born 1877)
 * December 14 – Frederick Greenwood, English novelist and journalist (born 1830)

Awards

 * Chancellor's Gold Medal: Dennis Holme Robertson
 * Nobel Prize in Literature: Selma Lagerlöf (first female recipient)
 * Newdigate Prize: Frank Ashton-Gwatkin
 * Knighthood: Arthur Wing Pinero
 * Prix Goncourt: Marius-Ary Leblond, En France

title: 1909 in literature


text:
Talk:Outline of theatre

Untitled
I'd like to suggest that an article on theater slang might be useful. -- Infrogmation

I think there should be a list of famous theatres, past and present. Could be a long list, of course. -- Lee M

A very obscure page, but obviously the right place for this piece of information:

http://www.doollee.com see themselves as "the definitive guide to modern Playwrights and their Plays. This site lists information on over 29,500 Plays produced or published in English since 1956, the year when John Osborne's Look Back in Anger was first performed at the Royal Court in London. Doollee also provides details on over 8,700 Playwrights with links to Agents, Theatres and Bookstores."

They also ask users to help them gather information. Well, I tried to add something yesterday but was unable to find the "submit" button I had been referred to -- probably comes from editing too much at Wikipedia :) . --KF 23:33, 16 Nov 2003 (UTC)

Helping with this page
I remade this page into a list to make it easier to look at. My suggestion is to make three lists. Completed pages, stubs, and wanted pages.

If I have time, I'll come back and work on that.

 * DJKS 20:51, 28 Jun 2004 (UTC)

Rename proposal for this page and all the pages of the set this page belongs to
See the proposal at the Village pump

The Transhumanist 09:27, 4 July 2008 (UTC)

Guidelines for outlines
Guidelines for the development of outlines are being drafted at Outlines.

Your input and feedback is welcomed and encouraged.

The Transhumanist 00:31, 24 May 2009 (UTC)

The "History of" section needs links!
Please add some relevant links to the history section.

Links can be found in the "History of" article for this subject, in the "History of" category for this subject, or in the corresponding navigation templates. Or you could search for topics on Google - most topics turn blue when added to Wikipedia as internal links.

The Transhumanist 00:31, 24 May 2009 (UTC)

Straw poll and discussion concerning what outlines should be called
A discussion is underway that may affect the name of this article.

See: Wikipedia talk:Outlines

The Transhumanist 04:34, 20 October 2009 (UTC)

Middle Eastern Theatre
I'd like to suggest Middle Eastern Theatre link to its own page, as the Asian Theatre and African Theatre subheadings do. I'm willing to help develop this content, but not sure where it would go. Does one start the page first and then simply link to it? The 'Theatre' subheading in Arabic Literatures has some quite out of date information in it. Thanks. Purrform (talk) 00:27, 21 December 2012 (UTC)

Quick explanation of Wikipedia outlines
"Outline" is short for "hierarchical outline". There are two types of outlines: sentence outlines (like those you made in school to plan a paper), and topic outlines (like the topical synopses that professors hand out at the beginning of a college course). Outlines on Wikipedia are primarily topic outlines that serve 2 main purposes: they provide taxonomical classification of subjects showing what topics belong to a subject and how they are related to each other (via their placement in the tree structure), and as subject-based tables of contents linked to topics in the encyclopedia. The hierarchy is maintained through the use of heading levels and indented bullets. See Outlines for a more in-depth explanation. The Transhumanist 00:11, 9 August 2015 (UTC)

Added Definitions & Terms
I have added definitions and terms to this page. It seems no one has touched it since 2012. I've also gone through and cited quite a lot. I changed "Venue for Theatres" to "Types of Theatres" because venue is always a moot point for us in the Theatre World. I've also clarified that Theatre is always spelled "RE" and Theater is always the domain of film. I cited the Theatrical Guild of American on that as well. there are many more types of African Theatre. No mention is made of the Islands nor of the Middle East. While this is meant to be an outline, it should be as inclusive as possible and link to pages dedicated to African Theatre, Middle Eastern Theatre, etc. I am a writer and while I will try my utmost to contribute to this, please be aware that I am working on my second novel.

title: Talk:Outline of theatre


text:
Talk:Client

Untitled
I removed this line:

Today, virtually all systems are simultaneously client and server and the terms are amusing but of much less import.

It is just not true, and that's not just my opinion. Many systems, even modern systems still use the client/server model. IRC clients are operated by users to connect to IRC servers. Web browsers are HTTP clients that connect to web servers, or HTTP servers. The author of the snippet I removed was probably trying to imply that the client/server distinction was blurred with peer networking.

I also plan to remove "Of course" from the beginning of the article, since it implies the relation of client and server is obvious, whereas it might not be obvious for the reader.

cprompt 02:31 Feb 22, 2003 (UTC)

Disambiguation
Err... should this page be disambiguated? Graft 16:12, 2 May 2003 (UTC)

title: Talk:Client


text:
Alt.sex.stories

alt.sex.stories is a Usenet newsgroup for erotic stories created on May 7, 1992, by Tim Pierce as an alternative to pre-existing alt erotica newsgroups. The group was initially unmoderated, a feature that was not shared by some of the other Usenet or altnet newsgroups. This feature allowed for greater user freedom.

alt.sex.stories.moderated
In early 1997 a moderated version of alt.sex.stories was created due to an increasing number of posts by "various pay services, scam artists, and bots". During the twenty years in which it was active, the moderated newsgroup (ASSM) has always operated by cross-posting all approved stories to alt.sex.stories, and was not simply a filtered version of the unmoderated group. All stories posted to ASSM were specifically submitted there.

Day-to-day operations and general direction of ASSM were overseen by the Alt.Sex.Stories Text Repository (ASSTR), which coordinated a group of volunteers to moderate the newsgroup using a web-based voting system. ASSTR also hosts an archive of the newsgroup, and hosted a mirror of the Nifty Erotic Stories Archive (now located at nifty.org).

Eventually, ASSM became one of the few remaining active groups in the alt.sex.* hierarchy. Due to competition from web-based erotica sites and communities, the volume of stories posted to ASSM (and thus to alt.sex.stories) had dropped considerably by 2006. The group continued to be actively moderated until July 2017 but is no longer functional.

The asstr.org website was last updated in 2017 and is no longer stable, having dropped completely offline in July 2022 only to reappear (with no new content) in 2023. Much of the content is mirrored to other sites, but these may be severely out-of.date.

Notable authors
Alt.sex.stories is notable for assisting in the launch of several notable authors of erotica such as Elf Sternberg and Mary Anne Mohanraj.

Story codes
Because of the large volume of stories posted, a set of codes to describe the story content was developed. Writers were encouraged to include these story codes in the title of their stories.

title: Alt.sex.stories


text:
Verification

Verification or verify may refer to:

General

 * Verification and validation, in engineering or quality management systems, is the act of reviewing, inspecting or testing, in order to establish and document that a product, service or system meets regulatory or technical standards
 * Verification (spaceflight), in the space systems engineering area, covers the processes of qualification and acceptance
 * Verification theory, philosophical theory relating the meaning of a statement to how it is verified
 * Third-party verification, use of an independent organization to verify the identity of a customer
 * Authentication, confirming the truth of an attribute claimed by an entity, such as an identity
 * Forecast verification, verifying prognostic output from a numerical model
 * Verifiability (science), a scientific principle
 * Verification (audit), an auditing process

Computing

 * Punched card verification, a data entry step performed after keypunching on a separate, keyboard-equipped machine, such as the IBM 056 Verifier
 * Verification and validation (software)
 * Account verification, verifying that an account is owned by a real person or organization

Applications

 * CAPTCHA, device to verify that a user of a website is human, to prevent automated abuse
 * File verification, checking the formal correctness or integrity of a file
 * Speech verification, checking of the correct speaking of given sentences
 * VERIFY (DOS command)
 * GOV.UK Verify, identity assurance system in the United Kingdom

Software development

 * Formal verification, mathematical proof of the correctness of algorithms
 * Intelligent verification, automatically adapts the testbench to changes in RTL
 * Runtime verification, during execution
 * Software verification, an overview of techniques for verifying software

Circuit development

 * Hardware verification
 * Functional verification of design of digital hardware
 * Analog verification, applies to analog or mixed-signal hardware
 * Physical verification, design of a circuit

title: Verification


text:
Talk:Wife

deletion
What exactly is wrong with redirecting this stub to marriage? spouse redirects to marriage. husband redirects to marriage. All the content on this page is duplicated at marriage. Martin

I agree. I don't see any reason to have separate article for wife. -- Taku

 * I made this article mirror the former husband, which once read:

 * In traditional western cultures, a husband is the male spouse in a married couple.

 * I thought that if there were a stub here, it might reflect traditional disabilities on a wife, as a suggestion for some kind of meaningful content here. Since then, somebody made husband redirect to marriage.  While it does, it seems reasonable that wife should do the same.  In the meantime, though, someone attempted to begin doing what I suggested.  For this, I accept the whole blame.  ---Ihcoyc

The content here does not constitute a proper article. I am redirecting it to Marriage as it was before. Joie de Vivre 23:09, 12 February 2007 (UTC)

Reasons? WP:WINAD, for one, and the fact that it was short and largely unsourced were also problems. Simply put, it wasn't enough info for an article, and the Marriage article already covers it. The (stub) tag is in order, and you'd have to remove the POV pontification on what the "role of women" is. Why not either write a complete article, or leave well enough alone? Joie de Vivre 23:15, 12 February 2007 (UTC)

No, it's not a dictionary. So propose a merge and let's vote, i think there are a number of reasons to have a seperate article.Rights of a wife within a marriage AND society, relation to the family members, history... Marriage, then, would cover the rights of the marriage in society... and so onFlammingoParliament 23:22, 12 February 2007 (UTC)

 * Sure, but you haven't done any of that. You've cobbled together a Charlie Brown Christmas Tree of an article using a dictionary and your own mind as your only sources.  Here's some of the content you invented:
 * For the development of women in their position in society, see woman.
 * Role in a marriage: A marriage might take many forms, like polygamy, though the role of a woman as a female spouse is destined (or at least might be influenced) by her ability to bear children.
 * This really should be redirected to the Marriage article, there is so little content. Joie de Vivre 23:27, 12 February 2007 (UTC)

Deleting fact tags
User:Flammingo has at least twice deleted the fact tags I placed on unsourced content. This is inappropriate behavior. Joie de Vivre 18:19, 13 February 2007 (UTC)
 * you gotta be kiddingFlammingoParliament 20:05, 13 February 2007 (UTC)

Remain Calm

From an outsiders perspective...It seems that at this point you guys are argueing for the sake of argument. Lets remember that wikipedia is not here for the editors. Wikipedia is here for outside viewers to get information quickly and efficiently. Wikipedia is always growing, and if someone wants information on 'wife' 'husband' blah blah blah. There is nothing wrong with having articles that directly correlate to the terms 'wife' 'husband' 'mother' 'father' etc etc etc. If someone comes to wikipedia looking for information on specifically a husband or wife, then as editors we should oblige them. Now lets all go have a coke and a smile. :-) Thank you for looking out! OfForByThePeople 19:34, 13 February 2007 (UTC)

"Christian Europe" and "Islam"
These two sections are entirely unsourced and seem to be the product of User:Flammingo's mind. I've added the Disputed template to these sections. Should we even have a section called "Christian Europe"? Joie de Vivre 19:37, 13 February 2007 (UTC)

 * I see what you mean, but maybe he should be given some time to properly source his statements, and the opportunity to create a new article before deleting, and if he can't fix this improperly cited, and poorly structured article. Then delete it, but maybe we should first see if he can make something of it.

 * If he can't then it looks like he wont be having a coke and a smile. :-) Thank you for looking out! OfForByThePeople 19:48, 13 February 2007 (UTC)
 * taking a gulp of coke* ;-)FlammingoParliament 20:08, 13 February 2007 (UTC)

 * Thanks for lightening the mood. Joie de Vivre 20:13, 13 February 2007 (UTC)

Could we have an actual citation for the case of a Muslim beating his wife in Germany? The case sounds implausible, suggesting there are details missing in the article. Paladinwannabe2 14:30, 14 May 2007 (UTC)
 * I've changed the paragraph a bit and hope it sounds better now.--FlammingoHey 14:52, 14 May 2007 (UTC)
 * Ok, it looks like the divorce was not rejected, an accelerated divorce was rejected. There was quite the fuss over it too, and I imagine the lady's appeal was successful.  It seems like a single crackpot judge, going against German legal tradition, much to the annoyance of her fellow citizens.  I'm going to remove it.  You can put it back if you find citiations and a reason that it helps the article.Paladinwannabe2 14:39, 14 May 2007 (UTC)
 * I will double-check, but it might have been an accelerated one; still, the support of domestic violence based on Islamic Law was what critics meant, since she was forced to have keep in touch with her husband, knowing he was threatening her. For the role of a wife, most essential. --FlammingoHey 14:56, 14 May 2007 (UTC)

Tags and Novels
Jane Austen and Daniel Defoe wrote the novels not purely fictional; Most 18th century novelists added a preface to elaborate their position. The social criticism, in this context the rights of a wife, is well present in the nonfictional parts. Please elaborate why a novel must not be a source. thank you. FlammingoParliament 21:28, 13 February 2007 (UTC)

Using Tags as part of a content dispute is silly - isn't it? Lets talk about the content here, and not resort to nasty sticky labels.... I'll take them off for now... Petesmiles 21:36, 13 February 2007 (UTC)

My feeling is also that this article has far too many references. When references get in the way of reading the thing, it's a problem. Perhaps we could consolidate many of them - they are mainly citing material most would consider uncontroversial. Petesmiles 21:39, 13 February 2007 (UTC)

 * I don't think novels are appropriate factual references. Reinstated templates.  Joie de Vivre 21:50, 13 February 2007 (UTC)

 * That makes me smile, uncontroversial. You'd think. And OR would mean i talked to those Mediaeval Nuns and made that all up by myself. You wouldn't think that, considering the material. Novels CANNOT be "OR", they are the authors opinion of his world, not my opinion of his. FlammingoParliament 21:55, 13 February 2007 (UTC)

 * But the novels do not stand as reliable sources, so they cannot be used for citation here. Without citation, the statements are uncited, and there may still be original research there. I'm bringing back the tags. — coe l acan t a lk  — 22:05, 13 February 2007 (UTC) edit: I see the tags are already back. — coe l acan  t a lk  — 22:06, 13 February 2007 (UTC)

 * I dont get why Defoe and Austen are unreliable authors.FlammingoParliament 22:22, 13 February 2007 (UTC)
 * And what is the guideline of OR that forbids novel authors as a reference? Could you elaborate a bit, a "x", which is shown in Defoe's "y"FlammingoParliament 22:26, 13 February 2007 (UTC)

As far as the novels go. I have to agree that those are not great sources. Try to find outside studies of the authors work, which verify the authors accuracy. I mean, when you watch a movie and it says "Based on a true story" you cannot rely on the movies truthiness (is that a word?) until you put in work to separate fact from fiction. Reviews and critics are not hard to find (most of the time)

Take some time, do some research, and dont worry about what others do to the article for now...you can revert the entire article with your great new sources with the click of One button.

I have a confession...I only drink Dr Pepper and this is an endorsement. Thank you for looking out! OfForByThePeople 00:42, 14 February 2007 (UTC)

New Format
I have to give it to you Flammingo this looks great. Lets all work together and make this into something really good! If any other people have recommendations or objections please discuss them here first on the talk page, because I believe common ground can always be found and remember to drink Dr Pepper Thank you for looking out! OfForByThePeople 05:29, 7 March 2007 (UTC)

Hinduism
The ip 122.164.62.48 did a wonderful job writing the hinduism section. Unfortunatly, it may be claimed that the section "missed the point": down to the word choice, it says "marriages are..." "boy and girl..." so this should go to marriage#hinduism. Since those guys over there have a vendetta about most things, that seems unlikely, because it would need to be restructured like this one is. Apart from the lack of sources and the English used, I ask (are you there, offforbythepeople?) whether and how we could take the bits out that give information ONLY about the wife, not about marriage. --FlammingoHey 18:19, 11 April 2007 (UTC)

In the Hindusim section it says, "A wife loses even her identity for sake of his man." Shouldn't it be "her man?" I just wanted to make sure it was a mistake before changing it. Isis4563 22:17, 12 April 2007 (UTC)

So, this sounds like "wedding", and might need some polishing before it is reinserted: ''If discussions were fruitfull, majority will look into astrological charts of both the boy and girl. Those astrological charts were based on statistical data collection done by Indian ancestors. It covers 10 major check for match between a boy and girl, which includes Sexual match also) will be 90% accurate (atleast in my marriage, it is 99% accurate). If the astrological charts were matching, the photos of both boy and girl will be shown to each other. If the photos are ok, they ask the parent of girl to bring the girl to a common place like temples, park or beach. The parent of the boy will look the girl with out the her notice. If they are satisfied with her, they keep flowers on Girl's hair and they fix the engagement dates. The boy may or may not get a chance to meet her girl till Engagement (a ceremony before marriage). The idea behind the parents seeing the girl, with out her notice is to avoid hurting the girl's feeling, if the results were negative. If every thing is positive, both parents call all their relatives and neighbours, they fix a community Hall and celebrate marriage ceremony.''

This part I don't get, where is that from: ''The wife basic character changes a lot after marriage in order to adjust with the man. Those who dont adjust are tend to fail or dominate. '' this is on husband:Husbands are responsible for maintaining the finacial status of a family and they protect his wife, child and age old parents against external dangers. I still would prefer a source, this is likely to be tagged (ie removed). --FlammingoHey 22:47, 12 April 2007 (UTC)

Incoherent Sentence
I have very little idea of what the following is trying to say or how to revise it. Does anyone else? "One other option was to buy access into a cloister as a nun, also called a "bride to Jesus", consequently being a "bride of Jesus" to support her chastity, and being economically protected. Until late in the 20th century, women could in some cultures or times sue a man for wreath money when he took her virginity without taking her as his wife.LCP 00:44, 22 May 2007 (UTC)

 * Sure, do you like it better now? --FlammingoHey 15:29, 18 June 2007 (UTC)

Christianity?
We have Islam and Hinduism but not Christianity in this article. For that matter, we don't have Buddhism either. Can someone with appropriate knowledge expand upon these? And no, Europe is not the same as Christian! —The preceding unsigned comment was added by Special:Contributions/ (talk)
 * That would be me ;-) Changed.--FlammingoHey 21:51, 22 August 2007 (UTC)

Marriage vs. Religion
I don't believe the connection between religions and form of marriage is as close as the article currently suggests. These things hardly split exactly along religion lines, and there are many many more cultures and customs related to marriage than there are major religions. I suggest having one section in which marriage is discussed in relation to (main) religion, and another (potentially much more detailed) where different existing forms of marriage and their consequences wrt property, family relationships, name and other similar things are explained. —The preceding unsigned comment was added by Special:Contributions/ (talk)
 * Bringing in all customs about "wives" (remember: not "marriage"!!) in the world to one page would certainly be a problem, don't you think?--FlammingoHey 18:42, 21 February 2010 (UTC)

Etymology
Might I suggest using the OED or, better yet, the Oxford Dictionary of English Etymology (ODEE) as a source for the etymology of wife? Using this page is a poor choice for two reasons: it's not in English (and this is the English Wikipedia) and, more importantly, it's non-authoritative, or at least not as authoritative as Oxford. Thoughts? If no one has a problem with this, I'll update the etymology to match the ODEE (and/or OED where applicable). Dr. C.S. Lewis-Barrie, Ph.D. (talk) 18:17, 28 January 2008 (UTC)
 * You're absolutely right. Do it. Wrad (talk) 18:20, 28 January 2008 (UTC)
 * I shall begin work on this etymology. Please check this entry to keep tabs on progress. I'll update this article when the work is complete. Dr. C.S. Lewis-Barrie, Ph.D. (talk) 19:27, 28 January 2008 (UTC)
 * Remember Bartleby's already in it!--FlammingoHey 18:38, 21 February 2010 (UTC)

Vandalism
Can someone PLEASE get rid of that blatant vandalism called "USES" ?

lead
I propose to combine the first two sentences from “A wife is a female lifetime partner in a continuing marital relationship. A wife may also be referred to as a spouse” into: “A wife is a female spouse.” The main reason is that “spouse” is gender-neutral, whereas the second sentence in the above (current version) implies that “wife” and “spouse” are synonyms. What do you think? 71.178.188.47 (talk) 14:08, 15 February 2013 (UTC)

Woman instead of Female
The article starts with the phrase "A wife is a female lifetime partner in a continuing marital relationship.". In my opinion, it would be better if the article was referring to the gender, stating "A wife is a woman lifetime partner in a continuing marital relationship.", and no to the sex. Taliandr (talk) 20:10, 18 February 2013 (UTC)

What we ll do with wife Tasibul (talk) 07:20, 6 April 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 2 external links on Wife. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20140824032832/http://wbl.worldbank.org/~/media/FPDKM/WBL/Documents/Reports/2014/Women-Business-and-the-Law-2014-Key-Findings.pdf to http://wbl.worldbank.org/~/media/FPDKM/WBL/Documents/Reports/2014/Women-Business-and-the-Law-2014-Key-Findings.pdf
 * Added archive https://web.archive.org/web/20160304092212/http://www.tandf.co.uk/journals/explore/cmcf-vsi-women-in-france.pdf to http://www.tandf.co.uk/journals/explore/cmcf-vsi-women-in-france.pdf
 * Added tag to http://www.findarticles.com/p/articles/mi_m2005/is_3_33/ai_61372238

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 10:34, 24 May 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 4 external links on Wife. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20070712030304/http://www.futureofchildren.org/information2827/information_show.htm?doc_id=290368 to http://www.futureofchildren.org/information2827/information_show.htm?doc_id=290368
 * Added archive https://web.archive.org/web/20070712030304/http://www.futureofchildren.org/information2827/information_show.htm?doc_id=290368 to http://www.futureofchildren.org/information2827/information_show.htm?doc_id=290368
 * Added archive https://web.archive.org/web/20070220202903/http://www.seniorlaw.com/fishman.htm to http://www.seniorlaw.com/fishman.htm
 * Added archive https://web.archive.org/web/20150924085957/http://www.renaissance.com.pk/novq12y1.html to http://www.renaissance.com.pk/novq12y1.html

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 22:57, 6 December 2017 (UTC)

title: Talk:Wife


text:
Hindu astrology

Hindu astrology, also called Indian astrology, Jyotisha (ज्योतिष; ) and, more recently, Vedic astrology, is the traditional Hindu system of astrology. It is one of the six auxiliary disciplines in Hinduism that is connected with the study of the Vedas.

The Vedanga Jyotisha is one of the earliest texts about astronomy within the Vedas. Some scholars believe that the horoscopic astrology practised in the Indian subcontinent came from Hellenistic influences. However, this is a point of intense debate, and other scholars believe that Jyotisha developed independently, although it may have interacted with Greek astrology.

The scientific consensus is that astrology is a pseudoscience.

Etymology
Jyotisha, states Monier-Williams, is rooted in the word Jyotish, which means light, such as that of the sun or the moon or heavenly body. The term Jyotisha includes the study of astronomy, astrology and the science of timekeeping using the movements of astronomical bodies. It aimed to keep time, maintain calendars, and predict auspicious times for Vedic rituals.

History and core principles
Jyotiṣa is one of the Vedāṅga, the six auxiliary disciplines used to support Vedic rituals. Early jyotiṣa is concerned with the preparation of a calendar to determine dates for sacrificial rituals, with nothing written regarding planets. There are mentions of eclipse-causing "demons" in the Atharvaveda and Chāndogya Upaniṣad, the latter mentioning Rāhu (a shadow entity believed responsible for eclipses and meteors). The term graha, which is now taken to mean the planet, originally meant demon. The Ṛigveda also mentions an eclipse-causing demon, Svarbhānu. However, the specific term graha was not applied to Svarbhānu until the later Mahābhārata and Rāmāyaṇa.

The foundation of Hindu astrology is the notion of bandhu of the Vedas (scriptures), which is the connection between the microcosm and the macrocosm. The practice relies primarily on the sidereal zodiac, which differs from the tropical zodiac used in Western (Hellenistic) astrology in that an ayanāṃśa adjustment is made for the gradual precession of the vernal equinox. Hindu astrology includes several nuanced sub-systems of interpretation and prediction with elements not found in Hellenistic astrology, such as its system of lunar mansions (Nakṣatra). It was only after the transmission of Hellenistic astrology that the order of planets in India was fixed in that of the seven-day week. Hellenistic astrology and astronomy also transmitted the twelve zodiacal signs beginning with Aries and the twelve astrological places beginning with the ascendant. The first evidence of the introduction of Greek astrology to India is the Yavanajātaka which dates to the early centuries CE. The Yavanajātaka (lit. "Sayings of the Greeks") was translated from Greek to Sanskrit by Yavaneśvara during the 2nd century CE, and is considered the first Indian astrological treatise in the Sanskrit language. However the only version that survives is the verse version of Sphujidhvaja which dates to AD 270. The first Indian astronomical text to define the weekday was the Āryabhaṭīya of Āryabhaṭa (born AD 476).

According to Michio Yano, Indian astronomers must have been occupied with the task of Indianizing and Sanskritizing Greek astronomy during the 300 or so years between the first Yavanajataka and the Āryabhaṭīya. The astronomical texts of these 300 years are lost. The later Pañcasiddhāntikā of Varāhamihira summarizes the five known Indian astronomical schools of the sixth century. Indian astronomy preserved some of the older pre-Ptolemaic elements of Greek astronomy.

The main texts upon which classical Indian astrology is based are early medieval compilations, notably the Bṛhat Parāśara Horāśāstra, and Sārāvalī by. The Horāshastra is a composite work of 71 chapters, of which the first part (chapters 1–51) dates to the 7th to early 8th centuries and the second part (chapters 52–71) to the later 8th century. The Sārāvalī likewise dates to around 800 CE. English translations of these texts were published by N. N. Krishna Rau and V. B. Choudhari in 1963 and 1961, respectively.

Modern Hindu astrology
Astrology remains an important facet of folk belief in the contemporary lives of many Hindus. In Hindu culture, newborns are traditionally named based on their jyotiṣa charts (Kundali), and astrological concepts are pervasive in the organization of the calendar and holidays, and in making major decisions such as those about marriage, opening a new business, or moving into a new home. Many Hindus believe that heavenly bodies, including the planets, have an influence throughout the life of a human being, and these planetary influences are the "fruit of karma". The Navagraha, planetary deities, are considered subordinate to Ishvara (the Hindu concept of a supreme being) in the administration of justice. Thus, it is believed that these planets can influence earthly life.

Astrology as a science
Astrology has been rejected by the scientific community as having no explanatory power for describing the universe. Scientific testing of astrology has been conducted, and no evidence has been found to support any of the premises or purported effects outlined in astrological traditions. There is no mechanism proposed by astrologers through which the positions and motions of stars and planets could affect people and events on Earth. In spite of its status as a pseudoscience, in certain religious, political, and legal contexts, astrology retains a position among the sciences in modern India.

India's University Grants Commission and Ministry of Human Resource Development decided to introduce "Jyotir Vigyan" (i.e. ) or "Vedic astrology" as a discipline of study in Indian universities, stating that "vedic astrology is not only one of the main subjects of our traditional and classical knowledge but this is the discipline, which lets us know the events happening in human life and in universe on time scale" in spite of the complete lack of evidence that astrology actually does allow for such accurate predictions. The decision was backed by a 2001 judgement of the Andhra Pradesh High Court, and some Indian universities offer advanced degrees in astrology. This was met with widespread protests from the scientific community in India and Indian scientists working abroad. A petition sent to the Supreme Court of India stated that the introduction of astrology to university curricula is "a giant leap backwards, undermining whatever scientific credibility the country has achieved so far".

In 2004, the Supreme Court dismissed the petition, concluding that the teaching of astrology did not qualify as the promotion of religion. In February 2011, the Bombay High Court referred to the 2004 Supreme Court ruling when it dismissed a case which had challenged astrology's status as a science. despite continuing complaints by scientists, astrology continues to be taught at various universities in India, and there is a movement in progress to establish a national Vedic University to teach astrology together with the study of tantra, mantra, and yoga.

Indian astrologers have consistently made claims that have been thoroughly debunked by skeptics. For example, although the planet Saturn is in the constellation Aries roughly every 30 years (e.g. 1909, 1939, 1968), the astrologer Bangalore Venkata Raman claimed that "when Saturn was in Aries in 1939 England had to declare war against Germany", ignoring all the other dates. Astrologers regularly fail in attempts to predict election results in India, and fail to predict major events such as the assassination of Indira Gandhi. Predictions by the head of the Indian Astrologers Federation about war between India and Pakistan in 1982 also failed.

In 2000, when several planets happened to be close to one another, astrologers predicted that there would be catastrophes, volcanic eruptions and tidal waves. This caused an entire sea-side village in the Indian state of Gujarat to panic and abandon their houses. The predicted events did not occur and the vacant houses were burgled.

Texts
The ancient extant text on Jyotisha is the Vedanga-Jyotisha, which exists in two editions, one linked to Rigveda and other to Yajurveda. The Rigveda version consists of 36 verses, while the Yajurveda recension has 43 verses of which 29 verses are borrowed from the Rigveda. The Rigveda version is variously attributed to sage Lagadha, and sometimes to sage Shuci. The Yajurveda version credits no particular sage, has survived into the modern era with a commentary of Somakara, and is the more studied version.

The Jyotisha text Brahma-siddhanta, probably composed in the 5th century CE, discusses how to use the movement of planets, sun and moon to keep time and calendar. This text also lists trigonometry and mathematical formulae to support its theory of orbits, predict planetary positions and calculate relative mean positions of celestial nodes and apsides. The text is notable for presenting very large integers, such as 4.32 billion years as the lifetime of the current universe.

The ancient Hindu texts on Jyotisha only discuss time keeping, and never mention astrology or prophecy. These ancient texts predominantly cover astronomy, but at a rudimentary level. Technical horoscopes and astrology ideas in India came from Greece and developed in the early centuries of the 1st millennium CE. Later medieval era texts such as the Yavana-jataka and the Siddhanta texts are more astrology-related.

Discussion
The field of Jyotisha deals with ascertaining time, particularly forecasting auspicious day and time for Vedic rituals. The field of Vedanga structured time into Yuga which was a 5-year interval, divided into multiple lunisolar intervals such as 60 solar months, 61 savana months, 62 synodic months and 67 sidereal months. A Vedic Yuga had 1,860 tithis (तिथि, dates), and it defined a savana-day (civil day) from one sunrise to another.

The Rigvedic version of Jyotisha may be a later insertion into the Veda, states David Pingree, possibly between 513 and 326 BCE, when Indus valley was occupied by the Achaemenid from Mesopotamia. The mathematics and devices for time keeping mentioned in these ancient Sanskrit texts, proposes Pingree, such as the water clock may also have arrived in India from Mesopotamia. However, Yukio Ohashi considers this proposal as incorrect, suggesting instead that the Vedic timekeeping efforts, for forecasting appropriate time for rituals, must have begun much earlier and the influence may have flowed from India to Mesopotamia. Ohashi states that it is incorrect to assume that the number of civil days in a year equal 365 in both Hindu and Egyptian–Persian year. Further, adds Ohashi, the Mesopotamian formula is different from the Indian formula for calculating time, each can only work for their respective latitude, and either would make major errors in predicting time and calendar in the other region. According to Asko Parpola, the Jyotisha and luni-solar calendar discoveries in ancient India, and similar discoveries in China in "great likelihood result from convergent parallel development", and not from diffusion from Mesopotamia.

Kim Plofker states that while a flow of timekeeping ideas from either side is plausible, each may have instead developed independently, because the loan-words typically seen when ideas migrate are missing on both sides as far as words for various time intervals and techniques. Further, adds Plofker, and other scholars, that the discussion of time keeping concepts are found in the Sanskrit verses of the Shatapatha Brahmana, a 2nd millennium BCE text. Water clock and sun dials are mentioned in many ancient Hindu texts such as the Arthashastra. Some integration of Mesopotamian and Indian Jyotisha-based systems may have occurred in a roundabout way, states Plofker, after the arrival of Greek astrology ideas in India.

The Jyotisha texts present mathematical formulae to predict the length of day time, sun rise and moon cycles. For example,

 * The length of daytime = $$\left(12 + \frac{2}{61}n \right)$$ muhurtas
 * where n is the number of days after or before the winter solstice, and one muhurta equals $1/30$ of a day (48 minutes).

 Water clock A prastha of water [is] the increase in day, [and] decrease in night in the [sun's] northern motion; vice versa in the southern. [There is] a six-muhurta [difference] in a half year.

— Yajurveda Jyotisha-vedanga 8, Translator: Kim Plofker

Elements
There are sixteen Varga (, 'part, division'), or divisional, charts used in Hindu astrology:

Zodiac
The Nirayana, or sidereal zodiac, is an imaginary belt of 360 degrees, which, like the Sāyana, or tropical zodiac, is divided into 12 equal parts. Each part (of 30 degrees) is called a sign or rāśi (Sanskrit: 'part'). Vedic (Jyotiṣa) and Western zodiacs differ in the method of measurement. While synchronically, the two systems are identical, Jyotiṣa primarily uses the sidereal zodiac (in which stars are considered to be the fixed background against which the motion of the planets is measured), whereas most Western astrology uses the tropical zodiac (the motion of the planets is measured against the position of the Sun on the spring equinox). After two millennia, as a result of the precession of the equinoxes, the origin of the ecliptic longitude has shifted by about 30 degrees. As a result, the placement of planets in the Jyotiṣa system is roughly aligned with the constellations, while tropical astrology is based on the solstices and equinoxes.

Nakṣhatras, or lunar mansions

The nakshatras or lunar mansions are 27 equal divisions of the night sky used in Hindu astrology, each identified by its prominent star(s).

Historical (medieval) Hindu astrology enumerated either 27 or 28 nakṣatras. In modern astrology, a rigid system of 27 nakṣatras is generally used, each covering 13° 20′ of the ecliptic. The missing 28th nakshatra is Abhijeeta. Each nakṣatra is divided into equal quarters or padas of 3° 20′. Of greatest importance is the Abhiśeka Nakṣatra, which is held as king over the other nakṣatras. Worshipping and gaining favour over this nakṣhatra is said to give power to remedy all the other nakṣatras, and is of concern in predictive astrology and mitigating Karma.

The junction of two Râshis as well as Nakshatras is known as Gandanta.

Daśās – planetary periods
The word dasha (Devanāgarī: दशा, Sanskrit,, 'planetary period') means 'state of being' and it is believed that the daśā largely governs the state of being of a person. The Daśā system shows which planets may be said to have become particularly active during the period of the Daśā. The ruling planet (the Daśānātha or 'lord of the Daśā') eclipses the mind of the person, compelling him or her to act per the nature of the planet.

There are several dasha systems, each with its own utility and area of application. There are Daśās of grahas (planets) as well as Daśās of the Rāśis (zodiac signs). The primary system used by astrologers is the Viṁśottarī Daśā system, which has been considered universally applicable in the Kali Yuga to all horoscopes.

The first Mahā-Daśā is determined by the position of the natal Moon in a given Nakṣatra. The lord of the Nakṣatra governs the Daśā. Each Mahā-Dāśā is divided into sub-periods called bhuktis, or antar-daśās, which are proportional divisions of the maha-dasa. Further proportional sub-divisions can be made, but error margins based on accuracy of the birth time grow exponentially. The next sub-division is called pratyantar-daśā, which can in turn be divided into sookshma-antardasa, which can in turn be divided into praana-antardaśā, which can be sub-divided into deha-antardaśā. Such sub-divisions also exist in all other Daśā systems.

Heavenly bodies
The navagraha (नवग्रह) are the nine celestial bodies used in Hindu astrology:
 * Surya (Sun)
 * Chandra (Moon)
 * Budha (Mercury)
 * Shukra (Venus)
 * Mangala (Mars)
 * Bṛhaspati or Guru (Jupiter)
 * Shani (Saturn)
 * Rahu (North node of the Moon)
 * Ketu (South node of the Moon)

The navagraha are said to be forces that capture or eclipse the mind and the decision making of human beings. When the grahas are active in their daśās, or periodicities they are said to be particularly empowered to direct the affairs of people and events.

Planets are held to signify major details, such as profession, marriage and longevity. Of these indicators, known as Karakas, Parashara considers Atmakaraka most important, signifying broad contours of a person's life.

Rahu and Ketu correspond to the points where the moon crosses the ecliptic plane (known as the ascending and descending nodes of the moon). Classically known in Indian and Western astrology as the "head and tail of the dragon", these planets are represented as a serpent-bodied demon beheaded by the Sudarshan Chakra of Vishnu after attempting to swallow the sun. They are primarily used to calculate the dates of eclipses. They are described as "shadow planets" because they are not visible in the night sky. Rahu and Ketu have an orbital cycle of 18 years and they are always retrograde in motion and 180 degrees from each other.

Gocharas – transits
A natal chart shows the position of the grahas at the moment of birth. Since that moment, the grahas have continued to move around the zodiac, interacting with the natal chart grahas. This period of interaction is called gochara (Sanskrit: , 'transit').

The study of transits is based on the transit of the Moon (Chandra), which spans roughly two days, and also on the movement of Mercury (Budha) and Venus (Śukra) across the celestial sphere, which is relatively fast as viewed from Earth. The movement of the slower planets – Jupiter (Guru), Saturn (Śani) and Rāhu–Ketu — is always of considerable importance. Astrologers study the transit of the Daśā lord from various reference points in the horoscope.

Yogas – planetary combinations
In Hindu astronomy, yoga (Sanskrit: , 'union') is a combination of planets placed in a specific relationship to each other.

Rāja yogas are perceived as givers of fame, status and authority, and are typically formed by the association of the Lord of Keṅdras ('quadrants'), when reckoned from the Lagna ('ascendant'), and the Lords of the Trikona ('trines', 120 degrees—first, fifth and ninth houses). The Rāja yogas are culminations of the blessings of Viṣṇu and Lakṣmī. Some planets, such as Mars for Leo Lagna, do not need another graha (or Navagraha, 'planet') to create Rājayoga, but are capable of giving Rājayoga by themselves due to their own lordship of the 4th Bhāva ('astrological house') and the 9th Bhāva from the Lagna, the two being a Keṅdra ('angular house'—first, fourth, seventh and tenth houses) and Trikona Bhāva respectively.

Dhana Yogas are formed by the association of wealth-giving planets such as the Dhaneśa or the 2nd Lord and the Lābheśa or the 11th Lord from the Lagna. Dhana Yogas are also formed due to the auspicious placement of the Dārāpada (from dara, 'spouse' and pada, 'foot'—one of the four divisions—3 degrees and 20 minutes—of a Nakshatra in the 7th house), when reckoned from the Ārūḍha Lagna (AL). The combination of the Lagneśa and the Bhāgyeśa also leads to wealth through the Lakṣmī Yoga.

Sanyāsa Yogas are formed due to the placement of four or more grahas, excluding the Sun, in a Keṅdra Bhāva from the Lagna.

There are some overarching yogas in Jyotiṣa such as Amāvasyā Doṣa, Kāla Sarpa Yoga-Kāla Amṛta Yoga and Graha Mālika Yoga that can take precedence over Yamaha yogar planetary placements in the horoscope.

Bhāvas – houses
The Hindu Jātaka or Janam Kundali or birth chart, is the Bhāva Chakra (Sanskrit: 'division' 'wheel'), the complete 360° circle of life, divided into houses, and represents a way of enacting the influences in the wheel. Each house has associated kāraka (Sanskrit: 'significator') planets that can alter the interpretation of a particular house. Each Bhāva spans an arc of 30° with twelve Bhāvas in any chart of the horoscope. These are a crucial part of any horoscopic study since the Bhāvas, understood as 'state of being', personalize the Rāśis/ Râshis to the native and each Rāśi/ Râshi apart from indicating its true nature reveals its impact on the person based on the Bhāva occupied. The best way to study the various facets of Jyotiṣa is to see their role in chart evaluation of actual persons and how these are construed.

Dṛiṣṭis
Drishti (Sanskrit: , 'sight') is an aspect to an entire house. Grahas cast only forward aspects, with the furthest aspect being considered the strongest. For example, Jupiter aspects the 5th, 7th and 9th house from its position, Mars aspects the 4th, 7th, and 8th houses from its position, and its 8th house.

The principle of Drishti (aspect) was devised on the basis of the aspect of an army of planets as deity and demon in a war field. Thus the Sun, a deity king with only one full aspect, is more powerful than the demon king Saturn, which has three full aspects.

Aspects can be cast both by the planets (Graha Dṛṣṭi) and by the signs (Rāśi Dṛṣṭi). Planetary aspects are a function of desire, while sign aspects are a function of awareness and cognizance.

There are some higher aspects of Graha Dṛṣṭi (planetary aspects) that are not limited to the Viśeṣa Dṛṣṭi or the special aspects. Rāśi Dṛṣṭi works based on the following formulaic structure: all movable signs aspect fixed signs except the one adjacent, and all dual and mutable signs aspect each other without exception.

title: Hindu astrology


text:
Talk:Bytecode

untitled
Some pretentious people making something of nothing. Bytecode is nonsense (just invented to make your dicks seem bigger).This article is total tosh and needs completely re-writing in terms of hex vs binary and interpreting for virtual machines. Better still, delete it all. —Preceding unsigned comment added by 124.187.137.11 (talk) 12:39, 13 April 2009 (UTC)

Hey guys, you'd better point out some disadvantages of bytecode once you speak about its advantages!!

This article is, umm, rather incomprehensible to someone who doesn't already know everything about this topic. k.lee

Bytecode may be used as an intermediate code of a compiler, or may be the saved 'tokenized' form used by an interpreter

How can this sentence be related to virtual machine? -- HJH

Bytecode may be used as an intermediate code of a compiler, or may be the saved 'tokenized' form used by an interpreter or a virtual machine

"Byte code", "byte-code", and "bytecode" seem to be fighting it out. Specifically, there is an entry for the Java Bytecode. Anyone have a strong preference as to which the final version should be? Charles Merriam 21:10, 4 February 2006 (UTC)

 * Bytecode —Ruud 01:19, 11 February 2006 (UTC)

 * I also vote for bytecode; a quick Google search seems to confirm its greater popularity. More importantly, "The Java Virtual Machine Specification" by Lindholm and Yellin (1997) spells it "bytecode". This is surely the ultimate reference, at least for the Java version. --Mike Van Emmerik 12:37, 11 February 2006 (UTC)
 * Bytecode, definately. Wouter Lievens 12:51, 11 February 2006 (UTC)
 * Bytecode, I don't think "byte" works as an adjective njaard 15:16, 23 March 2006 (UTC)
 * Bytecode is more common. Obviously, make redirects. --Leapfrog314 04:58, 20 April 2006 (UTC)
 * Bytecode | Acaciz 18:01, 3 June 2006 (UTC)
 * Bytecode. ais523 16:55, 15 June 2006 (UTC)

 * Page moved. Eugène van der Pijll 21:14, 24 June 2006 (UTC)

"The current reference implementation of the Ruby programming language does not use bytecode, however it relies on tree-like structures which resemble intermediate representations used in compilers.". Is it relevant to talk about Ruby not using bytecode in this article? - Philoctet

incorrect use of term bytecode
I believe that this entire article is a misuse of the term bytecode. I have worked near machine level in computer science for many years, and in my experience, bytecode applies specifically to the Java Virtual Machine, whose instruction set does indeed consist of one-byte opcodes. For other programming languages, the correct term for what this article described is "intermediate language". Visual Basic compiles to an intermediate language, as did Pascal, Smalltalk, and others. These were NEVER to my knowledge called "bytecode."

I think this needs to be fixed, hopefully by the author of this article.

 * I agree. / HenkeB (talk) 21:40, 13 January 2008 (UTC)

I disagree. See http://www.google.com/search?hl=en&q=bytecode+-java&btnG=Search PuerExMachina (talk) 04:51, 14 January 2008 (UTC)

 * Ok, is there a fundamental difference between "bytecode" and other intermediate representations then, as you see it? / HenkeB (talk) 14:47, 14 January 2008 (UTC)

 * Yes an intermediary representation does not have to have it's tokens stored in a single byte per token. It's quite possible that a completely different scheme is used. A "bytecode" representation however, always uses a single byte for a single pseudo opcode token.Mahjongg (talk) 16:43, 14 January 2008 (UTC)

 * A quite superficial distinction then, if I understand you correctly? Sounds like, perhaps, this article should be renamed intermediate code with the word bytecode redirect here (instead of the other way round) - or better - create a separate one for intermediate code. However, I had the feeling this java-term had begun to mean just about any representation that is more similar (isomorph) to ordinary machine code than, say, tree-structured code, "quadruples", or stack code? / HenkeB (talk) 17:47, 14 January 2008 (UTC)

Smalltalk-80 used the term Bytecode as well, and, it was always a inconsistent notion. Smalltalk bytecode do not use a fixed size to encode opcodes, but 4bit to 8bit, and there are instructions which are encoded with 2byte. So,in essence, the term Bytecode is usually used to name a VM instruction set which is designed with a hardware instruction set architecture in mind. 2009-08-20 —Preceding unsigned comment added by 134.184.43.183 (talk) 12:09, 20 August 2009 (UTC)

Well, I will just comment that personally I find both this article, as well as the one on interpreters, to be rather vague / misleading.

For example, usually it is not "semantic analysis" (as I understand the term) which produces bytecode, rather, it is more commonly the process of flattening an AST which produces bytecode, with this process driving the remainder of the compiler logic, and often with little or no "semantic analysis" (at least for many dynamic languages, where most of this is left to be figured out at runtime).

As for Java and Bytecode, I think Java popularized the term, but they by no means own it. Generally, it refers to a byte-centric opcode-based structure, with 1 (or more) bytes for an opcode, and usually any arguments directly following. Usually, it is understood to be interpreted linearly as well (similar to machine code), and often handling control flow via offsets and jumps, rather than being tree or graph structured or using high-level control flow.

Its main property then is usually that of being similar to, but at the same time usually far less complex and bit-twiddly than, machine code (as well as traditionally interpreted or JIT-compiled rather than being directly run on a piece of hardware). —Preceding unsigned comment added by 174.18.204.116 (talk) 18:56, 2 October 2009 (UTC)

The focus should probably be on 'byte-oriented', in the sense of simplifying instruction decoding. The op-code is only one of several fields -- it is not a great benefit if the op-code is easy to extract, while other fields are complex. I've always thought the instruction encoding used for the EM-1 'machine' was a good example: opcode is one byte, escape sequence is one byte, and address fields is one or two bytes. There are a few exceptions where the instructions and arguments were encoded into one byte, but this was to speed execution of very common instructions. (See Informatica Report IR-81 (from 1983) by Andrew S Tanenbaum et al.: Description of a machine architecture for use with block structured languages.) Although the term 'bytecode' is not used by the authors, it has been used in descriptions of the Amsterdam Compiler Kit, of which EM-1 was a central concept.Athulin (talk) 09:46, 10 January 2011 (UTC)

Layman's terms
I have to agree with the above comments about how the article needs to be easier to understand. I'm a part-time developer for various languages for the past 10 years. And I don't even understand what byte-code is, nor has this article helped. I'm not suggesting we compromise and make a 'for dummies' article, but just add a sentence here and there to help clarify.

I also agree with this. Specifically, in the sentence, "Since it is processed by software, [bytecodes are] usually more abstract than machine code". In what sense is the word "abstract" being used? When comparing it to "machine code", do you mean more abstract than binary code or more abstract than assembly language? So, is bytecode higher level compared to one of these or lower level than one of these, or just different syntactically?

The following sentence is also similarly confusing: "Compared to source code (intended to be human-readable), bytecodes are less abstract, more compact, and more computer-centric."

From what I understand, being "more abstract" usually means lower level. So how could bytecode be more human readable (less abstract) but then more abstract than machine code??? From the current description, I interpret the former sentence to mean that Bytecode is lower level than assembly, or possibly, even lower level than binary, which isn't possible! I am also not familiar with how the word "computer-centric" is generally used when refering to levels of computer code, but I think this needs to be described more simply.

 * In normal computer terminology, the more abstract the code the further it is removed from the physical implementation on the hardware. Usually more abstract code is therefore easier for a human to understand in everyday concepts instead of machine concepts. -- RTC 18:47, 7 February 2007 (UTC)

Bytecode execution techniques?
This and virtual machine both don't explain any techniques used to execute bytecode. I've sketched some basic thoughts out on a blog entry of mine at KernelTrap; but I don't know how current day ones operate, if there's generally optimization, if instruction ordering counts, etc.

binary requirement
Could a textual language be considered bytecode? Obviously not, but this article lists CIL as an example of bytecode, and many other articles call it "bytecode". The article for CIL even calls it both "human-readable" and "bytecode". CIL example Herorev 21:22, 19 November 2006 (UTC)
 * It seems CIL is not in itself bytecode, but can be assembled into bytecode. So CIL itself is not a form of bytecode. The only "human readable bytecode" I can think of is one which just uses each letter of the alphabet were each letter stands for the mnemonic of one opcode, for example the letter 'G' (47Hex) for 'Goto'. That would be "readable", and would use one byte for each instruction. Mahjongg (talk) 11:57, 14 January 2008 (UTC)

 * Another human-readable bytecode: the original wiki mentions "sed scripts don't need to be tokenized; they already are ... All sed commands are one byte long, not including arguments. ... More languages than just sed have this property or a similar one." -- LittleLanguage. --68.0.124.33 (talk) 01:43, 25 October 2008 (UTC)

Old page history
For old page history that used to be at this title, see Talk:Bytecode/old. Graham 87 08:33, 5 February 2009 (UTC)

Merge neologisms
So far as I can tell, “bytecode” appears to be nothing but an euphemism for a slightly lower level Interpreted language. 72.235.213.232 (talk) 03:43, 19 June 2010 (UTC)

Bytecode vs. machine code
I have suggested that bytecode and machine code be merged on the machine code page's discussion page -- my point being that the two words are interchangeable in all cases and that there is no way to tell them apart nor do they in any way differ from one another. Bytecode langauges are just ordinary languages we pretend are not, by, implmenting them in software rather than hardware. There is no reason why any language cannot be run in hardware as well as software. There are plenty of example of hardware implementations of bytecode languages (various java processors) and software implementations of machine code languages (qemu, boch, vmware, etc.). Besides, the bytecode article appears mostly to be a list of example languages that are considered to be bytecode. I would also like to note that it is entirely possible to translate langauges which typically are translated into a "bytecode" language, into a "machine code" language and vice versa (GCJ for instance translates Java source code into native machine code. I'm certain you can find C compilers that target any particular "bytecode" machine). FrederikHertzum (talk) 13:35, 19 June 2010 (UTC)
 * The main difference is that bytecodes are specifically designed to run on systems independent of the native machine code of the system. You are right that the bytecode could be the native machine code, but that is often done to run such bytecode on a platform optimized to run it. bytecode is NOT the same thing as machinecode. Mahjongg (talk) 14:21, 19 June 2010 (UTC)
 * From a computer scientists point of view, there is no difference between a virtual or a real machine and their instruction sets are clearly equally powerful (given that both are Turing complete). My point is not what is being done, but the technical difference between the two terms, being that there is none. Being designed to be run on-top of another, unknown, machine is hardly a good criterion for distinction. FrederikHertzum (talk) 03:41, 21 June 2010 (UTC)
 * Keep Separate — Well, the difference is that a "virtual machine" needs a real machine... Also, all computer related articles cannot have an abstract computer "science" point of view; although basic principles are indeed important to clarify, real world usage, practical aspects, and conventions are equally (or more) important in most articles on computing, electronics and science. 83.255.42.68 (talk) 08:03, 26 July 2010 (UTC)
 * I'm not sure if this was correct from a computer science perspective. A 'virtual machine' (back in the 1970s or so, when I first got interested in compiler language) was non-existing hardware.  The MIX 'computer' used by Donald Knuth to teach and discuss certain aspects of computing was very much a virtual machine. Today a 'virtual machine'  is what then would probably have been called an 'emulated machine'. (See https://en.wikipedia.org/wiki/Stack_machine for several uses of 'virtual machine' used for stack-oriented designs.  The link from that article to 'virtual machine' however, is somewhat misleading, as it is not until the term 'Process virtual machines' that the intended meaning is beginning to emerge.  (That term is almost certainly a modern term.) Athulin (talk) 17:59, 29 November 2022 (UTC)
 * Not in my experience. In the 1970s a virtual machine was usually a machine with the same architecture as the host, running under, e.g., VM/370.
 * Also in that time frames, P-code was specifically UCSD p-code. I never heard the term byte code until Java. --Shmuel (Seymour J.) Metz Username:Chatul (talk) 08:09, 30 November 2022 (UTC)
 * Keep Separate — But this article needs to be refined and its category has to be determined. Is it related to virtual machines, interpreters, or process virtual machines? The page on VMs has to explain the type of code --Melab±1 ☎ 22:45, 19 June 2010 (UTC)
 * Keep Separate The term Bytecode has been in use ever since its canonical example (or maybe even earlier) of a byte-code in the form of the p-code used by UCSD Pascal, which was one of the contenders for an operating system for the upcoming IBM PC. So at the very least the term has historical significance. Mahjongg (talk) 17:52, 21 June 2010 (UTC)
 * This is a little strange. I don't know that anything deserves to be called bytecode more than VAX machine code. (And there are plenty of software implementations of VAX.) But also, I suspect the reason VAX went away, was that it uses a bytecode. VAX instructions can have from one to at least six operands. Each operand has a byte indicating the address mode for that argument. Depending on the address mode, that byte is followed by an appropriate number of bytes for that mode. It might be one to 60 bytes for an instruction. Like JVM code, it is well designed for processing one byte at a time. It is, however, extremely difficult to decode instructions in parallel. Very convenient for the microcoded VAX machines. The important distinction, then, is that it is convenient for processing one byte at a time, based on the state determined by earlier bytes. And especially, a large number of different modes depending on those bytes. Gah4 (talk) 09:23, 30 November 2022 (UTC)
 * The VAX-11/780 was hardly the first machine with variable length instructions, nor the first with complicated operand specifications. The Bendix G-20, GE 635 and RCA 601 have similar complexities in one way or another. A more modern example is the encoding of opcodes on IBM z/Architecture. The VAX was more influenced by the PDP-11 than by, e.g., UCSD p-code --Shmuel (Seymour J.) Metz Username:Chatul (talk) 14:25, 30 November 2022 (UTC)
 * Not the first, but maybe worst. It would have been a lot better for VAX to put all the address mode bytes immediately after the opcode byte. Until you get to an address mode byte, you don't know how long that address mode is. For S/370, and I believe z/, you know the instruction length from the first byte. For VAX, it is almost the last byte. Address modes can have a 0, 1, 2, 4, 8, or 16 byte immediate value. For z/, you know quickly where the next instruction starts, and can start decoding it in parallel. Or even that z/ instructions are always an even number of bytes. I suspect VAX would have been what Brooks calls a Second-system effect. The PDP-11 is nice and simple in many ways, that VAX is complicated. It isn't even easy to figure out what the longest VAX instruction is, with which addressing modes are allowed for which operands, of which instructions. (I believe you can't write to immediate operands, for example.) Gah4 (talk) 21:03, 30 November 2022 (UTC)
 * This is a little strange. I don't know that anything deserves to be called bytecode more than VAX machine code. (And there are plenty of software implementations of VAX.) But also, I suspect the reason VAX went away, was that it uses a bytecode. VAX instructions can have from one to at least six operands. Each operand has a byte indicating the address mode for that argument. Depending on the address mode, that byte is followed by an appropriate number of bytes for that mode. It might be one to 60 bytes for an instruction. Like JVM code, it is well designed for processing one byte at a time. It is, however, extremely difficult to decode instructions in parallel. Very convenient for the microcoded VAX machines. The important distinction, then, is that it is convenient for processing one byte at a time, based on the state determined by earlier bytes. And especially, a large number of different modes depending on those bytes. Gah4 (talk) 09:23, 30 November 2022 (UTC)
 * The VAX-11/780 was hardly the first machine with variable length instructions, nor the first with complicated operand specifications. The Bendix G-20, GE 635 and RCA 601 have similar complexities in one way or another. A more modern example is the encoding of opcodes on IBM z/Architecture. The VAX was more influenced by the PDP-11 than by, e.g., UCSD p-code --Shmuel (Seymour J.) Metz Username:Chatul (talk) 14:25, 30 November 2022 (UTC)
 * Not the first, but maybe worst. It would have been a lot better for VAX to put all the address mode bytes immediately after the opcode byte. Until you get to an address mode byte, you don't know how long that address mode is. For S/370, and I believe z/, you know the instruction length from the first byte. For VAX, it is almost the last byte. Address modes can have a 0, 1, 2, 4, 8, or 16 byte immediate value. For z/, you know quickly where the next instruction starts, and can start decoding it in parallel. Or even that z/ instructions are always an even number of bytes. I suspect VAX would have been what Brooks calls a Second-system effect. The PDP-11 is nice and simple in many ways, that VAX is complicated. It isn't even easy to figure out what the longest VAX instruction is, with which addressing modes are allowed for which operands, of which instructions. (I believe you can't write to immediate operands, for example.) Gah4 (talk) 21:03, 30 November 2022 (UTC)
 * Not the first, but maybe worst. It would have been a lot better for VAX to put all the address mode bytes immediately after the opcode byte. Until you get to an address mode byte, you don't know how long that address mode is. For S/370, and I believe z/, you know the instruction length from the first byte. For VAX, it is almost the last byte. Address modes can have a 0, 1, 2, 4, 8, or 16 byte immediate value. For z/, you know quickly where the next instruction starts, and can start decoding it in parallel. Or even that z/ instructions are always an even number of bytes. I suspect VAX would have been what Brooks calls a Second-system effect. The PDP-11 is nice and simple in many ways, that VAX is complicated. It isn't even easy to figure out what the longest VAX instruction is, with which addressing modes are allowed for which operands, of which instructions. (I believe you can't write to immediate operands, for example.) Gah4 (talk) 21:03, 30 November 2022 (UTC)
 * Not the first, but maybe worst. It would have been a lot better for VAX to put all the address mode bytes immediately after the opcode byte. Until you get to an address mode byte, you don't know how long that address mode is. For S/370, and I believe z/, you know the instruction length from the first byte. For VAX, it is almost the last byte. Address modes can have a 0, 1, 2, 4, 8, or 16 byte immediate value. For z/, you know quickly where the next instruction starts, and can start decoding it in parallel. Or even that z/ instructions are always an even number of bytes. I suspect VAX would have been what Brooks calls a Second-system effect. The PDP-11 is nice and simple in many ways, that VAX is complicated. It isn't even easy to figure out what the longest VAX instruction is, with which addressing modes are allowed for which operands, of which instructions. (I believe you can't write to immediate operands, for example.) Gah4 (talk) 21:03, 30 November 2022 (UTC)

Bytecode v8
Since Chrome 66, now V8 does partitally utilize bytecode. — Preceding unsigned comment added by 119.145.72.152 (talk) 04:17, 20 April 2019 (UTC)

List of examples
It seems to me like the list of examples will grow indefinitely, as most interpreters use bytecode as an intermediate representation for interpretation, including many of those which can also optionally produce native code or compile to another language (i.e. to C or LLVM). I can myself immediately think of various examples which are missing from the list, but am not sure it would be wise to add them... 76.10.128.192 (talk) 15:13, 5 July 2013 (UTC) It wouldn't.

Bytecode versus P-code
The article and DAB page for P code treat bytecode and P-codeas synonymous. However, I have never seen the term P-code used in the literature for anything but the code generated by UCSD Pascal. Shmuel (Seymour J.) Metz Username:Chatul (talk) 06:39, 31 May 2021 (UTC)

 * The UCSD people inherited the term from the the Zurich Pascal (or Pascal P) compiler, that was distributed to interested parties. The P4 version was released in 1976 or 1977.  I don't have Barron's book around (Pascal: The language and its implementation), but I think P-code was discussed in it as well. The Pascal-S subset (1975 or so) had a combined compiler/interpreter, based on a P code.Athulin (talk) 18:16, 6 November 2021 (UTC)

 * The term P-code is certainly confusing to me. It sounds very much like Pseudocode. I sure do not know what the P in P-code would be. The term P-code used in this context seems to be from a beginner that does not understand what they mean. Sam Tomato (talk) 11:41, 6 May 2022 (UTC)

 * It would be very understandable if a term such as pseudo-assembly code were used but I do not know how common that is. Sam Tomato (talk) 11:44, 6 May 2022 (UTC)

History of?
Bytecode. Came here looking for "history of". Is always a good lead in to understanding anything. Wanted to know who was first to implement it (or name 'bytecode'), subsequent implementations. Aspidistra9812 (talk) 03:57, 27 July 2021 (UTC)

 * I only have a suggestion: look for material coming out of the compilers / interpreters designed for portability starting in the 1960s, and usually based on the ideas of solving the M*N compiler problem (languages*architectures), which some researchers proposed to solve by defining a universal intermediate language between the M languages and the N computer architectures, making it into a M+N problem. When I hear the term I think of Algol 60 (Randall & Russell: Algol 60 implementation, (1964)), Smalltalk-80 and Pascal, and certainly the Amsterdam Compiler Kit (Andrew Tanenbaum). Tanenbaum's paper on the design of the EM-1 byte code ("DESCRIPTION OF A MACHINE ARCHITECTURE FOR USE WITH BLOCK STRUCTURED LANGUAGE", Informatica Report IR-81) is worth reading. It doesn't use the term 'byte code', but the instruction format is heavily byte-oriented for processing efficiency, and anyone knowing EM-1 would almost certainly interpret the term as a synonym for intermediate code based on the same design principles. At a stretch, Griswold's book on portable SNOBOL4 implementation might be relevant, perhaps also Lisp Machine stuff, and I vaguely remember another author who wrote a lot about portable code (Winter?). Barron's and Pemberton's books on Pascal implementation may also provides clues. Athulin (talk) 09:27, 20 October 2022 (UTC)
 * ... and interestingly enough I come on the https://en.wikipedia.org/wiki/Virtual_machine#History where the term 'O-Code' is used for one such intermediate language. It is possible, that the term P code is a reference back to O code: they seem to have been used in much the same way. Athulin (talk) 18:02, 29 November 2022 (UTC)

title: Talk:Bytecode


text:
User:Thatguy~enwiki

That Guy, From That Show! tgfts, That Guy tfgts, that guy from that show tfts grammarpalooza let's party naked 2006 wikipedia

User:That Guy, From That Show!

TGFTS, That Guy, From That Show!, That Guy, From That Show

tgfts, that guy from that show, that guy, that show, that guy from that show, that guy, from that show, tgfts

Hi there, this ia a dopple account (protection) for that guy, from that show aka tgfts, that guy, that show, etc... tgfts. Bold text

title: User:Thatguy~enwiki


text:
Future Crew

Future Crew was a Finnish demogroup that created PC demos and software, active mostly between 1987 and 1994.

History
The group was founded in 1986 by PSI (Sami Tammilehto) and JPM (Jussi Markula) as a Commodore 64 group, before moving to the PC demoscene in 1988; other members included, over time, Trug, Wildfire, Pixel, ICE, GORE, Abyss, Purple Motion, and Skaven, as well as several others.

Noteworthy demos by Future Crew include Unreal (released at Assembly 1992), Panic (released at The Party 1992) and Second Reality (released at Assembly 1993). Second Reality may be considered one of the most influential PC demos ever made. Future Crew was also responsible for the popular MOD editor Scream Tracker, which was fashioned after the Amiga Soundtracker as well as the Advanced DigiPlayer sound editor, and later became itself inspiration for other trackers like Impulse Tracker.

Future Crew was co-organizer of the first Assembly demo party in 1992, and continued organizing the annual party until 1995, when the organization set up the Finnish company ASSEMBLY Organizing in order to "provide a solid financial basis for the events and a reliable partner for our sponsors". Long time Future Crew member Abyss is one of the party's main organizers.

Future Crew did not release anything as a group after Scream Tracker 3 (July 1994). While it was never officially dissolved, its members parted ways in the second half of the 1990s. Companies like Futuremark (3DMark), Remedy (Death Rally, Max Payne, Alan Wake), Bugbear Entertainment (FlatOut, Glimmerati, Rally Trophy), Bitboys (a graphics hardware company) and Recoil Games (Rochard) were all started in whole or in part by members of Future Crew. Prior to their dissolution they also contributed graphics to the game Ken's Labyrinth published by Epic MegaGames. Skaven contributed music to Unreal Tournament 1999.

Reception and impact
Future Crew was an influential pioneer of the PC demoscene and the PC as multimedia device in general, and achieved wide public recognition.

Awards and tributes
Slashdot voted the Future Crew Demo Second Reality as one of the "Top 10 Hacks of All Time". Tributes to Future Crew include a 3D graphics benchmark called Final Reality by Remedy Entertainment (shown at Assembly 1997), and a remake of Second Reality for the Commodore 64 by Smash Designs called Second Reality 64 (released at The Party 1997). Nectarine Records has released a free-to-download album titled "Metropolis" containing the most known songs of Future Crew in 24-bit remastered as a tribute.

Members
These are the members of the group at the time it released Second Reality:

 * Gore (Samuli Syvähuoko): organizer
 * Psi (Sami Tammilehto): programmer
 * Trug (Mika Tuomi): programmer
 * Wildfire (Arto Vuori): programmer
 * Purple Motion (Jonne Valtonen): music
 * Skaven (Peter Hajba): music & graphics
 * Marvel (Aki Raula, formerly Aki Määttä): graphic artist
 * Pixel (Misko Iho) : graphic artist
 * Abyss (Jussi Laakkonen): BBS coordinator / public relations
 * Henchman (Markus Mäki): BBS operator
 * Jake (Jarkko Heinonen): Internet PR

Releases
Future Crew released the following productions on the PC demoscene :
 * GR8 (1988, demo)
 * YO! (1989, demo)
 * Slideshow I (1990, slideshow)
 * Scream Tracker 2 (1990, tool)
 * Mental Surgery (1991, demo)
 * Assembly '92 Invitation, aka. Fishtro (1992, invitation)
 * Unreal (1992, demo, 1st at Assembly 92)
 * Starport BBStro (1992, BBStro)
 * The Party 92 Invite (1992, invite)
 * Panic (1992, demo, 2nd at The Party 92)
 * Assembly '93 Invitation (1993, invitation)
 * Worldcharts #01 (1993, diskmag)
 * Second Reality (1993, 1st at Assembly 93)
 * Bussimatkaintro (1993, invitation)
 * Journey 1 (1993, musicdisk)
 * Journey 2 (1993, musicdisk)
 * Starport BBS Add 2 (1993, BBStro)
 * Chaotic Mind (1994, musicdisk)
 * Assembly '94 Pre-invitation (1994, invitation)
 * Assembly '94 Invitation (1994, invitation)
 * Soppa (1994, 64k demo)
 * Scream Tracker 3 (1994, tool)
 * Metropolis (2011, music compilation)

title: Future Crew


text:
Howard Hodgkin

Sir Gordon Howard Eliott Hodgkin (6 August 1932 – 9 March 2017) was a British painter and printmaker. His work is most often associated with abstraction.

Early life
Gordon Howard Eliot Hodgkin was born on 6 August 1932 in Hammersmith, London, the son of Eliot Hodgkin (1905–1973), a manager for the chemical company ICI and an amateur horticulturist, and his wife Katherine, a botanical illustrator. During the Second World War, Eliot Hodgkin was an RAF officer, rising to Wing Commander, and was assistant to Sefton Delmer in running his black propaganda campaign against Nazi Germany.

His maternal grandfather Gordon Hewart, 1st Viscount Hewart was a journalist, lawyer, Member of Parliament (MP) and Lord Chief Justice; and the scientist Thomas Hodgkin was his great-great-grandfather's older brother. Hodgkin was a cousin of the English still life painter Eliot Hodgkin (1905–1987).

During the Second World War, Hodgkin was evacuated with his mother and sister to the US, where they lived on Long Island, New York. On returning, he was educated at Eton College and then at Bryanston School in Dorset. He had decided on a career in art in early childhood and ran away from school to pursue this.

He studied at the Camberwell Art School and later at the Bath Academy of Art in Corsham, where Edward Piper studied drawing under him.

Career
Memoirs (1949), one of Hodgkin's earliest recorded paintings, shows the artist, then aged 17, listening to a female figure reclining on a sofa. Painted with angular forms and black outlines, the work precedes Hodgkin's distinct abstract style.

Hodgkin's first solo show was in London in 1962.

In 1980, Hodgkin was invited by John Hoyland to exhibit work as part of the Hayward Annual at the Hayward Gallery along with Gillian Ayres, Basil Beattie, Terry Setch, Anthony Caro, Patrick Caulfield, Ben Nicholson and others.

In 1981, Hodgkin had collaborated with the Rambert Dance Company's Resident Choreographer, Richard Alston, for his abstract work 1981 for the production of Night Music and later for the production of Pulcinella in 1987.

In 1984, Hodgkin represented Britain at the Venice Biennale, in 1985 he won the Turner Prize, and in 1992 he was knighted.

British Council in India
Hodgkin was invited to design a mural for the front of Charles Correa's 1992 headquarters for the British Council in India. Hodgkin's mural is of a banyan tree spreading its branches across the walls. It is a symbol of the British Council's work rooted in the Indian cultural scene. Hodgkin said of Correa:   “Charles Correa is the most perfect architect you could imagine. He first suggested that I think about the mural as an Indian flag turning into a Union Jack. I said no.”

In 1995, Hodgkin printed the Venetian Views series, which depict the same view of Venice at four different times of day. Venice, Afternoon – one of the four prints – uses 16 sheets, or fragments, in a hugely complex printing process that creates a colourful, painterly effect. This piece was given to the Yale Centre of British Art in June 2006 by its Israeli family owners in order to complement the museum's already-impressive collection of Hodgkins.

A major exhibition of his work was mounted at Tate Britain, London, in 2006. Also in 2006, The Independent declared him one of the 100 most influential gay people in Britain, as his work has helped many people express their emotions to others.

In September 2010, Hodgkin and five other British artists, John Hoyland, John Walker, Ian Stephenson, Patrick Caulfield and R.B. Kitaj, were in an exhibition entitled The Independent Eye: Contemporary British Art From the Collection of Samuel and Gabrielle Lurie, at the Yale Center for British Art.

Before his death on 9 March 2017 he was working on two UK exhibitions, one at the Hepworth Wakefield, and another at the National Portrait Gallery.

His prints were hand-painted etchings and he worked with the master printer Jack Shirreff at 107 Workshop.

A feature of his painting was that he made the frame intrinsic to the work "incorporated physically into the painting as part of its making, or created as an illusion to give definition to his subject."

National Life Stories conducted an oral history interview (C466/286) with Howard Hodgkin between 2008 and 2017 for its Artists' Lives collection held by the British Library.

Honours
Hodgkin was appointed a CBE in 1977, and he was knighted in 1992. In 1997 the Hamburg-based Alfred Toepfer Foundation awarded Hodgkin its annual Shakespeare Prize in recognition of his life's work. He received an honorary fellowship from the London Institute in 1999. In 2000, he was awarded an honorary DLitt by the University of Oxford. He was made a Member of the Order of the Companions of Honour in the 2003 New Year Honours for his services to art. Hodgkin was named 2014 Whitechapel Gallery Art Icon.

Personal life
In 1955, Hodgkin married Julia Lane, by whom he had two children. Hodgkin knew he was gay, even when he was married, and later left his wife. In 2009, The Independent reported that he had been with his partner, the music writer Antony Peattie, for 20 years. They lived in a four-storey Georgian house in Bloomsbury, near the British Museum.

Death
On 9 March 2017, Hodgkin died at the age of 84 in a hospital in London. Tributes to him were made by several figures in British art, including Tate director Nicholas Serota.

title: Howard Hodgkin