![]() Proto-Macro-Jê is notable for having relatively few consonants and a large vocalic inventory. However, Nikulin (2020) considers Chiquitano to be a sister of Macro-Jê. Nikulin (2020) does not accept the following languages and language families as part of Macro-Jê. ? Kamakã (possibly part of Trans-São Francisco).Nikulin (2020) proposes the following internal classification of Macro-Jê: Macro-Jê Timbira: Apãniekra Kraho Krẽje † Krĩkati Parkateje Pykobje Ramkokamekra.Jeoromitxi-Arikapu (Yabutian): Arikapu Jeoromitxi.Jolkesky (2016) proposes the following internal classification of Macro-Jê: : 794–795 Macro-Jê It notes suggestive grammatical similarities with Bororoan, Kariri, and Chiquitano, of the kind also shared with Tupian and Cariban, but little lexical evidence. Lexical parallels with Kamakanan and Purian have yet to be corroborated with reconstructions the similarities with Purian disappear once Coropo is reclassified as Maxakalian. Glottolog accepts Jean, Krenak (Aimore), Karaja, Maxakalian, Ofaie, Rikbaktsa, and Yabutian (Jabuti). Pache (2018) suggests a distant genetic relationship between Macro-Jê and Chibchan. These languages share irregular morphology with the Tupi and Carib families, and Rodrigues (2000) and Ribeiro connect them all as a Je–Tupi–Carib family. Ribeiro does include Chiquitano, pace Rodrigues. Įduardo Ribeiro of the University of Chicago finds no evidence to classify Fulniô (Yatê) and Guató as Macro-Jê, pace Kaufman, nor Otí, pace Greenberg. Kaufman (1990) finds the proposal "probable". The Macro-Jê family was first proposed in 1926, and has undergone moderate modifications since then. It is centered on the Jê language family, with most other branches currently being single languages due to recent extinctions. Macro-Jê (also spelled Macro-Gê) is a medium-sized language stock in South America, mostly in Brazil but also in the Chiquitanía region in Santa Cruz, Bolivia, as well as (formerly) in small parts of Argentina and Paraguay. The preprocessor treats comments as white space, so comments of the form /* some sort of comment */ are treated as white space.The Macro-Jê families of Kaufman's conception You can do that by using C-style comments ( /**/). This works well for small macros, but if you have a larger macro that is spread over several lines, it might be nice to put comments nearer some tricky or crucial bit of code. The easiest way to document macros is to just add comments before or after the macro definition: // returns the larger of the two arguments This works with both C and C++ compilers. Comments are an important part of documenting your code.Īdding comments to macros is quite easy, but it has to be done the right way. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |