Re: [fpc-pascal] Smart Pointers

Am 10.05.2016 um 22:57 schrieb Maciej Izak: > 2016-05-10 21:18 GMT+02:00 Florian Klämpfl >: > > Aren't there several bug reports open which must be fixed first? > > > There is one critical bug related to class var and generics, but as

Re: [fpc-pascal] Smart Pointers

On Wed, 11 May 2016, Sven Barth wrote: On 11.05.2016 22:23, Florian Klämpfl wrote: Am 11.05.2016 um 14:12 schrieb Maciej Izak: 2016-05-11 13:46 GMT+02:00 Michael Van Canneyt >: Anything the compiler needs *must* be in the system

Re: [fpc-pascal] Smart Pointers

On Wed, 11 May 2016, Florian Klämpfl wrote: Am 11.05.2016 um 14:12 schrieb Maciej Izak: 2016-05-11 13:46 GMT+02:00 Michael Van Canneyt >: Anything the compiler needs *must* be in the system unit. The compiler should only assume

Re: [fpc-pascal] Smart Pointers

On 11.05.2016 22:23, Florian Klämpfl wrote: > Am 11.05.2016 um 14:12 schrieb Maciej Izak: >> 2016-05-11 13:46 GMT+02:00 Michael Van Canneyt > >: >> >> Anything the compiler needs *must* be in the system unit. The compiler >> should

Re: [fpc-pascal] Smart Pointers

Am 11.05.2016 um 14:12 schrieb Maciej Izak: > 2016-05-11 13:46 GMT+02:00 Michael Van Canneyt >: > > Anything the compiler needs *must* be in the system unit. The compiler > should only assume the system unit, possibly objpas or

Re: [fpc-pascal] Smart Pointers

2016-05-11 15:07 GMT+02:00 Maciej Izak : > > 2016-05-11 14:51 GMT+02:00 Sven Barth : > >> And I stand by that decision. Generics are a rather frickle feature and I >> want to know of critical failures as early as possible (and yes, I've made >> use

Re: [fpc-pascal] Smart Pointers

On Wed, 11 May 2016, Sven Barth wrote: Am 11.05.2016 14:42 schrieb "Maciej Izak" : 2016-05-11 14:23 GMT+02:00 Michael Van Canneyt : Where is that written ? As far as I know, it is only there because classes is there, and classes has some

Re: [fpc-pascal] Smart Pointers

2016-05-11 14:51 GMT+02:00 Sven Barth : > And I stand by that decision. Generics are a rather frickle feature and I > want to know of critical failures as early as possible (and yes, I've made > use of that already numerous times!), thus I prefer fgl to be part of the

Re: [fpc-pascal] Smart Pointers

Am 11.05.2016 14:42 schrieb "Maciej Izak" : > > 2016-05-11 14:23 GMT+02:00 Michael Van Canneyt : >> >> Where is that written ? As far as I know, it is only there because classes >> is there, and classes has some define to allow it to be compiled with

Re: [fpc-pascal] Smart Pointers

On Wed, 11 May 2016, Maciej Izak wrote: 2016-05-11 14:23 GMT+02:00 Michael Van Canneyt : Where is that written ? As far as I know, it is only there because classes is there, and classes has some define to allow it to be compiled with fgl. by Sven (29 January 2016

Re: [fpc-pascal] Smart Pointers

2016-05-11 14:23 GMT+02:00 Michael Van Canneyt : > Where is that written ? As far as I know, it is only there because classes > is there, and classes has some define to allow it to be compiled with fgl. > > by Sven (29 January 2016 10:54 thread "Generics.Collections as

Re: [fpc-pascal] Smart Pointers

In our previous episode, Michael Van Canneyt said: > > For example fgl module is part of RTL just because is usefully > > for Sven for testing purposes (! that is curious). > > Where is that written ? As far as I know, it is only there because classes > is there, and classes has some define to

Re: [fpc-pascal] Smart Pointers

On Wed, 11 May 2016, Maciej Izak wrote: 2016-05-11 13:46 GMT+02:00 Michael Van Canneyt : Anything the compiler needs *must* be in the system unit. The compiler should only assume the system unit, possibly objpas or macpas or so. All the rest should remain out of the

Re: [fpc-pascal] Smart Pointers

In our previous episode, Maciej Izak said: > > Some rtl-objpas units use classes, like fmtbcd. > > > > If you don't use fcl-base I would make it RTL, so we can use it in fcl-base > > if needed :-) > > > Library is low level without using anything outside RTL, IMO it should be > part of RTL like

Re: [fpc-pascal] Smart Pointers

2016-05-11 13:46 GMT+02:00 Michael Van Canneyt : > Anything the compiler needs *must* be in the system unit. The compiler > should only assume the system unit, possibly objpas or macpas or so. > > All the rest should remain out of the RTL, which should be as small as >

Re: [fpc-pascal] Smart Pointers

On Wed, 11 May 2016, Maciej Izak wrote: 2016-05-11 10:22 GMT+02:00 Marco van de Voort : Some rtl-objpas units use classes, like fmtbcd. If you don't use fcl-base I would make it RTL, so we can use it in fcl-base if needed :-) Library is low level without using anything

Re: [fpc-pascal] Smart Pointers

2016-05-11 10:22 GMT+02:00 Marco van de Voort : > Some rtl-objpas units use classes, like fmtbcd. > > If you don't use fcl-base I would make it RTL, so we can use it in fcl-base > if needed :-) Library is low level without using anything outside RTL, IMO it should be part of

Re: [fpc-pascal] Smart Pointers

In our previous episode, Florian Kl?mpfl said: > > whatever... > > If it depends on classes: fcl-generic, else RTL-generic. Some rtl-objpas units use classes, like fmtbcd. If you don't use fcl-base I would make it RTL, so we can use it in fcl-base if needed :-)

Re: [fpc-pascal] Smart Pointers

Am 11. Mai 2016 12:06:07 vorm. schrieb Sven Barth : > the main problem being the location, e.g. rtl-generics or fcl-generics or > whatever... If it depends on classes: fcl-generic, else RTL-generic. > > Regards, > Sven > > > > -- >

Re: [fpc-pascal] Smart Pointers

Am 10.05.2016 21:18 schrieb "Florian Klämpfl" : > > Am 10.05.2016 um 10:07 schrieb Maciej Izak: > > 2016-05-09 22:11 GMT+02:00 Florian Klämpfl >: > > > > Who said that? We discussed the syntax etc. and at least I

Re: [fpc-pascal] Smart Pointers

Am 10.05.2016 23:06 schrieb "Maciej Izak" : >> >> That is with (note these functions are generic): >> >> procedure Foo1(A: TArray); >> procedure Foo2(var A: TArray); >> procedure Foo3(out A: TArray); >> >> Where each can be called with a TManagedArray as the "A" argument

Re: [fpc-pascal] Smart Pointers

2016-05-10 22:33 GMT+02:00 Anthony Walter : > From your example code, the usage looks exactly like what I'd want. One > question though. Would the magic code also work with var and out arguments? > Yes. > That is with (note these functions are generic): > > procedure Foo1(A:

Re: [fpc-pascal] Smart Pointers

2016-05-10 21:18 GMT+02:00 Florian Klämpfl : > Aren't there several bug reports open which must be fixed first? There is one critical bug related to class var and generics, but as Sven said it need wait to "packages branch"... With other bugs we can +/- live. ;) btw

Re: [fpc-pascal] Smart Pointers

Maciej, >From your example code, the usage looks exactly like what I'd want. One question though. Would the magic code also work with var and out arguments? That is with (note these functions are generic): procedure Foo1(A: TArray); procedure Foo2(var A: TArray); procedure Foo3(out A: TArray);

Re: [fpc-pascal] Smart Pointers

Am 10.05.2016 um 10:07 schrieb Maciej Izak: > 2016-05-09 22:11 GMT+02:00 Florian Klämpfl >: > > Who said that? We discussed the syntax etc. and at least I see good > changes to integrate it in trunk > as soon as it is ready.

Re: [fpc-pascal] Smart Pointers

Am 10.05.2016 um 10:25 schrieb Maciej Izak: > 2016-05-09 23:23 GMT+02:00 Sven Barth >: > > I agree with Florian regarding the management operators. They will > probably be merged. > > > probably = wait few years + rather

Re: [fpc-pascal] Smart Pointers

2016-05-10 11:26 GMT+02:00 Anthony Walter : > Hey I'm all for your improvements. Good work, keep it up, and I actually > appreciate it. If you want, I can write up an overview of your improvements > at getlazarus.org and provide precompiled versions for testings/use on > all

Re: [fpc-pascal] Smart Pointers

Maciej, Hey I'm all for your improvements. Good work, keep it up, and I actually appreciate it. If you want, I can write up an overview of your improvements at getlazarus.org and provide precompiled versions for testings/use on all platforms (win, mac, linux, raspbian).. I asked Sven the other

Re: [fpc-pascal] Smart Pointers

2016-05-09 23:23 GMT+02:00 Sven Barth : > I agree with Florian regarding the management operators. They will > probably be merged. > probably = wait few years + rather no ;) > What I'm not in favor of however is overloading of "." and such (but you > haven't put

Re: [fpc-pascal] Smart Pointers

2016-05-09 22:11 GMT+02:00 Florian Klämpfl : > Who said that? We discussed the syntax etc. and at least I see good > changes to integrate it in trunk > as soon as it is ready. Neither Sven nor me would discuss a feature if we > are in doubt that it will > make it in trunk.

Re: [fpc-pascal] Smart Pointers

On 09.05.2016 22:11, Florian Klämpfl wrote: > Am 09.05.2016 um 21:40 schrieb Maciej Izak: >> 2016-05-09 19:50 GMT+02:00 Mazo Winst > >: >> >> I read that mails about implementation of management operators and smart >> pointers. >> >> 1

Re: [fpc-pascal] Smart Pointers

Am 09.05.2016 um 21:40 schrieb Maciej Izak: > 2016-05-09 19:50 GMT+02:00 Mazo Winst >: > > I read that mails about implementation of management operators and smart > pointers. > > 1 - These features are expected to be available in

Re: [fpc-pascal] Smart Pointers

2016-05-09 19:50 GMT+02:00 Mazo Winst : > I read that mails about implementation of management operators and smart > pointers. > > 1 - These features are expected to be available in which version? > The feature is ready and works almost perfectly but I need more time to

Re: [fpc-pascal] Smart Pointers

Am 09.05.2016 19:50 schrieb "Mazo Winst" : > > Hello list, > > I don't know if here is the correct place to make this question. > > I read that mails about implementation of management operators and smart pointers. > > 1 - These features are expected to be available in which

[fpc-pascal] Smart Pointers

Hello list, I don't know if here is the correct place to make this question. I read that mails about implementation of management operators and smart pointers. 1 - These features are expected to be available in which version? 2 - Are these features an introduction to Arc objects? Best regards