Re: [Lazarus] Best practices on using classes for subroutine libraries

2012-04-15 Thread Joao Morais
On Sat, Apr 14, 2012 at 04:23, Frank Church vfcli...@gmail.com wrote: Is it possible to make them virtual and override them or replace them in descendant classes? {$mode objfpc} type tfooclass = class of tfoo; tfoo = class public class function m1: string; virtual;

Re: [Lazarus] Best practices on using classes for subroutine libraries

2012-04-14 Thread Sven Barth
On 14.04.2012 09:23, Frank Church wrote: On 10 April 2012 19:08, Marcos Douglasm...@delfire.net wrote: On Tue, Apr 10, 2012 at 12:49 PM, Frank Churchvfcli...@gmail.com wrote: On 10 April 2012 12:28, Marcos Douglasm...@delfire.net wrote: On Tue, Apr 10, 2012 at 1:07 AM, Frank

Re: [Lazarus] Best practices on using classes for subroutine libraries

2012-04-14 Thread Marcos Douglas
On Sat, Apr 14, 2012 at 4:23 AM, Frank Church vfcli...@gmail.com wrote: On 10 April 2012 19:08, Marcos Douglas m...@delfire.net wrote: On Tue, Apr 10, 2012 at 12:49 PM, Frank Church vfcli...@gmail.com wrote: On 10 April 2012 12:28, Marcos Douglas m...@delfire.net wrote: On Tue, Apr 10, 2012 at

Re: [Lazarus] Best practices on using classes for subroutine libraries

2012-04-10 Thread Hans-Peter Diettrich
Frank Church schrieb: When I need a variation in procedures (standalone, not a class or object procedure) I use across my applications, I often find it more convenient to create a copy the unit into the project folder and make the changes there. Sometimes they get merged back into the shared

Re: [Lazarus] Best practices on using classes for subroutine libraries

2012-04-10 Thread Marcos Douglas
On Tue, Apr 10, 2012 at 1:07 AM, Frank Church vfcli...@gmail.com wrote: When I need a variation in procedures (standalone, not a class or object procedure) I use across my applications, I often find it more convenient to create a copy the unit into the project folder and make the changes

Re: [Lazarus] Best practices on using classes for subroutine libraries

2012-04-10 Thread Frank Church
On 10 April 2012 12:28, Marcos Douglas m...@delfire.net wrote: On Tue, Apr 10, 2012 at 1:07 AM, Frank Church vfcli...@gmail.com wrote: When I need a variation in procedures (standalone, not a class or object procedure) I use across my applications, I often find it more convenient to create a

Re: [Lazarus] Best practices on using classes for subroutine libraries

2012-04-10 Thread Marcos Douglas
On Tue, Apr 10, 2012 at 12:49 PM, Frank Church vfcli...@gmail.com wrote: On 10 April 2012 12:28, Marcos Douglas m...@delfire.net wrote: On Tue, Apr 10, 2012 at 1:07 AM, Frank Church vfcli...@gmail.com wrote: When I need a variation in procedures (standalone, not a class or object procedure) I

[Lazarus] Best practices on using classes for subroutine libraries

2012-04-09 Thread Frank Church
When I need a variation in procedures (standalone, not a class or object procedure) I use across my applications, I often find it more convenient to create a copy the unit into the project folder and make the changes there. Sometimes they get merged back into the shared unit or not at all. I am