LivelyKernel/LivelyKernel — pull request #156 by lauritzthamsen (2013-08-20 11:35:33+00:00)
Title: File Parsing: allow more white space in module definitions

previously, the file parser looked for the beginning of a module definition, meaning the first line of the following example, only on a single line and also didn't allow any white space in it.
```javascript
module(...).requires(...).toRun(function(){
...
})
```

i stumbled over this after adding line breaks between the three calls at the beginning of my modules, when i had particularly long module names...resulting in SCBs that only show content in the first pane (files) and none in the other panes (classes, protocols, and methods).

these changes let the file parser check the whole remaining source of a file during parsing for the beginning of a module definition, meaning also multiple lines, and also allows for white space in the beginning of a module. so, the following example would still be parsed as a module definition:
```javascript
module(...).
requires(...).
toRun(function(){
...
})
```

our file parser tests doesn't seem to run really longer locally. also, opening and saving files doesn't seems significantly longer after these changes.