conventions

Let's say you have a Fortran 90 module containing lots of variables, functions and subroutines. In your USE statement, which convention do you follow: explicitly declare which variables/functions/subroutines you're using with the , only : syntax, such as USE [module_name], only : variable1, variable2, ... ? Insert a blanket USE [module_name] ? On the one hand, the only clause makes the code a bit more verbose. However, it forces you to repeat yourself in the code and if your module contains lots of variables/functions/subroutines, things begin to look unruly. Here's an example: module

While coding python I'm using only 2 spaces to indent, sure PEP-8 really recommend to have 4 spaces, but historically for me it's unusual. So, can anyone convince me to use 4 spaces instead of 2? What pros and cons? P.S. And finally, what's easy way to convert all existing codebase from 2 spaces to 4 spaces? P.P.S. PEP-8 Also srictly recommend not using tabs for indention. read here So, to summarize: Pros: Have more space to arrange when wraping string more than 80 lines long. Can copy code from snippets and it just works. Cons: With deeper level of nested statements you have less space for

I'm having trouble finding good advice and common practices for the use of namespaces in Clojure. I realize that namespaces are not the same as Java packages so I'm trying to tease out the conventions in Clojure, which seem surprisingly hard to determine. I think I have a pretty good idea how to split functions into clj files and even roughly how I'd want to organize those files into directories. But beyond that I'm having trouble finding the mechanics for my dev environment. Some inter-related questions: Do I use the same uniqueness conventions for Clojure namespaces as I would normally use

Is there any difference of use, efficiency or background technique between var mc:MovieClip = MovieClip(getChildByName("mc")); and var mc:MovieClip = getChildByName("mc") as MovieClip; ? The choice is just matter of convention, preference or are there cases where you can't use one? Paul Bellora This article describes the differences well: A key difference between casting and the as operator is the behavior on failure. When a cast fails in ActionScript 2, null is returned. When a cast fails in ActionScript 3, a TypeError is thrown. With the as operator in ActionScript 3, whenever a cast fails