See snake`lowbar`case on Wiktionary
{ "forms": [ { "form": "snake`lowbar`case", "tags": [ "canonical" ] } ], "head_templates": [ { "args": { "1": "-" }, "expansion": "snake`lowbar`case (uncountable)", "name": "en-noun" } ], "lang": "English", "lang_code": "en", "original_title": "Unsupported titles/snake`lowbar`case", "pos": "noun", "senses": [ { "alt_of": [ { "word": "snake case" } ], "categories": [ { "kind": "other", "name": "English entries with incorrect language header", "parents": [ "Entries with incorrect language header", "Entry maintenance" ], "source": "w" }, { "kind": "other", "name": "Pages with 1 entry", "parents": [], "source": "w" }, { "kind": "other", "name": "Pages with entries", "parents": [], "source": "w" } ], "examples": [ { "ref": "2018, Camille McCue, Sarah Guthals, Helping Kids with Coding For Dummies®, John Wiley & Sons, Inc., →ISBN, page 130:", "text": "Some evidence shows that coders are better able to read code (their code and code written by others) when using snake_case, not camelCase naming.", "type": "quote" }, { "ref": "2020, Jeanne Boyarsky, Scott Selikoff, OCP Oracle Certified Professional Java SE 11 Programmer I: Study Guide, Exam 1Z0-815, John Wiley & Sons, Inc., →ISBN, page 49:", "text": "While both camelCase and snake_case are perfectly valid syntax in Java, the development community functions better when everyone adopts the same style convention.", "type": "quote" }, { "ref": "2020, Titus Winters, Tom Manshreck, Hyrum Wright, Software Engineering at Google: Lessons Learned from Programming Over Time, O’Reilly Media, Inc., →ISBN:", "text": "We were incorporating third-party Python libraries for some of our projects, leading to a mix within our codebase of our own CamelCase format with the externally preferred snake_case style.", "type": "quote" } ], "glosses": [ "Alternative form of snake case" ], "id": "en-snake`lowbar`case-en-noun-U3Gnk-RY", "links": [ [ "snake case", "snake case#English" ] ], "tags": [ "alt-of", "alternative", "uncountable" ] } ], "word": "snake`lowbar`case" }
{ "forms": [ { "form": "snake`lowbar`case", "tags": [ "canonical" ] } ], "head_templates": [ { "args": { "1": "-" }, "expansion": "snake`lowbar`case (uncountable)", "name": "en-noun" } ], "lang": "English", "lang_code": "en", "original_title": "Unsupported titles/snake`lowbar`case", "pos": "noun", "senses": [ { "alt_of": [ { "word": "snake case" } ], "categories": [ "English autological terms", "English entries with incorrect language header", "English lemmas", "English nouns", "English terms spelled with `", "English terms with quotations", "English uncountable nouns", "Pages with 1 entry", "Pages with entries" ], "examples": [ { "ref": "2018, Camille McCue, Sarah Guthals, Helping Kids with Coding For Dummies®, John Wiley & Sons, Inc., →ISBN, page 130:", "text": "Some evidence shows that coders are better able to read code (their code and code written by others) when using snake_case, not camelCase naming.", "type": "quote" }, { "ref": "2020, Jeanne Boyarsky, Scott Selikoff, OCP Oracle Certified Professional Java SE 11 Programmer I: Study Guide, Exam 1Z0-815, John Wiley & Sons, Inc., →ISBN, page 49:", "text": "While both camelCase and snake_case are perfectly valid syntax in Java, the development community functions better when everyone adopts the same style convention.", "type": "quote" }, { "ref": "2020, Titus Winters, Tom Manshreck, Hyrum Wright, Software Engineering at Google: Lessons Learned from Programming Over Time, O’Reilly Media, Inc., →ISBN:", "text": "We were incorporating third-party Python libraries for some of our projects, leading to a mix within our codebase of our own CamelCase format with the externally preferred snake_case style.", "type": "quote" } ], "glosses": [ "Alternative form of snake case" ], "links": [ [ "snake case", "snake case#English" ] ], "tags": [ "alt-of", "alternative", "uncountable" ] } ], "word": "snake`lowbar`case" }
Download raw JSONL data for snake`lowbar`case meaning in All languages combined (1.8kB)
This page is a part of the kaikki.org machine-readable All languages combined dictionary. This dictionary is based on structured data extracted on 2025-01-13 from the enwiktionary dump dated 2025-01-01 using wiktextract (4ba5975 and 4ed51a5). The data shown on this site has been post-processed and various details (e.g., extra categories) removed, some information disambiguated, and additional data merged from other sources. See the raw data download page for the unprocessed wiktextract data.
If you use this data in academic research, please cite Tatu Ylonen: Wiktextract: Wiktionary as Machine-Readable Structured Data, Proceedings of the 13th Conference on Language Resources and Evaluation (LREC), pp. 1317-1325, Marseille, 20-25 June 2022. Linking to the relevant page(s) under https://kaikki.org would also be greatly appreciated.