digitalmars.D - sequence matters
- Frank Benoit (14/14) Apr 14 2006 for a mixin it is important where the template is declared.
- Frank Benoit (7/7) Apr 14 2006 Now I can say, it is not my code that is illegal.
- Lars Ivar Igesund (2/4) Apr 14 2006 I think you can with build 2.10
- Derek Parnell (8/12) Apr 14 2006 Build now gives the files to the compiler in the same order that it
- Frank Benoit (2/6) Apr 14 2006 I need it on Linux. I read about actual problems with 2.10 on Linux in
- Derek Parnell (6/12) Apr 14 2006 I hope so. I'll have 2.11 out this weekend sometime.
for a mixin it is important where the template is declared. mixin T!(int); template T(t){ t a; } does not work. Error: mixin forward reference to template. In one module this is no problem. I can modify the sequence. The problem comes, if the template and the mixin are in different modules. I have a lot of templates. Working fine with mixins. Now I added the "import A" to my file "B", and suddenly the compile fails in module "C". In module "C" i also have an "import A" and there I use mixins with templates out of A. Why does the compile of C fail, when I modify B? Is the template/mixin feature really stable?
Apr 14 2006
Now I can say, it is not my code that is illegal. I gave dmd with another source file order a try. Putting my module "B" at the last position. And it works. But now I know, the feature is not reliable. I will encounter more problems in future. And I cannot tell /build/ in which order is should list the source files :( I will make a bug report.
Apr 14 2006
Frank Benoit wrote:And I cannot tell /build/ in which order is should list the source files :(I think you can with build 2.10
Apr 14 2006
On Sat, 15 Apr 2006 03:11:28 +1000, Lars Ivar Igesund <larsivar igesund.net> wrote:Frank Benoit wrote:Build now gives the files to the compiler in the same order that it encounters them. If you have a specific requirement to compile B before A then place B before A on the Build command line, or in a .brf file. -- Derek Parnell Melbourne, AustraliaAnd I cannot tell /build/ in which order is should list the source files :(I think you can with build 2.10
Apr 14 2006
Build now gives the files to the compiler in the same order that it encounters them. If you have a specific requirement to compile B before A then place B before A on the Build command line, or in a .brf file.I need it on Linux. I read about actual problems with 2.10 on Linux in your forum. Are the problems solved?
Apr 14 2006
On Sat, 15 Apr 2006 04:39:10 +1000, Frank Benoit <keinfarbton nospam.xyz> wrote:I hope so. I'll have 2.11 out this weekend sometime. -- Derek Parnell Melbourne, AustraliaBuild now gives the files to the compiler in the same order that it encounters them. If you have a specific requirement to compile B before A then place B before A on the Build command line, or in a .brf file.I need it on Linux. I read about actual problems with 2.10 on Linux in your forum. Are the problems solved?
Apr 14 2006