DBT
----------

DBT (Dependencies and deBugging Tool) is a tool that looks for `break`,
`require`, and `provides` commands (and does a *teensy* bit of code analyzing -
it will detect VERY basic class and module declarations) to make your RubyMotion
`Rakefile` and `debugger_cmds` files short and consistent.

**CAUTION**: It overwrites the `debugger_cmds` file!

To use, include this gem (`gem 'depdep'`), and add `app.analyze` to your
`Rakefile`, after you have added your libraries and whatnot.  It looks at
`app.files` and scans those files, so I mean it when I say "after you have added
your libraries and whatnot". In your source code you add DBT commands:

```ruby
# @provides Foo
# @requires Bar
def scary_method
#-----> break
  doing
  interesting
  stuff
end
```

When you run `rake`, these commands will be found and translated into directives
for `app.files_dependencies` and `debugger_cmds`. Run `rake` or `rake debug=1`,
and off you go!

Your files will be grep'd for `^\w*(class|module)`, and these will be registered
automatically as:

```ruby
# @provides class:ClassName
class ClassName
end

# @provides module:ModuleName
class ModuleName
end
```

So right out of the box, you can add `# @requires class:Foo` if you're having
trouble with dependencies and want a quick fix without having to add
`# @provides` declarations all over the place.

The syntax for a command is:

```regex
^#[ \t]*@(provides|requires)
or for break points:
^#--+> *(break)( *(\w+|[0-9]+))?$
```

If a line number is given to the `break` command, a breakpoint will be added *at
that line*, otherwise it will be added to the line below `break`.  It's better to
insert the `#--> break` where you NEED it, rather than hardcode line numbers,
since line numbers are not constant.