LANGUAGE #LENGHT #LENGTH = #LENGHT/#LENGTH
JavaScript 4252 2907459 = 0.0015
C 18981 2902857 = 0.0065
Java 7706 2348900 = 0.0033
Ruby 10789 1690604 = 0.0064
C++ 9458 1315552 = 0.0072
PHP 3116 1167924 = 0.0027
C# 1352 937647 = 0.0014
Python 3662 737292 = 0.0050
Ruby 1232 380484 = 0.0032
Perl 1239 258892 = 0.0048
Objective-C 679 238051 = 0.0029
P.S. There is something wrong with Github's language breakdown algorithm, sometimes it shows same language twice with a different number of hits.Search: .lenght - Github
31–40 of 106 posts
Re: Search: .lenght - Github
#32Re: Search: .lenght - Github
#33I remember seeing a Github bot a couple weeks ago that strips out whitespace and adds a .gitignore file to a repo (I also remember this really rubbing some people the wrong way). This search indicates that it would probably be useful to have a linter bot running on Github for all the popular languages. It would find syntax errors, common mispellings, and compilation issues, and then submit pull requests to fix the is…
I actually just replied with a suggestion that Github should implement some built-in functionality for simple error-checking. I think it's a great idea. It would be really helpful if you got a simple little list of notifications for a commit indicating possible error points.
Re: Search: .lenght - Github
#34A common typo, it seems. But I'm a bit confused as to why this was submitted.
In JavaScript, if you check for a non-existent property on a variable (e.g. aVar.lenght vs aVar.length) it will return "undefined". So people often rely on this behaviour to check if something is an array or not (no comment on whether this is good or bad), with: if(somethingThatMightBeAnArray.length){ // do things with array } So misspelling of length can be making a lot of code out there behave in an unexpected way.
Re: Search: .lenght - Github
#35Re: Search: .lenght - Github
#36What's the trade-off by having "undefined" returned instead of having an error reported as soon as the code is loaded?
Re: Search: .lenght - Github
#37A common typo, it seems. But I'm a bit confused as to why this was submitted.
In a static language this would be flagged as an error. I assume something less than ideal happens in languages such as Ruby. I once worked at a company where a very early piece of code had a typo "properites" instead of "properties". This misspelling became institutionalized, and was used throughout the codebase because it was deemed too expensive to fix. And this was with a static language (with good IDE refactorin…
Re: Search: .lenght - Github
#38A common typo, it seems. But I'm a bit confused as to why this was submitted.
Re: Search: .lenght - Github
#39Earlier quoted context omitted.
In a static language this would be flagged as an error. I assume something less than ideal happens in languages such as Ruby. I once worked at a company where a very early piece of code had a typo "properites" instead of "properties". This misspelling became institutionalized, and was used throughout the codebase because it was deemed too expensive to fix. And this was with a static language (with good IDE refactorin…
I'm confused as to why they couldn't simply: grep -R properites .
Re: Search: .lenght - Github
#40I thought this is actually interesting but I would like to know if >4k misspellings is a lot or not. Here is one way to do it: LANGUAGE #LENGHT #LENGTH = #LENGHT/#LENGTH JavaScript 4252 2907459 = 0.0015 C 18981 2902857 = 0.0065 Java 7706 2348900 = 0.0033 Ruby 10789 1690604 = 0.0064 C++ 9458 1315552 = 0.0072 PHP 3116 1167924 = 0.0027 C# 1352 937647 = 0.0014 Python 3662 737292 = 0.0050 Ruby 1232 380484 = 0.0032 Perl 12…