According to the Racket documentation, there is no difference — there is only a convention to use [ and ] for cond clauses (and use your judgement for the rest, as far as I understand): The use of square brackets for cond clauses is a convention. In Racket, parentheses and square brackets are actually interchangeable, … Read more
add this in your .emacs: (setq-default indent-tabs-mode nil) or you can define a before-save-hook that eliminate hard tabs
Note: Please see the update at the end of the answer, declarations within blocks became valid (but quite complicated if you’re not using strict mode). Here’s one reason: var whatever; if (some_condition) { whatever = function() { // Do something }; } else { whatever = function() { // Do something else }; } whatever(); … Read more
The plain-adjective form is easily the norm in Ruby and Rails — even?, nil?, empty? and blank? for example. The only method of the form is_#{something}? that I can think of is Kernel#is_a? to determine class identity. So to stick with standard naming conventions, I would leave off the is_ on boolean methods like this.
There is no recommendation / convention for this case, and as Halcyon already mentioned this is a quite exceptional case. However, there is a recommendation for a function call with a long list of parameters: Argument lists MAY be split across multiple lines, where each subsequent line is indented once. When doing so, the first … Read more
The theoretical limit is really long but do you really need worry about these long Email addresses? If someone can’t login with a 100-char Email, do you really care? We actually prefer they can’t. Some statistical data may shed some light on the issue. We analyzed a database with over 10 million Email addresses. These … Read more