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] fpc/lazarus and kinect sample

On 05/10/2016 04:33 PM, Björn Lundin wrote: I found the nice article "Programming the Microsoft Kinect in Pascal" by Michaël Van Canneyt, in Blaise Pascal Magazine. (Nr 5 / 2013) However, I wonder if anyone have seen the sample code somewhere published on the web ? I do not get it all quite

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);

[fpc-pascal] fpc/lazarus and kinect sample

Hi! I got an xbox 360 kinect, which I'd like to use for controlling a drone (Crazyflie 2). https://www.youtube.com/watch?v=UzFwg2Fpv4E The drone software is all in a virtual machine, and I do not get the kinect to work with that machine. (3d accelerated cards are hard to get to work well) So,

Re: [fpc-pascal] The world is ending

In our previous episode, Jonas Maebe said: > > ExecuteProcess is in trunk since late march. > > > > It is fairly self contained and could be merged to 3.0.2 technically. > > I mentioned that it is in trunk, but it's incomplete: it does not > translate the command line arguments to the code page

[fpc-pascal] RTL and Unicode Strings

Hello all, I am very confused about the way the system codepage are determined. >From what i understand, the string codepage is determined at runtime in a platform dependent manner. Suppose that my app needs to read a file encoded with UTF-8. Suppose that my app runs on Windows, where the system

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] String theory

On 10/05/16 17:48, Tony Whyman wrote: On 10/05/16 14:15, Bart wrote: It already is [part of the string type. See the StringCodePage function. > I don't think this is what I meant as StringCodePage is a unicode > string function. I am looking at the single byte string types.

Re: [fpc-pascal] String theory

Am 2016-05-10 um 17:48 schrieb Tony Whyman: I don't think this is what I meant as StringCodePage is a unicode string function. I am looking at the single byte string types. On 10/05/16 14:15, Bart wrote: It already is [part of the string type. See the StringCodePage function. Codepages

Re: [fpc-pascal] String theory

I don't think this is what I meant as StringCodePage is a unicode string function. I am looking at the single byte string types. On 10/05/16 14:15, Bart wrote: It already is [part of the string type. See the StringCodePage function. ___ fpc-pascal

Re: [fpc-pascal] String theory

On 5/10/16, Tony Whyman wrote: > .. Pascal could be improved by including (for string types) the code > page as part of the string data itself rather than having to infer it. It already is [part of the string type. See the StringCodePage function. Bart

Re: [fpc-pascal] The world is ending

marcov wrote on Tue, 10 May 2016: In our previous episode, Jonas Maebe said: As to the original question: most RTL routines don't care about what the default code page is of ansistrings. Of the ones that do, most have been adapted to deal with changing the default ansistring code page

Re: [fpc-pascal] The world is ending

In our previous episode, Jonas Maebe said: > As to the original question: most RTL routines don't care about what > the default code page is of ansistrings. Of the ones that do, most > have been adapted to deal with changing the default ansistring code > page

Re: [fpc-pascal] The world is ending

On Tue, 10 May 2016, Graeme Geldenhuys wrote: On 2016-05-10 09:40, Michael Van Canneyt wrote: > No idea. As far as I understand pretty much nothing has been done to the > RTL regarding text encodings, so I wouldn't expect too much. Why do you say that ? What would you expect to be done ?

Re: [fpc-pascal] The world is ending

Graeme Geldenhuys wrote on Tue, 10 May 2016: On 2016-05-10 09:40, Michael Van Canneyt wrote: > No idea. As far as I understand pretty much nothing has been done to the > RTL regarding text encodings, so I wouldn't expect too much. Why do you say that ? What would you expect to be done ?

Re: [fpc-pascal] The world is ending

On 2016-05-10 09:40, Michael Van Canneyt wrote: >> > No idea. As far as I understand pretty much nothing has been done to the >> > RTL regarding text encodings, so I wouldn't expect too much. > Why do you say that ? > > What would you expect to be done ? > By that I meant a lot in the RTL is

[fpc-pascal] String theory

While my first thought over the "String Type" or "End of World" threads was this is another "how many angels to the pinhead" type discussion. However, having worked through it, I believe that there is an issue here and Pascal could be improved by including (for string types) the code page as

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] The world is ending

On Tue, 10 May 2016, Graeme Geldenhuys wrote: On 2016-05-10 03:17, Mazo Winst wrote: 1 - So, is there a way to set the codepage to be used by the String type regardless of the platform? Yes, apparently via SetMultiByteConversionCodePage(). I still need to check the documentation to find

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] Warning not to use the "String" type with FPC 3.x

On 2016-05-09 14:41, Michael Schnell wrote: > You can't seriously suggest to dump all code that ever had been written > in Pascal (Delphi Dialect). No, just search and replace all String types with AnsiString and force a specific encoding. Or search and replace all String types with

Re: [fpc-pascal] The world is ending

On 2016-05-10 03:17, Mazo Winst wrote: > 1 - So, is there a way to set the codepage to be used by the String type > regardless of the platform? Yes, apparently via SetMultiByteConversionCodePage(). I still need to check the documentation to find out more details. I think this is what Lazarus is

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] Warning not to use the "String" type with FPC 3.x

On 05/09/2016 11:57 AM, Graeme Geldenhuys wrote: the usage of the aliased "String" type should not be used any more with FPC 3.x. You can't seriously suggest to dump all code that ever had been written in Pascal (Delphi Dialect). -Michael ___