Re: [fpc-pascal] FPReport: Split text across two or more pages

2024-01-01 Thread Michael Van Canneyt via fpc-pascal
On Mon, 1 Jan 2024, Pique7 via fpc-pascal wrote: Hello everyone, I have already asked this and related questions in the Lazarus Forum. I want to improve FPReport in order to use it for my project - if possible. Some features are missing for this, e.g. automatic splitting of text across two

[fpc-pascal] FPReport: Split text across two or more pages

2024-01-01 Thread Pique7 via fpc-pascal
Hello everyone, I have already asked this and related questions in the Lazarus Forum. I want to improve FPReport in order to use it for my project - if possible. Some features are missing for this, e.g. automatic splitting of text across two or more pages. As far as I can judge, the current

Re: [fpc-pascal] How to avoid Copy

2024-01-01 Thread Wayne Sherman via fpc-pascal
On Mon, Jan 1, 2024 at 6:14 AM Hairy Pixels wrote: > > On Jan 1, 2024, at 3:50 PM, Michael Van Canneyt wrote: > > You can't optimize that. As said, a generic is convenient but slow. > > I don't know about that. Like was mentioned the enumerator needs to return a > pointer, preferable without ^ so

Re: [fpc-pascal] How to avoid Copy

2024-01-01 Thread Hairy Pixels via fpc-pascal
> On Jan 1, 2024, at 3:50 PM, Michael Van Canneyt > wrote: > > You can't optimize that. As said, a generic is convenient but slow. I don't know about that. Like was mentioned the enumerator needs to return a pointer, preferable without ^ so it feels like a record and only use that in the

Re: [fpc-pascal] How to avoid Copy

2024-01-01 Thread Michael Van Canneyt via fpc-pascal
On Mon, 1 Jan 2024, Hairy Pixels via fpc-pascal wrote: On Dec 30, 2023, at 3:18 PM, Michael Van Canneyt via fpc-pascal wrote: And try to avoid "for r in data" because it will create a copy for each element in the list. This seems more like bad compiler design than anything. From the