I typically use the following little hack tools to allow me to perform more tasks faster or automate certain tasks completely.
I had a php script which scanned the project directory and generated a list of TODO's extracted from my source. I have since just switched to using grep. Still damn handy if your like me and place TODO comments throughout your code.
What kind of tools have you hammered out in the past or present to assist you in making your coding experience more plesant...
try and avoid third party tools like lint, etc...I'm more curious to hear about tools you hacked out to help solve re-occuring problems in a particular project or all projects you work on.
What the heck, mention all the lints you use too...I just wanna know what adhoc type tools you use to make development easier...
No IDE's or their extensions, like source browsers, etc don't count.
Custom tools
Moderator: General Moderators
-
alex.barylski
- DevNet Evangelist
- Posts: 6267
- Joined: Tue Dec 21, 2004 5:00 pm
- Location: Winnipeg
- Maugrim_The_Reaper
- DevNet Master
- Posts: 2704
- Joined: Tue Nov 02, 2004 5:43 am
- Location: Ireland
Well, I'm writing a behaviour specification suite - does that count
.
You probably pegged it best - most of the tiny tasks I write (often as Phing plugins) are for recursively scanning source code files and directories hunting for metrics. So I may want to compile a list of @todo notes (I think annotations are the cleanest form of marking), or maybe compile a list of files a specific test requires from the source code under test, or just to allow a quick scan of a class for its method names (so I don't need to go open and read the file to remember them all!). Nearly all run from the command line.
You probably pegged it best - most of the tiny tasks I write (often as Phing plugins) are for recursively scanning source code files and directories hunting for metrics. So I may want to compile a list of @todo notes (I think annotations are the cleanest form of marking), or maybe compile a list of files a specific test requires from the source code under test, or just to allow a quick scan of a class for its method names (so I don't need to go open and read the file to remember them all!). Nearly all run from the command line.
-
alex.barylski
- DevNet Evangelist
- Posts: 6267
- Joined: Tue Dec 21, 2004 5:00 pm
- Location: Winnipeg
Thats a good idea. Quick, realtime docs. I wonder if this could easily be accomplished using reflection, to simply list the class name and their methods and parameters.or just to allow a quick scan of a class for its method names (so I don't need to go open and read the file to remember them all!).
- Maugrim_The_Reaper
- DevNet Master
- Posts: 2704
- Joined: Tue Nov 02, 2004 5:43 am
- Location: Ireland
- Kieran Huggins
- DevNet Master
- Posts: 3635
- Joined: Wed Dec 06, 2006 4:14 pm
- Location: Toronto, Canada
- Contact:
-
alex.barylski
- DevNet Evangelist
- Posts: 6267
- Joined: Tue Dec 21, 2004 5:00 pm
- Location: Winnipeg