summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorDoug Kearns <dougkearns@gmail.com>2010-10-22 16:14:20 +1100
committerDoug Kearns <dougkearns@gmail.com>2010-10-22 16:14:20 +1100
commit76549faacc60a91642cba6d8ee236de1f1c4801a (patch)
treecfa26e8b6c753873ea85e1d905b50bb80163e070 /HACKING
parentb0098255304482cd2c4750f84b0dc20f1bd307c7 (diff)
downloadpentadactyl-76549faacc60a91642cba6d8ee236de1f1c4801a.tar.gz
Remove vague and untrue coding style recommendations.
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING9
1 files changed, 0 insertions, 9 deletions
diff --git a/HACKING b/HACKING
index eb0a2c37..1bfaea07 100644
--- a/HACKING
+++ b/HACKING
@@ -19,15 +19,6 @@ important, please ask.
In general: Just look at the existing source code!
-We try to target experienced JavaScript developers who do not
-necessarily need to have a good understanding of Pentadactyl's source
-code, nor necessarily understand in-depth concepts of other
-languages like Lisp or Python. Therefore, the coding style should
-feel natural to any JavaScript developer. Of course, this does not
-mean, you have to avoid all new JavaScript features like list
-comprehension or generators. Use them, when they make sense, but
-don't use them when the resulting code is hard to read.
-
=== The most important style issues are: ===
* Use 4 spaces to indent things, no tabs, not 2, nor 8 spaces. If you use Vim,