Thread overview | |||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
March 12, 2005 DMD 0.117 release | ||||
---|---|---|---|---|
| ||||
Cleaning out the attic of lots of minor bug fixes. http://www.digitalmars.com/d/changelog.html |
March 12, 2005 Re: DMD 0.117 release | ||||
---|---|---|---|---|
| ||||
Posted in reply to Walter | Walter wrote: > Cleaning out the attic of lots of minor bug fixes. > > http://www.digitalmars.com/d/changelog.html > > > horray! i'm not sure if i got the new version, because the command line still says 'DMD .116' though i did get it from ftp://ftp.digitalmars.com/dmd.117.zip one question, though. why doesn't the compiler stop compiling when it gives me warnings? shouldn't warnings just warn and still compile? *confused* thanks. |
March 12, 2005 Re: DMD 0.117 release | ||||
---|---|---|---|---|
| ||||
Posted in reply to Walter | Walter wrote: > Cleaning out the attic of lots of minor bug fixes. > > http://www.digitalmars.com/d/changelog.html Such as # Added pragma(lib, "library name"); Hip. Hip. Hooray! I think a few people have requested this. ;) # cent and ucent are now keywords, to ensure they stay reserved. Great! It nevers hurts to plan ahead. -- Justin (a/k/a jcc7) http://jcc_7.tripod.com/d/ |
March 12, 2005 Re: DMD 0.117 release | ||||
---|---|---|---|---|
| ||||
Posted in reply to clayasaurus | "clayasaurus" <clayasaurus@gmail.com> wrote in message news:d0torr$19ia$1@digitaldaemon.com... > Walter wrote: > > Cleaning out the attic of lots of minor bug fixes. > > > > http://www.digitalmars.com/d/changelog.html > > horray! > > i'm not sure if i got the new version, because the command line still says 'DMD .116' though i did get it from ftp://ftp.digitalmars.com/dmd.117.zip Forgot to copy the linux one in, fixed now. > one question, though. why doesn't the compiler stop compiling when it gives me warnings? shouldn't warnings just warn and still compile? The warnings cause the compiler to stop with a non-zero exit code for those who do automated builds. If it didn't, they'd miss the warnings as the scroll off the screen. |
March 12, 2005 Re: DMD 0.117 release | ||||
---|---|---|---|---|
| ||||
Posted in reply to Walter | Walter, one question: are you going to provide static AA initializers? For the sake if consistency with arrays and structs. And one more: do you have public bugs DB access? I mean to take a look on what is "Fixed D.bugs/1795". Thanks in advance, Andrew. "Walter" <newshound@digitalmars.com> wrote in message news:d0tn63$18an$1@digitaldaemon.com... > Cleaning out the attic of lots of minor bug fixes. > > http://www.digitalmars.com/d/changelog.html > |
March 12, 2005 Re: DMD 0.117 release | ||||
---|---|---|---|---|
| ||||
Posted in reply to Andrew Fedoniouk | "Andrew Fedoniouk" <news@terrainformatica.com> wrote in message news:d0tqj5$1bag$1@digitaldaemon.com... > Walter, one question: > are you going to provide static AA initializers? > For the sake if consistency with arrays and structs. Yes, but not for 1.0. There are some non-trivial decisions that have to be made before it can be implemented. > And one more: do you have public bugs DB access? > I mean to take a look on what is "Fixed D.bugs/1795". That refers to newsgroup posting digitalmars.D.bugs/1795 |
March 12, 2005 Mango and -w | ||||
---|---|---|---|---|
| ||||
Posted in reply to Walter | In article <d0tn63$18an$1@digitaldaemon.com>, Walter says... > >Cleaning out the attic of lots of minor bug fixes. Mango produced three or four of the following warning types, which appear to be bogus: "warning - function mango.io.FileConduit.FileConduit.copy no return at end of function" # FileConduit copy (FilePath source) # { # auto FileConduit fc = new FileConduit (source); # super.copy (fc); # return this; # } Moving along, Mango conjures up a thicket of "implicit conversion of type int to bit can cause loss of data". These are caused by a variation upon this kind of statement: # bool x (int y, int z) # { # return y > z; # } Then, there's a few similar warnings where the sign bit is lost through a legitimate conversion. There's also a few narrowing conversions when interfacing with Win32 functions, and so on. The latter are occasionally related to enum specifications, which could be changed. All in all the warnings found one bug, caused me to cleanup the 'sign' of a few declarations (potentially better codegen), and pointed out that various methods in std.date return a 64-bit long instead of something much smaller (how many hours /are/ there in a day? :-) Definately worthwhile, IMO. I could understand if some complained about "not seeing the forest for the trees", but that's life with a type-system of this nature. I do wonder if there's any value in filtering the warnings somehow. For example, the "int to bit" conversion for returns is one of those "idioms" that Walter talks about; and Mango produces lots of 'em! But then we'd perhaps have to get into warning levels? Oh well. Thanks, Walter. I think this was absolutely worthwhile. |
March 12, 2005 Re: DMD 0.117 release | ||||
---|---|---|---|---|
| ||||
Posted in reply to Walter | Walter wrote: > Cleaning out the attic of lots of minor bug fixes. > > http://www.digitalmars.com/d/changelog.html > Added pragma(lib, "library name"); Excellent. Making library distribution simple just got a whole lot simpler: 1) Store source code in "src/mylibrary/mylibrary.d" 2) Put libraries in "lib/mylibrary.lib" 3) compress all this to .zip 4) Users of the library decompress this archive to d:/path/to/dmd Under such a scheme, projects that wish to use the library do not require so much as a single compile switch. The trick is getting a convention into place. :) -- andy |
March 12, 2005 Re: DMD 0.117 release | ||||
---|---|---|---|---|
| ||||
Posted in reply to Walter | Thanks a lot, Walter. >> are you going to provide static AA initializers? >> For the sake if consistency with arrays and structs. > > Yes, but not for 1.0. There are some non-trivial decisions that have to be made before it can be implemented. Please let me know if you need help here. I guess that {struct aaA} can be used "as is" for placing elements in static section. So lookup procedure can be built on the same principles as lookup in the heap... Andrew. "Walter" <newshound@digitalmars.com> wrote in message news:d0traq$1bvh$1@digitaldaemon.com... > > "Andrew Fedoniouk" <news@terrainformatica.com> wrote in message news:d0tqj5$1bag$1@digitaldaemon.com... >> Walter, one question: >> are you going to provide static AA initializers? >> For the sake if consistency with arrays and structs. > > Yes, but not for 1.0. There are some non-trivial decisions that have to be made before it can be implemented. > >> And one more: do you have public bugs DB access? >> I mean to take a look on what is "Fixed D.bugs/1795". > > That refers to newsgroup posting digitalmars.D.bugs/1795 > > |
March 12, 2005 Re: DMD 0.117 release | ||||
---|---|---|---|---|
| ||||
Posted in reply to J C Calvarese | J C Calvarese wrote:
> Walter wrote:
>
>> Cleaning out the attic of lots of minor bug fixes.
>>
>> http://www.digitalmars.com/d/changelog.html
>
>
> Such as
> # Added pragma(lib, "library name");
> Hip. Hip. Hooray! I think a few people have requested this. ;)
This is great. One less thing for Derek's build to worry about. I'm a little surprised, though, that it suddenly showed up in dmd. Walter showed no indication of adding this pragma, unless I missed a post somewhere. Maybe he just found Derek's build utility /too/ handy! ;-)
-JJR
|
Copyright © 1999-2021 by the D Language Foundation