Eli L. Whiteley

Eli Lamar Whiteley (December 10, 1913 – December 2, 1986) was a former infantry captain in the United States Army who received the Medal of Honor for valor in World War II, for his actions in Sigolsheim, France in 1944. He was drafted into the US Army in April 1942.[3]

Eli L. Whiteley
Eli L. Whiteley and an exhibit Medal of Honor on display at Texas A&M University[1][2]
Born(1913-12-10)December 10, 1913
Georgetown, Texas
DiedDecember 2, 1986(1986-12-02) (aged 72)
College Station, Texas
Place of burial
College Station Cemetery, College Station, Texas
AllegianceUnited States of America
Service/branchUnited States Army
Years of service1942–1945
RankCaptain
UnitCompany L, 15th Infantry, 3rd Infantry Division
Battles/warsWorld War II
AwardsMedal of Honor
Purple Heart
Combat Infantryman Badge

Medal of Honor

Whiteley's Medal of Honor citation reads:

While leading his platoon on December 27, 1944, in savage house-to-house fighting through the fortress town of Sigolsheim, France, he attacked a building through a street swept by withering mortar and automatic weapons fire. He was hit and severely wounded in the arm and shoulder; but he charged into the house alone and killed its 2 defenders. Hurling smoke and fragmentation grenades before him, he reached the next house and stormed inside, killing 2 and capturing 11 of the enemy. He continued leading his platoon in the extremely dangerous task of clearing hostile troops from strong points along the street until he reached a building held by fanatical Nazi troops. Although suffering from wounds which had rendered his left arm useless, he advanced on this strongly defended house, and after blasting out a wall with bazooka fire, charged through a hail of bullets. Wedging his submachine gun under his uninjured arm, he rushed into the house through the hole torn by his rockets, killed 5 of the enemy and forced the remaining 12 to surrender. As he emerged to continue his fearless attack, he was again hit and critically wounded. In agony and with 1 eye pierced by a shell fragment, he shouted for his men to follow him to the next house. He was determined to stay in the fighting, and remained at the head of his platoon until forcibly evacuated. By his disregard for personal safety, his aggressiveness while suffering from severe wounds, his determined leadership and superb courage, 1st Lt. Whiteley killed 9 Germans, captured 23 more and spearheaded an attack which cracked the core of enemy resistance in a vital area.

gollark: Well, yes, but they're byte sequences.
gollark: I mean, it's better than C and stuff, and I wouldn't mind writing simple apps in it.
gollark: Speaking specifically about the error handling, it may be "simple", but it's only "simple" in the sense of "the compiler writers do less work". It's very easy to mess it up by forgetting the useless boilerplate line somewhere, or something like that.
gollark: Speaking more generally than the type system, Go is just really... anti-abstraction... with, well, the gimped type system, lack of much metaprogramming support, and weird special cases, and poor error handling.
gollark: - They may be working on them, but they initially claimed that they weren't necessary and they don't exist now. Also, I don't trust them to not do them wrong.- Ooookay then- Well, generics, for one: they *kind of exist* in that you can have generic maps, channels, slices, and arrays, but not anything else. Also this (https://fasterthanli.me/blog/2020/i-want-off-mr-golangs-wild-ride/), which is mostly about the file handling not being good since it tries to map on concepts which don't fit. Also channels having weird special syntax. Also `for` and `range` and `new` and `make` basically just being magic stuff which do whatever the compiler writers wanted with no consistency- see above- Because there's no generic number/comparable thing type. You would need to use `interface{}` or write a new function (with identical code) for every type you wanted to compare- You can change a signature somewhere and won't be alerted, but something else will break because the interface is no longer implemented- They are byte sequences. https://blog.golang.org/strings.- It's not. You need to put `if err != nil { return err }` everywhere.

See also

References
  1. "Memorial Student Center". Archived from the original on August 25, 2004. Retrieved October 5, 2010.
  2. "Aggie Traditions". Archived from the original on July 1, 2012. Retrieved October 5, 2010.
  3. Texas Handbook Online
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.