Mitrasacme
Mitrasacme is a genus of plants in the family Loganiaceae. Around 40 species occur,[1] mostly in Australia, though also extending to various parts of Asia and the Pacific Islands. Two species also occur in China.
| Mitrasacme | |
|---|---|
 | |
| Mitrasacme polymorpha | |
Scientific classification  | |
| Kingdom: | Plantae |
| Clade: | Tracheophytes |
| Clade: | Angiosperms |
| Clade: | Eudicots |
| Clade: | Asterids |
| Order: | Gentianales |
| Family: | Loganiaceae |
| Genus: | Mitrasacme Labill. |
The name comes from the Greek, alluding to “the highest point of the mitre”. As the fruit capsule has an alleged resemblance to a mitre.
Selected species
- Mitrasacme alsinoides
- Mitrasacme ambigua
- Mitrasacme connata
- Mitrasacme epigaea
- Mitrasacme exserta
- Mitrasacme foliosa
- Mitrasacme paradoxa
- Mitrasacme paludosa
- Mitrasacme pilosa
- Mitrasacme polymorpha
- Mitrasacme serpyllifolia
gollark: > sqlite is not less complex than this formatYes. *But*, you don't actually have to interact with the SQLite disk format directly because libsqlite3 exists.
gollark: I suspect SQLite would lose out somewhat in storage efficiency, but it could plausibly be faster for many things at runtime.
gollark: It's less complex for everyone interacting with it, since they can just... use SQLite, which has bindings for everything, instead of "zimlib". And by "efficiency" do you mean "space efficiency" or "lookup efficiency"? Because, as I said, SQLite would probably only add a few bytes per directory entry row, which is not a significant increase.
gollark: SQLite's overhead is pretty low, and the majority of the filesize is from the binary blobs which would remain the same in each.
gollark: It's less complex for them as the code is already there and written with a nice API, and "less efficient" how? Slightly more space on headers?
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.