Re: [fpc-pascal] Namespaces Support

On Mon, Oct 28, 2013 at 12:31 PM, Martin Schreiber wrote: > On Monday 28 October 2013 13:10:04 Dmitry Boyarintsev wrote: > >> > I have, for years, many units that have the prefix 'M'. So I have >> > MClasses, MCore, MTasks, MSystem, etc. >> > Now MSEgui (by Martin Schreiber) introduced a mclasses

Re: [fpc-pascal] Namespaces Support

On Monday 28 October 2013 13:10:04 Dmitry Boyarintsev wrote: > > I have, for years, many units that have the prefix 'M'. So I have > > MClasses, MCore, MTasks, MSystem, etc. > > Now MSEgui (by Martin Schreiber) introduced a mclasses unit -- your > > own implementation of classes unit -- and I can

Re: [fpc-pascal] Namespaces Support

On Mon, Oct 28, 2013 at 9:10 AM, Dmitry Boyarintsev wrote: > On Sun, Oct 27, 2013 at 12:07 PM, Marcos Douglas wrote: >> >> Yes and how I still use D7 at work I still have this problem. >> This problem happen not only for unit names but component names too. I >> can not register two components wit

Re: [fpc-pascal] Namespaces Support

On Sun, Oct 27, 2013 at 12:07 PM, Marcos Douglas wrote: > Yes and how I still use D7 at work I still have this problem. > This problem happen not only for unit names but component names too. I > can not register two components with the same name. > So, because that, programmers around the world u

Re: [fpc-pascal] Namespaces Support

In our previous episode, Marcos Douglas said: > Yes and how I still use D7 at work I still have this problem. > This problem happen not only for unit names but component names too. I > can not register two components with the same name. True. But is maybe because RTTI (and .classname) didn't allow

Re: [fpc-pascal] Namespaces Support

On Sun, Oct 27, 2013 at 12:04 PM, Fabrício Srdic wrote: > 2013/10/27 Marco van de Voort >> >> In our previous episode, Marcos Douglas said: >> > > Namespaces are only for pseudo hierarchical disambiguation of unit >> > > names in >> > > Pascal. >> > >> > Very true. I agree with everything. >> > B

Re: [fpc-pascal] Namespaces Support

On Sun, Oct 27, 2013 at 11:59 AM, Marco van de Voort wrote: > In our previous episode, Marcos Douglas said: >> > Namespaces are only for pseudo hierarchical disambiguation of unit names in >> > Pascal. >> >> Very true. I agree with everything. >> BUT, IMHO, the only problem is if you have two 3rd

Re: [fpc-pascal] Namespaces Support

2013/10/27 Marco van de Voort > In our previous episode, Marcos Douglas said: > > > Namespaces are only for pseudo hierarchical disambiguation of unit > names in > > > Pascal. > > > > Very true. I agree with everything. > > BUT, IMHO, the only problem is if you have two 3rd frameworks that use >

Re: [fpc-pascal] Namespaces Support

In our previous episode, Marcos Douglas said: > > Namespaces are only for pseudo hierarchical disambiguation of unit names in > > Pascal. > > Very true. I agree with everything. > BUT, IMHO, the only problem is if you have two 3rd frameworks that use > the same unit name. In that case I can not ad

Re: [fpc-pascal] Namespaces Support

On Sun, Oct 27, 2013 at 11:13 AM, Marco van de Voort wrote: > In our previous episode, Fabr?cio Srdic said: >> > used in Java and .NET as either languages don't have "units". >> > Adding "features" just because "enterpise-class dev platforms" have them >> > is more marketing move, than actual tech

Re: [fpc-pascal] Namespaces Support

2013/10/27 Marco van de Voort > In our previous episode, Fabr?cio Srdic said: > > > used in Java and .NET as either languages don't have "units". > > > Adding "features" just because "enterpise-class dev platforms" have > them > > > is more marketing move, than actual technical need. > > > > > >

Re: [fpc-pascal] Namespaces Support

In our previous episode, Fabr?cio Srdic said: > > used in Java and .NET as either languages don't have "units". > > Adding "features" just because "enterpise-class dev platforms" have them > > is more marketing move, than actual technical need. > > > > We can't nest units to form a hierarchical co

Re: [fpc-pascal] Namespaces Support

On Sat, Oct 26, 2013 at 11:37 PM, Fabrício Srdic wrote: . > > We can't nest units to form a hierarchical content. With namespaces, we > can. Furthermore, namespaces can be used to disambiguate identifiers with > the same name, eliminating the need to prefix our identifiers. It's a pure > techinica

Re: [fpc-pascal] Namespaces Support

2013/10/27 Dmitry Boyarintsev > D2010 have introduced the namespace feature and DXE2 "forced" us to >> adjust our existing code base to its new unit scope names - namespace of >> its base units - but in return it give us new possibilities to organize our >> existing code base through namespaces,

Re: [fpc-pascal] Namespaces Support

On Sat, Oct 26, 2013 at 9:17 PM, Fabrício Srdic wrote: > D2009 "forced" us to adjust our existing code base to its new > UnicodeString support, but in return it give us internationalization > support and new possibilities. > Again, this is not really accurate. Internationalization is provided by u

Re: [fpc-pascal] Namespaces Support

2013/10/26 waldo kitty > On 10/26/2013 7:06 PM, Fabrício Srdic wrote: > >> If the namespace feature isn't a improvement, so why was it added to fpc? > > because FPC (and lazarus) strives to be better? and to not alienate > those who use it by forcing them to adjust all their working code when a

Re: [fpc-pascal] Namespaces Support

On 10/26/2013 7:06 PM, Fabrício Srdic wrote: If the namespace feature isn't a improvement, so why was it added to fpc? compatibility with delphi products that use it?? -- NOTE: No off-list assistance is given without prior approval. Please keep mailing list traffic on the list unless

Re: [fpc-pascal] Namespaces Support

On 10/25/2013 10:18 PM, Fabrício Srdic wrote: I know I'm a newbie in fpc, myself.. even after almost a decade ;) As Michael and Sven said, if Delphi itself is not fully compatible among versions, why should fpc be? because FPC (and lazarus) strives to be better? and to not alienate those wh

Re: [fpc-pascal] Namespaces Support

2013/10/26 Dmitry Boyarintsev > On Sat, Oct 26, 2013 at 7:06 AM, Fabrício Srdic > wrote: > >> >> I agree with the importance of backward compatibility, but I disagree >> when it becomes a reason to stop the implementation of improvements in the >> tool. >> > > Well, no. You shouldn't say "improv

Re: [fpc-pascal] Namespaces Support

On Sat, Oct 26, 2013 at 7:06 AM, Fabrício Srdic wrote: > > I agree with the importance of backward compatibility, but I disagree when > it becomes a reason to stop the implementation of improvements in the tool. > Well, no. You shouldn't say "improvement". Because "improvement" has positive conte

Re: [fpc-pascal] Namespaces Support

In our previous episode, Dmitry Boyarintsev said: > 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

Re: [fpc-pascal] Namespaces Support

In our previous episode, Fabr?cio Srdic said: > 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. It depends on the improvement. And IMHO this is a meagre o

Re: [fpc-pascal] Namespaces Support

Sven and Leledumbo, I agree with the importance of backward compatibility, but I disagree when it becomes a reason to stop the implementation of improvements in the tool. I remember the nigthmare of migrating my existing codebase to D2009 because of your new UnicodeString support. But, with this

Re: [fpc-pascal] Namespaces Support

Am 26.10.2013 04:18 schrieb "Fabrício Srdic" : > > 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. We value backwards compatibility very high as there is mu

Re: [fpc-pascal] Namespaces Support

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

Re: [fpc-pascal] Namespaces Support

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

Re: [fpc-pascal] Namespaces Support

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

Re: [fpc-pascal] Namespaces Support

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

Re: [fpc-pascal] Namespaces Support

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

Re: [fpc-pascal] Namespaces Support

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

Re: [fpc-pascal] Namespaces Support

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

Re: [fpc-pascal] Namespaces Support

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

Re: [fpc-pascal] Namespaces Support

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

Re: [fpc-pascal] Namespaces Support

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

Re: [fpc-pascal] Namespaces Support

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

Re: [fpc-pascal] Namespaces Support

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

Re: [fpc-pascal] Namespaces Support

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

Re: [fpc-pascal] Namespaces Support

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

Re: [fpc-pascal] Namespaces Support

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

Re: [fpc-pascal] Namespaces Support

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 2013/10/24 Michael Van Canneyt > > > On Thu, 24 Oct 2013, Sven Barth wrote: > > Am 23.10.2013 16:34, sc

Re: [fpc-pascal] Namespaces Support

On Thu, 24 Oct 2013, Sven Barth wrote: Am 23.10.2013 16:34, schrieb Graeme Geldenhuys: Michael, how Delphi-compatible is it?  In Delphi I can use (maybe not the best example) the reference Forms.Application and in the project compiler settings I can say if it is the VCL or the FM

Re: [fpc-pascal] Namespaces Support

Am 23.10.2013 16:34, schrieb Graeme Geldenhuys: Michael, how Delphi-compatible is it? In Delphi I can use (maybe not the best example) the reference Forms.Application and in the project compiler settings I can say if it is the VCL or the FMX namespace, so it knows at compile time which Applica

Re: [fpc-pascal] Namespaces Support

Michael, how Delphi-compatible is it? In Delphi I can use (maybe not the best example) the reference Forms.Application and in the project compiler settings I can say if it is the VCL or the FMX namespace, so it knows at compile time which Application global variable to use. I personally hav

Re: [fpc-pascal] Namespaces Support

2013/10/23 Tomas Hajny > On Wed, October 23, 2013 14:01, Michael Van Canneyt wrote: >> > On Wed, 23 Oct 2013, Fabrício Srdic wrote: >> > >> >> >> >> Thanks! >> >> >> >> When the fpc 2.7.1 will be released? >> > >> > Not in the near future. At least one more year, I suspect. >> >> Just for comple

Re: [fpc-pascal] Namespaces Support

2013/10/23 Paul Ishenin > > 23.10.2013 21:45, silvioprog пишет: > >> >> Any sample showing how to use this feature? >> >> > Either look at fpc tests: > > http://svn.freepascal.org/svn/**fpc/trunk/tests/test/**tdotunits1.pp > http:/

Re: [fpc-pascal] Namespaces Support

23.10.2013 11:12, Fabrício Srdic wrote: Hello guys, I'm new to free-pascal. Will fpc 2.7.x have some namespace implementation/support? Although you already got an answer please note that you can read about comming features on the following page: http://wiki.lazarus.freepascal.org/FPC_New_Fe

Re: [fpc-pascal] Namespaces Support

23.10.2013 21:45, silvioprog пишет: Any sample showing how to use this feature? Either look at fpc tests: http://svn.freepascal.org/svn/fpc/trunk/tests/test/tdotunits1.pp http://svn.freepascal.org/svn/fpc/trunk/tests/test/tdotunits2.pp http://svn.freepascal.org/svn/fpc/trunk/tests/test/tdot

Re: [fpc-pascal] Namespaces Support

2013/10/23 Tomas Hajny > On Wed, October 23, 2013 14:01, Michael Van Canneyt wrote: > > On Wed, 23 Oct 2013, Fabrício Srdic wrote: > > > >> > >> Thanks! > >> > >> When the fpc 2.7.1 will be released? > > > > Not in the near future. At least one more year, I suspect. > > Just for completeness sake

Re: [fpc-pascal] Namespaces Support

On Wed, October 23, 2013 14:01, Michael Van Canneyt wrote: > On Wed, 23 Oct 2013, Fabrício Srdic wrote: > >> >> Thanks! >> >> When the fpc 2.7.1 will be released? > > Not in the near future. At least one more year, I suspect. Just for completeness sake (since you mentioned to be new with FPC) - yo

Re: [fpc-pascal] Namespaces Support

On Wed, 23 Oct 2013, Fabrício Srdic wrote: Thanks! When the fpc 2.7.1 will be released? Not in the near future. At least one more year, I suspect. Michael.___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/ma

Re: [fpc-pascal] Namespaces Support

Thanks! When the fpc 2.7.1 will be released? Em 23/10/2013 09:34, "Michael Van Canneyt" escreveu: > > > On Wed, 23 Oct 2013, Fabrício Srdic wrote: > > >> But I have asked "will fpc 2.7.x have... " ^^... >> > > Yes, and I said: it is already implemented. Obviously, that means it is in > 2.7.1. >

Re: [fpc-pascal] Namespaces Support

On Wed, 23 Oct 2013, Fabrício Srdic wrote: But I have asked "will fpc 2.7.x have... "  ^^... Yes, and I said: it is already implemented. Obviously, that means it is in 2.7.1. It uses the Delphi style notation? It does. Michael.___ fpc-pasc

Re: [fpc-pascal] Namespaces Support

But I have asked "will fpc 2.7.x have... " ^^... It uses the Delphi style notation? Em 23/10/2013 09:04, "Michael Van Canneyt" escreveu: > > > On Wed, 23 Oct 2013, Fabrício Srdic wrote: > > >> How it works? >> >> I have tried to use the Delphi style dotted unit notation but doesn't >> work. >>

Re: [fpc-pascal] Namespaces Support

On Wed, 23 Oct 2013, Fabrício Srdic wrote: How it works? I have tried to use the Delphi style dotted unit notation but doesn't work. I'm using Lazarus 1.0.12 - fpc 2.6.2. Aha: 2.6.2 - You write it :-) Support is in 2.7.1 Michael.___ fpc-pascal

Re: [fpc-pascal] Namespaces Support

How it works? I have tried to use the Delphi style dotted unit notation but doesn't work. I'm using Lazarus 1.0.12 - fpc 2.6.2. Thanks Em 23/10/2013 05:40, "Michael Van Canneyt" escreveu: > > > On Wed, 23 Oct 2013, Fabrício Srdic wrote: > > Hello guys, >> >> I'm new to free-pascal. >> >> Will

Re: [fpc-pascal] Namespaces Support

On Wed, 23 Oct 2013, Fabrício Srdic wrote: Hello guys, I'm new to free-pascal. Will fpc 2.7.x have some namespace implementation/support? It already has. Michael.___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal