Hi,
With development fpc I get a lot of messages like:
fgl.pp(1112,1) Note: (3123) "inherited" not yet supported inside inline
procedure/function
Since most users can't do anything about the fgl inline modifier, this
message dilutes the output.
IMO such a message should be off by default.
Hairy Pixels via fpc-pascal said on Thu, 22 Jun 2023 20:23:13 +0700
>I've forgotten entirely, what does subscripting a pointer do in
>Pascal? p[0] returns 100 but after that garbage. Seems like a c-style
>array which doesn't feel right in the language.
>
>var
> i: Integer;
> p: PInteger;
>begin
> On Jun 24, 2023, at 7:18 PM, Michael Van Canneyt via fpc-pascal
> wrote:
>
> According to Florian, inline should not be used to begin with, since the
> compiler should be able to decide autonomously to inline a routine or not.
Doesn't this mean the compiler can dictate the binary size by
On Sat, 24 Jun 2023, Hairy Pixels via fpc-pascal wrote:
On Jun 24, 2023, at 7:18 PM, Michael Van Canneyt via fpc-pascal
wrote:
According to Florian, inline should not be used to begin with, since the
compiler should be able to decide autonomously to inline a routine or not.
Doesn't
On Sat, 24 Jun 2023, Mattias Gaertner via fpc-pascal wrote:
Hi,
With development fpc I get a lot of messages like:
fgl.pp(1112,1) Note: (3123) "inherited" not yet supported inside inline
procedure/function
Since most users can't do anything about the fgl inline modifier, this
message
Mattias Gaertner via fpc-pascal schrieb
am Sa., 24. Juni 2023, 13:12:
> Hi,
>
> With development fpc I get a lot of messages like:
>
> fgl.pp(1112,1) Note: (3123) "inherited" not yet supported inside inline
> procedure/function
>
> Since most users can't do anything about the fgl inline
> On Jun 24, 2023, at 10:11 PM, Hairy Pixels wrote:
>
> Doesn't this mean the compiler can dictate the binary size by inlining
> everything even if the programmer doesn't want that?
and another thing, I have frequent problems with a crash which happens in an
inlined function and it's now
On Sat, 24 Jun 2023, Hairy Pixels via fpc-pascal wrote:
On Jun 24, 2023, at 10:11 PM, Hairy Pixels wrote:
Doesn't this mean the compiler can dictate the binary size by inlining
everything even if the programmer doesn't want that?
and another thing, I have frequent problems with a
On 24/06/2023 17:21, Hairy Pixels via fpc-pascal wrote:
On Jun 24, 2023, at 10:11 PM, Hairy Pixels wrote:
Doesn't this mean the compiler can dictate the binary size by inlining
everything even if the programmer doesn't want that?
and another thing, I have frequent problems with a crash
Michael Van Canneyt via fpc-pascal
schrieb am Sa., 24. Juni 2023, 14:18:
>
>
> On Sat, 24 Jun 2023, Mattias Gaertner via fpc-pascal wrote:
>
> > Hi,
> >
> > With development fpc I get a lot of messages like:
> >
> > fgl.pp(1112,1) Note: (3123) "inherited" not yet supported inside inline
> >
On Sat, 24 Jun 2023, Sven Barth via fpc-pascal wrote:
Michael Van Canneyt via fpc-pascal
schrieb am Sa., 24. Juni 2023, 14:18:
On Sat, 24 Jun 2023, Mattias Gaertner via fpc-pascal wrote:
Hi,
With development fpc I get a lot of messages like:
fgl.pp(1112,1) Note: (3123) "inherited"
> On Jun 24, 2023, at 8:00 PM, Steve Litt via fpc-pascal
> wrote:
>
> I don't do much with Pascal pointers, but it looks to me like you:
>
> * Set p to the address of i
> * Set the contents of p to 100
> * Read the contents of p, which of course would be the value of i, 100
> * Read the
> On Jun 24, 2023, at 8:37 PM, Sven Barth via fpc-pascal
> wrote:
>
> and thus leading to the necessity to do recompilations which are already not
> working that well.
Speaking of this, I've been including units in the implementation section and
this often totally breaks the compilers
> On Jun 24, 2023, at 10:27 PM, Michael Van Canneyt via fpc-pascal
> wrote:
>
> It seems to me no gain is to be had from e.g. inlining a routine of 500+ lines
> of code.
What if the function was only called from 3 places in the program and each one
of those was in something with very long
14 matches
Mail list logo