CamelCase vs underscores: Scientific showdown (2011)

Post by andyferris » Tue, May 21, 2024, 12:57 PM UTC

navane wrote: post #12

Why can't we just have spaces in our variable names? These are both work arounds.

Post by navane » Tue, May 21, 2024, 1:19 PM UTC

delichon wrote: post #32

rileymat2 wrote: post #22

Earlier quoted context omitted.

I am not picturing why this is true, if you cannot use key words as parts of variables (alone separated by a space) and lines end with a newline or semicolon (some symbol) The first restriction might make this a problem. I am not saying it is a good idea, but it is not obvious to me.

Removing keywords from variables is a big sacrifice when they are often such common glue words, like `and`, `or`, `if`, etc. Say `and` is the keyword and you want a variable called foo_and_bar. To get such words back you would need to add something so that the parser knows if foo and bar == true means foo && bar == true or foo_and_bar == true ? You could fix it with ugliness like making the keyword `@and` or some suc…

  if ( thisLooksAppealing )
  {
      youLikeCamelCase = true;
      votePoll( camelCaseFormatting );
  }
  else if ( this_looks_appealing )
  {
      you_like_underscores = true;
      vote_poll( underscore_formatting );
  }
  else if ( this looks appealing )
  {
      you like spaces = true;
      vote poll ( space formatting );
  }

Post by navane » Tue, May 21, 2024, 1:24 PM UTC

ReleaseCandidat wrote: post #70

ivan_gammel wrote: post #39

Earlier quoted context omitted.

var search result = users. find all by name (name); if (search result. is present()) { return ok(search result. get()); } else return not found(); It’s weird and syntax highlighting is absolutely necessary to read this.

Using something else than a dot is better, same as using a slightly different syntax: search result := users @ find all by name (name) if search result @ is present() { return ok(search result @ get()) } else { return not found() }

   search result := users, find all by name (name)

   if search result, is present() { 
      return ok(search result, get())
   } else {
     return not found()
   }

Post by ReleaseCandidat » Tue, May 21, 2024, 1:49 PM UTC

navane wrote: post #76

ReleaseCandidat wrote: post #70

Earlier quoted context omitted.

Using something else than a dot is better, same as using a slightly different syntax: search result := users @ find all by name (name) if search result @ is present() { return ok(search result @ get()) } else { return not found() }

I still think the space adds more readability than the dot dectracts. If you don't like the dot though, I would use a comma. We have been writing for a couple centuries now, and the comma is well known and used. search result := users, find all by name (name) if search result, is present() { return ok(search result, get()) } else { return not found() }

Post by keybored » Tue, May 21, 2024, 1:54 PM UTC

IshKebab wrote: post #45

keybored wrote: post #3

hyphen-case is worth the grammar concessions (like making whitespace between binary operators mandatory).

Yeah no thanks. Soo `a-b` and `a - b` are both potentially valid and different? Also allowing hyphens generally leads to issues when interoperating with other languages that don't support hyphens. Probably the best example of this is CSS which does allow hyphens, and Javascript which doesn't. `background-color` in CSS gets translated to `backgroundColor` in JS. It's an annoying paper cut that trips up beginners and m…