Frederick Louis, Count of Nassau-Ottweiler

Frederick Louis of Nassau-Ottweiler (13 November 1651 – 25 May 1728) was a member of the House of Nassau.

Frederick Louis of Nassau-Ottweiler
Born(1651-11-13)13 November 1651
Ottweiler
Died25 May 1728(1728-05-25) (aged 76)
Saarbrücken
Noble familyHouse of Nassau
Spouse(s)Christiane of Ahlefeldt
Louise Sophie of Hanau-Lichtenberg
FatherJohn Louis, Count of Nassau-Ottweiler
MotherCountess Palatine Dorothea Catherine of Birkenfeld-Bischweiler

Biography

He was born in Ottweiler, the son of John Louis, Count of Nassau-Ottweiler and Countess Palatine Dorothea Catherine of Birkenfeld-Bischweiler. He was count of Nassau-Ottweiler from 1680 until his death. From 1721, he was also Count of Nassau-Idstein; from 1723 also Count of Nassau-Saarbrücken. When he died in Saarbrücken, without a male heir, his territories fell to his cousin Charles of Nassau-Usingen after his death in 1728.

Family

Frederick Louis married on 28 July 1680 with Christiane (1659–95), the daughter of Frederick of Ahlefeldt and Margaret Dorothea of Rantzau. They had eight daughters:

After Christiane's death, Frederick Louis married on 27 September 1697 Countess Louise Sophie of Hanau-Lichtenberg (11 April 1662 in Bischofsheim am Hohen Steg – 9 April 1751 in Ottweiler), the daughter of Johann Reinhard II of Hanau-Lichtenberg and Countess Palatine Anna Magdalena of Birkenfeld-Bischweiler. This marriage remained childless.

Ancestry
Frederick Louis, Count of Nassau-Ottweiler
Born: 13 November 1651 Died: 25 May 1728
Preceded by
John Louis		 Count of Nassau-Ottweiler
1680-1728		 Succeeded by
Charles
Preceded by
George August		 Count of Nassau-Idstein
1721-1728
Preceded by
Charles Louis		 Count of Nassau-Saarbrücken
1723-1728


gollark: - `make`/`new` are basically magic- `range` is magic too - what it does depends on the number of return values you use, or something. Also, IIRC user-defined types can't implement it- Generics are available for all of, what, three builtin types? Maps, slices and channels, if I remember right.- `select` also only works with the built-in channels- Constants: they can only be something like four types, and what even is `iota` doing- The multiple return values can't be used as tuples or anything. You can, as far as I'm aware, only return two (or, well, more than one) things at once, or bind two returns to two variables, nothing else.- no operator overloading- it *kind of* has exceptions (panic/recover), presumably because they realized not having any would be very annoying, but they're not very usable- whether reading from a channel is blocking also depends how many return values you use because of course
gollark: What, you mean no it doesn't have weird special cases everywhere?
gollark: It pretends to be "simple", but it isn't because there are bizarre special cases everywhere to make stuff appear to work.
gollark: So of course, lol no generics.
gollark: Well, golang has no (user-defined) generics, you see.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.