> Code style by project would be useful. Projects may have very different > origins and very different styles. > Having several named code styles (company, jdk, apache, etc) and choosing > which code-style a project uses would be useful.
> I don't see much use for this within a project . Editable files within the > project should all have the same code style. There is a world of difference between "should all have the same style" and what is often the case. Many of us are not fortunate enough to work on consistently styled projects especially where there are a large number of developers involved or where projects have been combined. In many cases developers draw from their personal code libraries, many ignore conventions and others periodically forget. Personally I'd see the feature for multiple choosable styles as a low priority and the option of auto-detecting style, with the ability to over-ride as more important. Paul. p.s. sorry about the previous blank mailing. -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
