On Fri, Mar 20, 2020 at 10:47 AM Bart wrote:
> I prefer the Options parameter over another Boolean, mainly because
> you never know if another use-case might raise the need for yet
> another parameter.
Committed in r62782
--
Bart
--
___
lazarus
On 20.03.2020 12:05, Juha Manninen via lazarus wrote:
On Thu, Mar 19, 2020 at 10:11 AM Ondrej Pokorny via lazarus
mailto:lazarus@lists.lazarus-ide.org>>
wrote:
It is really frustrating when this happens every 10 minutes :/ I
really don't see a point to change working code to generics.
On Thu, Mar 19, 2020 at 10:11 AM Ondrej Pokorny via lazarus <
lazarus@lists.lazarus-ide.org> wrote:
> Well, generics may cause an internal error on a simple compile. A clean
> rebuild is needed to compile even after a small change.
>
It may be true when a generics class definition changes.
On Fri, Mar 20, 2020 at 9:12 AM Rolf Wetjen via lazarus
wrote:
> Same change in code as I used for my patch.
>
> So, yes: working.
OK.
I prefer the Options parameter over another Boolean, mainly because
you never know if another use-case might raise the need for yet
another parameter.
--
Same change in code as I used for my patch.
So, yes: working.
Rolf
Am 19.03.2020 um 22:40 schrieb Bart via lazarus:
On Thu, Mar 19, 2020 at 6:37 PM Bart wrote:
It's on my ToDo list (as long as other devels don't object to this.
I intend to have an Options property for that, with for now
Hi Bart,
I did something similar yesterday:
TMask.InitMaskString(const AValue: String; const CaseSensitive: Boolean;
*const UseSets: Boolean = True*);
TMask.Create(const AValue: String; const CaseSensitive: Boolean = False;
*const UseSets: Boolean = True*);
TMaskList.Create(const AValue:
