Op 2010-10-03 18:56, Matt Emson het geskryf:
File.fppl
Or
File.fplib ??
Why force a backward facing legacy on the an OS that does not have such
a restriction? Even NT4 supported longer file extensions.
:-) I must agree with you 100%! So many still use *.cfg or *.txt etc...
for a
Am 04.10.2010 02:43, schrieb Willibald Krenn:
Yes, they probably do. For the beginning (and with generics in
mind) it's probably easier if they do.
don't forget inline as well, not just generics.
Yep. (For inlined methods/functions we could - theoretically - provide a
'non-inlined' version
In our previous episode, Willibald Krenn said:
I don't like the Delph all-or-nothing philosophy here. I'd prefer to
specify the packages, that shall be loaded at runtime, while all other
You can always load packages at runtime.. That is, after the RTL
supports that of course.
Runtime
In our previous episode, Dimitri Smits said:
for
enormous amounts of symbols might be costly (since they are resolved
with a
call per symbol, instead of by one call to the system, as during
startup).
only the symbols that are used are imported in the dyn-loaded package. And
it
On 04/10/2010 09:46, Dimitri Smits wrote:
nope, D7 does this too. (maybe even D5, but cannot verify)
Yes, Delphi 5+ does this. It might even work in 3 or 4, I haven't tried
it. Packages were horribly buggy in 3 from what I remember and I only
used 4 briefly as 5 came out rapidly after we'd
In our previous episode, Dimitri Smits said:
The same effect could be achieved by a separation of packages into
(Lazarus-type) static libraries, and packages *designed* for dynamic
loading (plug-ins...).
Delphi compiler does this as well. One caveat in this discussion is for
instance:
Op 2010-10-04 01:51, Dimitri Smits het geskryf:
fpc-trunc to compile and create a specific bin folder. as far as I've
gathered is that you need to do a make clean all and then copy all the
resulting exe's to somewhere (find and retrieve yourself strategy). But
No, simply specify
In our previous episode, Willibald Krenn said:
Yes, they probably do. For the beginning (and with generics in
mind) it's probably easier if they do.
don't forget inline as well, not just generics.
Yep. (For inlined methods/functions we could - theoretically - provide a
'non-inlined'
Am 04.10.2010 12:35, schrieb Matt Emson:
On 04/10/2010 10:56, Sven Barth wrote:
So I personally would prefer *.ppl (for Pascal Package Library) on
every platform supporting packages.
Scenario - I'm using someother Pascal compiler
(GNU/Delphi/Virtual/etc) so I can use the PPL's from Free
Sent from my iPhone
On 4 Oct 2010, at 04:35, Hans-Peter Diettrich drdiettri...@aol.com wrote:
Dimitri Smits schrieb:
It is therefore simple to say in delphi that you want to build with
rtlXXX.bpl only, but still have the vclXXX.dcp statically linked into
your executable when you use a
- Marco van de Voort mar...@stack.nl schreef:
In our previous episode, Willibald Krenn said:
I don't like the Delph all-or-nothing philosophy here. I'd prefer
to
specify the packages, that shall be loaded at runtime, while all
other
You can always load packages at runtime..
Dimitri Smits schrieb:
if you say you want to build with runtime packages x, y and z, the
linker/compiler take into account that you implicitly dynamically
link to the (units contained in) the packages that package x,y and z
depend on (and recusively until no additional dependencies remain).
Am 04.10.2010 10:39, schrieb Marco van de Voort:
However, at the moment I don't see why this is better than shipping all
necessary ppl files. BTW: I realize that ppl might be a bad TLA - since
it probably means people for quite a number of ppl ;-)
Nah. Just wonder if that is necessary, if
- Hans-Peter Diettrich drdiettri...@aol.com schreef:
Dimitri Smits schrieb:
It is therefore simple to say in delphi that you want to build with
rtlXXX.bpl only, but still have the vclXXX.dcp statically linked
into
your executable when you use a TForm and include the Forms unit
In our previous episode, Hans-Peter Diettrich said:
I fear also a lot of pitfalls with this possibility for example
executables using dyn. packages might be never smartlinked because it is
unknown at link time which packages will be loaded so all symbols of the
statically linked packages
I wonder if there is anything special that hinders the implementation of non-local goto’s and
nested exits in macpas mode. I am asking because emulation through exception-handling does seem to
work (which implies that the code to unwind the stack is there).
For example:
{$mode macpas}
In our previous episode, Sven Barth said:
However, at the moment I don't see why this is better than shipping all
necessary ppl files. BTW: I realize that ppl might be a bad TLA - since
it probably means people for quite a number of ppl ;-)
Nah. Just wonder if that is necessary, if
Am 04.10.2010 11:52, schrieb Marco van de Voort:
In our previous episode, Sven Barth said:
However, at the moment I don't see why this is better than shipping all
necessary ppl files. BTW: I realize that ppl might be a bad TLA - since
it probably means people for quite a number of ppl ;-)
On 04/10/2010 10:56, Sven Barth wrote:
So I personally would prefer *.ppl (for Pascal Package Library) on
every platform supporting packages.
Scenario - I'm using someother Pascal compiler
(GNU/Delphi/Virtual/etc) so I can use the PPL's from Free Pascal with
them? After all, they *are*
Am 04.10.2010 09:35, schrieb Sven Barth:
Yep. (For inlined methods/functions we could - theoretically - provide a
'non-inlined' version in the binary package)
For generics: the token stream is already included in the PPUs (learned
by looking at DoDi's ppudump patches ^^)
This is
Hi!
It seems there is a problem with dynamic arrays which are defined as
static variables in classes.
Type
TTest = class
FDynArr : Array of Integer; static;
End;
When the class is Destroy()ed, the call to CleanupInstance, which calls
fpc_finalize, does a fpc_dynarray_decr_ref which
Hello FPC,
I find a problem that I'm unable to resolve, with my limited skills.
In TReader when a property is a TClass it is being added to be
resolved after all components are loaded, but the Loaded call is
performed before this fixup, so when a component receive the Loaded
signal some fields
22 matches
Mail list logo
