Not really namespace related, but:
Most of the commercial/free/open source Delphi/FPC libraries are backward
compatible to D7-D6 (including all Delphi-win32 versions)
That comes with a cost (a bless) of not using new language syntax (as much
as possible).
And typically include a long-long ".inc" th
I know I'm a newbie in fpc, but I don't see backward compatibility a reason
enough to leave to implement some improvements, like organize the
base units of the fpc into proper namespaces.
As Michael and Sven said, if Delphi itself is not fully compatible among
versions, why should fpc be?
Accordi
On Fri, 25 Oct 2013, Marco van de Voort wrote:
No one forces anything. You can perfectly set the default namespace to
'fpc' (or whatever) in the default config file, and all should compile as it
was.
Yes. One can live with the XE2+ renaming at the cost of renaming units,
potentially fixing
Am 25.10.2013 16:21 schrieb "Marco van de Voort" :
> > In my opinion, this constitutes exactly:
> > 1. Being very consequent.
>
> Leaving out D2009-DXE?
>
Default namespaces again.
> > 2. Caring about backwards compatibility.
>
> Only the one you want. I'm more interested in D2009 compatibility t
In our previous episode, Michael Van Canneyt said:
> >> Strange reaction.
> >>
> >> As I said: the above scenario is the very reason why namespaces were
> >> invented to begin with.
> >
> > Not that I can see. It seems that Embarcadero used it mostly for own
> > purposes, not the users, and their s
2013/10/24 LacaK
> silvioprog wrote / napísal(a):
>
> Hello,
>>
>> This morning, I compiled a code using FPC (Windows, rev. 2013/09/01),
>> after that, my tests using dataset.locate has stopped.
>>
>> The Locate method locates record, even when it does not exists. The
>> problem occurs only wit
On Fri, 25 Oct 2013, Marco van de Voort wrote:
In our previous episode, Michael Van Canneyt said:
Yes. And he deserves it IMHO.
Strange reaction.
As I said: the above scenario is the very reason why namespaces were
invented to begin with.
Not that I can see. It seems that Embarcadero use
In our previous episode, Michael Van Canneyt said:
> > Yes. And he deserves it IMHO.
>
> Strange reaction.
>
> As I said: the above scenario is the very reason why namespaces were
> invented to begin with.
Not that I can see. It seems that Embarcadero used it mostly for own
purposes, not the use
On Fri, 25 Oct 2013, Tomas Hajny wrote:
On Fri, October 25, 2013 10:51, Michael Van Canneyt wrote:
On Fri, 25 Oct 2013, Marco van de Voort wrote:
In our previous episode, Michael Van Canneyt said:
Delphi uses winapi, not windows.
And I see no need. There is so much code in use that assumes
On Fri, October 25, 2013 10:51, Michael Van Canneyt wrote:
> On Fri, 25 Oct 2013, Marco van de Voort wrote:
>> In our previous episode, Michael Van Canneyt said:
Delphi uses winapi, not windows.
And I see no need. There is so much code in use that assumes the
standard
names
On Fri, 25 Oct 2013, Marco van de Voort wrote:
In our previous episode, Michael Van Canneyt said:
Delphi uses winapi, not windows.
And I see no need. There is so much code in use that assumes the standard
names, and I don't see a need to force existing codebase users to rename
everything jus
Am 25.10.2013 09:24, schrieb Marco van de Voort:
In our previous episode, Fabr?cio Srdic said:
e.g types -> system.types; winsock -> windows.winsock; winmouse ->
windows.winmouse
Delphi uses winapi, not windows.
And I see no need. There is so much code in use that assumes the standard
names, a
In our previous episode, Michael Van Canneyt said:
> > Delphi uses winapi, not windows.
> >
> > And I see no need. There is so much code in use that assumes the standard
> > names, and I don't see a need to force existing codebase users to rename
> > everything just to free up a few unit names for
On Fri, 25 Oct 2013, Marco van de Voort wrote:
In our previous episode, Fabr?cio Srdic said:
e.g types -> system.types; winsock -> windows.winsock; winmouse ->
windows.winmouse
Delphi uses winapi, not windows.
And I see no need. There is so much code in use that assumes the standard
names
In our previous episode, Fabr?cio Srdic said:
>
> e.g types -> system.types; winsock -> windows.winsock; winmouse ->
> windows.winmouse
Delphi uses winapi, not windows.
And I see no need. There is so much code in use that assumes the standard
names, and I don't see a need to force existing codeb
On Fri, 25 Oct 2013, Xiangrong Fang wrote:
Hi,
First of all, I did some research and found this:
http://free-pascal-general.1045716.n5.nabble.com/Compiler-Warning-Constructor-should-be-public-td2825747.html
But that did not convince me. So here is my situation and question.
I have the foll
On Fri, October 25, 2013 02:24, Fabrício Srdic wrote:
> With the new namespace support feature, will the fpc standard and base
> units be structured into packages?
>
> e.g types -> system.types; winsock -> windows.winsock; winmouse ->
> windows.winmouse
Would it bring any benefits? E.g. having uni
17 matches
Mail list logo
