49th Indian Infantry Brigade
The 49th Indian Infantry Brigade was an infantry brigade formation of the Indian Army during World War II. It was formed in October 1941 at Bolarum in India. It was assigned to the 19th Indian Infantry Division. The brigade fought in the Burma Campaign and moved between a number of infantry divisions. It was with the 14th Indian Infantry Division between March and May in 1942, the 23rd Indian Infantry Division between May 1942 and March 1944, the 17th Indian Infantry Division between March and April 1944 and the served with the 23rd Indian Division until the end of the war. The Brigade is currently a reserve formation on the Western Front.[1]
| 49th Indian Infantry Brigade | |
|---|---|
| Active | 1941–1945 |
| Country |  |
| Allegiance |  |
| Branch | |
| Type | Infantry |
| Size | Brigade |
| Engagements | Burma Campaign |
| Commanders | |
| Notable commanders | R D Whitehill W B Thomas F A Esse C H B Rodham A W S Mallaby |
Formation
- 1st Battalion, 17th Dogra Regiment October 1941 to May 1942
- 2nd Battalion, 19th Hyderabad Regiment November 1941 to November 1942
- 5th Battalion, 6th Rajputana Rifles November 1941 to August 1945
- Kalibahadur Regiment, Nepal May to September 1942
- Shere Regiment, Nepal May to September 1942
- 4th Battalion, 5th Mahratta Light Infantry June 1942 to August 1945
- 6th Battalion, 5th Mahratta Light Infantry November 1942 to August 1945
- 9th Battalion, 12th Frontier Force Regiment May 1944 [2]
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.
gollark: Oh, and the error handling is terrible and it's kind of the type system's fault.
gollark: If I remember right Go strings are just byte sequences with no guarantee of being valid UTF-8, but all the functions working on them just assume they are.
References
- "49 Indian Brigade". Order of Battle. Retrieved 2009-10-23.
- "49 Indian Brigade Units". Order of Battle. Retrieved 2009-10-23.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.