D - DMD 0.66 release
- "Walter" <walter digitalmars.com> Jun 08 2003
- "Carlos Santander B." <carlos8294 msn.com> Jun 08 2003
- Patrick Down <pat codemoon.com> Jun 08 2003
- "Walter" <walter digitalmars.com> Jun 08 2003
- Patrick Down <pat codemoon.com> Jun 09 2003
- "Walter" <walter digitalmars.com> Jun 09 2003
- Patrick Down <Patrick_member pathlink.com> Jun 09 2003
- "Walter" <walter digitalmars.com> Jun 09 2003
- Patrick Down <Patrick_member pathlink.com> Jun 09 2003
- "Walter" <walter digitalmars.com> Jun 09 2003
- Patrick Down <pat codemoon.com> Jun 09 2003
- Patrick Down <pat codemoon.com> Jun 09 2003
- "Walter" <walter digitalmars.com> Jun 09 2003
- Russ Lewis <spamhole-2001-07-16 deming-os.org> Jun 10 2003
- "Carlos Santander B." <carlos8294 msn.com> Jun 10 2003
- "Walter" <walter digitalmars.com> Jun 11 2003
- Andy Friesen <andy ikagames.com> Jun 11 2003
- Georg Wrede <Georg_member pathlink.com> Jun 11 2003
Many minor bugs fixed. http://www.digitalmars.com/d/changelog.html
Jun 08 2003
I've been wanting to ask this for a couple of weeks now, and now I feel it's a good time to do so. Are there any major changes expected in the language design? Because I'm starting to believe that it could be a good moment to have a final release. What do you all think? ————————————————————————— Carlos Santander --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.488 / Virus Database: 287 - Release Date: 2003-06-05
Jun 08 2003
"Walter" <walter digitalmars.com> wrote in news:bc0d2j$20r6$1 digitaldaemon.com:http://www.digitalmars.com/d/changelog.html
What happened to the -o option? It used to let me set the obj file directory.
Jun 08 2003
"Patrick Down" <pat codemoon.com> wrote in message news:Xns9394EC4C4963patcodemooncom 63.105.9.61..."Walter" <walter digitalmars.com> wrote in news:bc0d2j$20r6$1 digitaldaemon.com:http://www.digitalmars.com/d/changelog.html
What happened to the -o option? It used to let me set the obj file directory.
Hmm. Nothing should have happened to it!
Jun 08 2003
"Walter" <walter digitalmars.com> wrote in news:bc13ci$2k3c$1 digitaldaemon.com:"Patrick Down" <pat codemoon.com> wrote in message news:Xns9394EC4C4963patcodemooncom 63.105.9.61..."Walter" <walter digitalmars.com> wrote in news:bc0d2j$20r6$1 digitaldaemon.com:http://www.digitalmars.com/d/changelog.html
What happened to the -o option? It used to let me set the obj file directory.
Hmm. Nothing should have happened to it!
The "help" listed below has two definitions for it and "-o filename name output file" seems to be the fuctionality now. Digital Mars D Compiler Beta v0.65 Copyright (c) 1999-2003 by Digital Mars written by Walter Bright www.digitalmars.com/d/index.html Usage: dmd files.d ... { -switch } files.d D source files -c do not link -d allow deprecated features -g add symbolic debug info -gt add trace profiling hooks -v verbose -O optimize -oobjdir write object files to directory objdir -o filename name output file -Ipath where to look for imports -Llinkerflag pass linkerflag to link -debug compile in debug code -debug=level compile in debug code <= level -debug=ident compile in debug code identified by ident -inline do function inlining -release compile release version -unittest compile in unit tests -version=level compile in version code >= level -version=ident compile in version code identified by ident
Jun 09 2003
Are you using the windows or linux version? "Patrick Down" <pat codemoon.com> wrote in message news:Xns939555016675patcodemooncom 63.105.9.61..."Walter" <walter digitalmars.com> wrote in news:bc13ci$2k3c$1 digitaldaemon.com:"Patrick Down" <pat codemoon.com> wrote in message news:Xns9394EC4C4963patcodemooncom 63.105.9.61..."Walter" <walter digitalmars.com> wrote in news:bc0d2j$20r6$1 digitaldaemon.com:http://www.digitalmars.com/d/changelog.html
What happened to the -o option? It used to let me set the obj file directory.
Hmm. Nothing should have happened to it!
The "help" listed below has two definitions for it and "-o filename name output file" seems to be the fuctionality now. Digital Mars D Compiler Beta v0.65 Copyright (c) 1999-2003 by Digital Mars written by Walter Bright www.digitalmars.com/d/index.html Usage: dmd files.d ... { -switch } files.d D source files -c do not link -d allow deprecated features -g add symbolic debug info -gt add trace profiling hooks -v verbose -O optimize -oobjdir write object files to directory objdir -o filename name output file -Ipath where to look for imports -Llinkerflag pass linkerflag to link -debug compile in debug code -debug=level compile in debug code <= level -debug=ident compile in debug code identified by ident -inline do function inlining -release compile release version -unittest compile in unit tests -version=level compile in version code >= level -version=ident compile in version code identified by ident
Jun 09 2003
In article <bc2b9u$n5v$1 digitaldaemon.com>, Walter says...Are you using the windows or linux version?
Windows
Jun 09 2003
"Patrick Down" <Patrick_member pathlink.com> wrote in message news:bc2bj8$nhv$1 digitaldaemon.com...In article <bc2b9u$n5v$1 digitaldaemon.com>, Walter says...Are you using the windows or linux version?
Here's how it works. If linking, the -o is assumed to be the executable file name. If not linking, and the filename ends in .obj, it is assumed to be the output .obj name. Otherwise, it is taken to be the output directory.
Jun 09 2003
In article <bc2i1i$tu0$1 digitaldaemon.com>, Walter says..."Patrick Down" <Patrick_member pathlink.com> wrote in message news:bc2bj8$nhv$1 digitaldaemon.com...In article <bc2b9u$n5v$1 digitaldaemon.com>, Walter says...Are you using the windows or linux version?
Here's how it works. If linking, the -o is assumed to be the executable file name. If not linking, and the filename ends in .obj, it is assumed to be the output .obj name. Otherwise, it is taken to be the output directory.
Ok, I understand. But it would seem desirable to have a separate flag for the output file and intermediate dicrectory.
Jun 09 2003
"Patrick Down" <Patrick_member pathlink.com> wrote in message news:bc2ml4$12aj$1 digitaldaemon.com...In article <bc2i1i$tu0$1 digitaldaemon.com>, Walter says..."Patrick Down" <Patrick_member pathlink.com> wrote in message news:bc2bj8$nhv$1 digitaldaemon.com...In article <bc2b9u$n5v$1 digitaldaemon.com>, Walter says...Are you using the windows or linux version?
Here's how it works. If linking, the -o is assumed to be the executable
name. If not linking, and the filename ends in .obj, it is assumed to be
output .obj name. Otherwise, it is taken to be the output directory.
Ok, I understand. But it would seem desirable to have a separate flag for
output file and intermediate dicrectory.
You're right, it is a little confusing.
Jun 09 2003
"Walter" <walter digitalmars.com> wrote in news:bc0d2j$20r6$1 digitaldaemon.com:Many minor bugs fixed. http://www.digitalmars.com/d/changelog.html
The following should print: count = 10 instead it prints: count = 0 class Foo { void Func(bit delegate() call) { for(int i = 0; i < 10; ++i) call(); } } class Bar { void Func() { int count = 0; Foo ic = new Foo(); ic.Func(delegate bit() { ++count; return false; } ); printf("count = %d\n",count); } } int main(char[][] argv) { Bar b = new Bar(); b.Func(); return 0; }
Jun 09 2003
"Walter" <walter digitalmars.com> wrote in news:bc0d2j$20r6$1 digitaldaemon.com:Many minor bugs fixed. http://www.digitalmars.com/d/changelog.html
Walter the Windows version in the latest zip file has version number 0.65 did it get updated to 0.66? It was downloaded from ftp://ftp.digitalmars.com/dmd.zip
Jun 09 2003
"Patrick Down" <pat codemoon.com> wrote in message news:Xns9395D338E3F2Epatcodemooncom 63.105.9.61...Walter the Windows version in the latest zip file has version number 0.65 did it get updated to 0.66? It was downloaded from ftp://ftp.digitalmars.com/dmd.zip
Yeah, I know. <g>. It's still 0.66, though.
Jun 09 2003
The following source prints out "default" on dmd linux 0.66:
int main(char[][] args)
{
switch("asdf")
{
case "asdf":
printf("asdf\n");
break;
case "jkl":
printf("jkl\n");
break;
default:
printf("default\n");
}
return 0;
}
If I change the switch to switch on args[1], then the switch works as it
should.
Jun 10 2003
I have this:
-----a.d
class A {}
-----b.d
private import a;
class B:A {}
-----c.d
import b;
B x; //works
A y; //doesn't work. great!
b.a.A z; //works
My question is if the last line should work. I'm not saying it shouldn't, I
just want to know.
—————————————————————————
Carlos Santander
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.488 / Virus Database: 287 - Release Date: 2003-06-05
Jun 10 2003
"Carlos Santander B." <carlos8294 msn.com> wrote in message news:bc61cl$vr7$1 digitaldaemon.com...I have this: -----a.d class A {} -----b.d private import a; class B:A {} -----c.d import b; B x; //works A y; //doesn't work. great! b.a.A z; //works My question is if the last line should work. I'm not saying it shouldn't,
just want to know.
I know about that case, and have mixed feelings about whether it should work that way or be a bug.
Jun 11 2003
Walter wrote:"Carlos Santander B." <carlos8294 msn.com> wrote in message news:bc61cl$vr7$1 digitaldaemon.com...I have this: -----a.d class A {} -----b.d private import a; class B:A {} -----c.d import b; B x; //works A y; //doesn't work. great! b.a.A z; //works My question is if the last line should work. I'm not saying it shouldn't,
Ijust want to know.
I know about that case, and have mixed feelings about whether it should work that way or be a bug.
Since b is its own namespace, I can't see how that could ever cause a problem. In fact, it looks like a useful construct, since it forces the fully qualified name to be used. It is kind of misleading, though, seeing as how private tends to indicate that nobody outside the module should be able to see it. Perhaps a protected import, or something of the like, is in order.
Jun 11 2003
In article <bc7b28$24th$1 digitaldaemon.com>, Andy Friesen says...Walter wrote:"Carlos Santander B." <carlos8294 msn.com> wrote in message news:bc61cl$vr7$1 digitaldaemon.com...I have this: -----a.d class A {} -----b.d private import a; class B:A {} -----c.d import b; B x; //works A y; //doesn't work. great! b.a.A z; //works My question is if the last line should work. I'm not saying it shouldn't,
Ijust want to know.
I know about that case, and have mixed feelings about whether it should work that way or be a bug.
Since b is its own namespace, I can't see how that could ever cause a problem. In fact, it looks like a useful construct, since it forces the fully qualified name to be used. It is kind of misleading, though, seeing as how private tends to indicate that nobody outside the module should be able to see it. Perhaps a protected import, or something of the like, is in order.
I think it definitely should not work. One way to think about it is: If b does a PRIVATE import, then the understood meaning is that b does not want the whole world to gain access to all of a. To let b.a.A work here would need a SERIOUS argument for it. We're developing a Straightforward language without undue catches and complications.
Jun 11 2003









"Carlos Santander B." <carlos8294 msn.com> 