Hi Martin,
I'm currently developing a Pascal Compiler and I have analyzed (although not
implemented) the best notation on managing objects and I would say, the way you
have defined the syntax for MSELAng is exactly the way I thought it must be.
Using clases like a dereference.
In order to
On Friday 12 May 2017 00:07:09 Fred van Stappen wrote:
> > It is logical that the libraries are bigger because the libraries contain
> > all named code
>
> Huh, :
>
>
> program prognude ;
> begin
> end.
> => 26.9 k
>
> library libnude ;
> begin
> end.
> => 196.3 k
Have you checked with objdump
On Friday 12 May 2017 03:44:30 Edson H wrote:
>
> In order to avoid confusion I would suggest to use some standard or
> recommendation on names, something like "All class names must be preceded
> by the letter C"
>
In MSEgui I use "T" as prefix for class types. All other custom types have no
On Thursday 11 May 2017 14:27:51 Fred van Stappen wrote:
> Hello Martin
>
> >> It is sad that still a fpc library with same code is 5 times bigger than
> >> a fpc executable ( and montain times bigger than same C code compiled
> >> with gcc or clang).
> >
> > Do you know why?
>
> Huh, the answers
Hello Martin
>> It is sad that still a fpc library with same code is 5 times bigger than a
>> fpc executable ( and montain times bigger than same C code compiled with
>> gcc or clang).
> Do you know why?
Huh, the answers in fpc forum are nebulous:
- One said it is because parameter -fPIC is
> It is logical that the libraries are bigger because the libraries contain all
> named code
Huh, :
program prognude ;
begin
end.
=> 26.9 k
library libnude ;
begin
end.
=> 196.3 k
--
Check out the vibrant tech
6 matches
Mail list logo
