632 BC

The year 632 BC was a year of the pre-Julian Roman calendar. In the Roman Empire, it was known as year 122 Ab urbe condita . The denomination 632 BC for this year has been used since the early medieval period, when the Anno Domini calendar era became the prevalent method in Europe for naming years.

Millennium: 1st millennium BC
Centuries:
Decades:
Years:
632 BC in various calendars
Gregorian calendar632 BC
DCXXXI BC
Ab urbe condita122
Ancient Egypt eraXXVI dynasty, 33
- PharaohPsamtik I, 33
Ancient Greek era37th Olympiad (victor)¹
Assyrian calendar4119
Balinese saka calendarN/A
Bengali calendar−1224
Berber calendar319
Buddhist calendar−87
Burmese calendar−1269
Byzantine calendar4877–4878
Chinese calendar戊子年 (Earth Rat)
2065 or 2005
     to 
己丑年 (Earth Ox)
2066 or 2006
Coptic calendar−915 – −914
Discordian calendar535
Ethiopian calendar−639 – −638
Hebrew calendar3129–3130
Hindu calendars
 - Vikram Samvat−575 – −574
 - Shaka SamvatN/A
 - Kali Yuga2469–2470
Holocene calendar9369
Iranian calendar1253 BP – 1252 BP
Islamic calendar1291 BH – 1290 BH
Javanese calendarN/A
Julian calendarN/A
Korean calendar1702
Minguo calendar2543 before ROC
民前2543年
Nanakshahi calendar−2099
Thai solar calendar−89 – −88
Tibetan calendar阳土鼠年
(male Earth-Rat)
−505 or −886 or −1658
     to 
阴土牛年
(female Earth-Ox)
−504 or −885 or −1657

Events

  • Cylon, Athenian nobleman, seizes the Acropolis in a failed attempt to become king.[1]

Births

Deaths

gollark: I wonder how long it'll be before someone makes Unicode Turing-complete.
gollark: https://www.reddit.com/r/rust/comments/5penft/parallelizing_enjarify_in_go_and_rust/dcsgk7n/I think this just wonderfully encapsulates Go.
gollark: Oh, it also has that weird conditional compile thing depending on `_linux.go` suffixes or `_test.go` ones I think?
gollark: Okay, sure, you can ignore that for Go itself, if we had Go-with-an-alternate-compiler-but-identical-language-bits it would be irrelevant.
gollark: I can't easily come up with a *ton* of examples of this, but stuff like generics being special-cased in for three types (because guess what, you *do* actually need them), certain basic operations returning either one or two values depending on how you interact with them, quirks of nil/closed channel operations, the standard library secretly having a `recover` mechanism and using it like exceptions a bit, multiple return values which are not first-class at all and which are used as a horrible, horrible way to do error handling, and all of go assembly, are just inconsistent and odd.

References

  1. E.J. Bickerman, Chronology of the Ancient World (Ithaca: Cornell University Press, 1968), p. 198


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.