Re: [Lazarus] CodeTools facility for documenting source code?

2011-04-20 Thread zeljko
On Wednesday 20 of April 2011 16:47:40 William Oliveira Ferreira wrote: Borland/CodeGear/Embardcadero Developer Studio cames with a tab that stores last saves on currentsaves. It all BDS creates a directory called __history that stores these files. Should be a good idea if lazarus do something

Re: [Lazarus] CodeTools facility for documenting source code?

2011-04-20 Thread Graeme Geldenhuys
On 20/04/2011 16:47, William Oliveira Ferreira wrote: called __history that stores these files. Should be a good idea if lazarus do something like? That's just duplication of what VCS or SCM systems already do (well the good ones at least). I can search my git repositories for a patch/commit

Re: [Lazarus] CodeTools facility for documenting source code?

2011-04-20 Thread Sven Barth
Am 20.04.2011 16:47, schrieb William Oliveira Ferreira: Borland/CodeGear/Embardcadero Developer Studio cames with a tab that stores last saves on currentsaves. It all BDS creates a directory called __history that stores these files. Should be a good idea if lazarus do something like? With the

Re: [Lazarus] CodeTools facility for documenting source code?

2011-04-20 Thread William Oliveira Ferreira
Ow yeah! sorry! i forgot that! William de Oliveira Ferreira Bacharel em Sistemas de Informação 2011/4/20 Sven Barth pascaldra...@googlemail.com: Am 20.04.2011 16:47, schrieb William Oliveira Ferreira: Borland/CodeGear/Embardcadero Developer Studio cames with

[Lazarus] CodeTools facility for documenting source code?

2011-04-19 Thread Frank Church
Is there a codetools facility that can help you annotate changes to your functions, and also help you create some kind of documentation block whenever you create a new function or procedure? eg when I want to commit changes to SCM I would like a tool that can list all procedures which have

Re: [Lazarus] CodeTools facility for documenting source code?

2011-04-19 Thread Mattias Gaertner
    Frank Church vfcli...@gmail.com hat am 19. April 2011 um 12:51 geschrieben: Is there a codetools facility that can help you annotate changes to your functions, and also help you create some kind of documentation block whenever you create a new function or procedure? eg when I

Re: [Lazarus] CodeTools facility for documenting source code?

2011-04-19 Thread Frank Church
2011/4/19 Mattias Gaertner nc-gaert...@netcologne.de Frank Church vfcli...@gmail.com hat am 19. April 2011 um 12:51 geschrieben: Is there a codetools facility that can help you annotate changes to your functions, and also help you create some kind of documentation block whenever you

Re: [Lazarus] CodeTools facility for documenting source code?

2011-04-19 Thread Michael Van Canneyt
On Tue, 19 Apr 2011, Frank Church wrote: 2011/4/19 Mattias Gaertner nc-gaert...@netcologne.de     Frank Church vfcli...@gmail.com hat am 19. April 2011 um 12:51 geschrieben: Is there a codetools facility that can help you annotate changes to your

Re: [Lazarus] CodeTools facility for documenting source code?

2011-04-19 Thread Martin
On 19/04/2011 13:50, Frank Church wrote: I am looking for something manually triggered that can check what procedures have been modified, or added, then I can jump to them one by one and note down my changes. I don't need something that is necessarily hooked into my VCS, but something that

Re: [Lazarus] CodeTools facility for documenting source code?

2011-04-19 Thread Hans-Peter Diettrich
Martin schrieb: It would not show you a diff, of what was changed, but that can be found via svn and co (Maybe another field, indicating which revision a file had, at the time of documenting Git comes with a nice listing of a file's history, which ranges of lines have been changed, by