www.digitalmars.com         C & C++   DMDScript  

D - DMD 0.78 release

reply "Walter" <walter digitalmars.com> writes:
Mainly bug fixes.

http://www.digitalmars.com/d/changelog.html
Jan 14 2004
next sibling parent reply "Matthew" <matthew.hat stlsoft.dot.org> writes:
Hmm. I reckon it could do with a nice memory-mapped file IO module. ;)

"Walter" <walter digitalmars.com> wrote in message
news:bu31vg$6bm$1 digitaldaemon.com...
 Mainly bug fixes.

 http://www.digitalmars.com/d/changelog.html

Jan 14 2004
parent reply "Sean L. Palmer" <palmer.sean verizon.net> writes:
Sure!

Hey, Matthew, thanks alot for making that recls library.  I often want
something like that but end up having to write it myself, in hacked, limited
form, every time.

for (all files mathing pattern in subdirectory, recursive) do something();

Sean

"Matthew" <matthew.hat stlsoft.dot.org> wrote in message
news:bu33kk$8pf$1 digitaldaemon.com...
 Hmm. I reckon it could do with a nice memory-mapped file IO module. ;)

 "Walter" <walter digitalmars.com> wrote in message
 news:bu31vg$6bm$1 digitaldaemon.com...
 Mainly bug fixes.

 http://www.digitalmars.com/d/changelog.html


Jan 20 2004
parent "Matthew" <matthew.hat stlsoft.dot.org> writes:
Pleasure. Good to hear appreciation any time. :)

You can use it from C, C++ (as simple classes, or as STL sequences), C# (or
any .NET), Java and D at the moment.

The next column - May - will cover COM, and the July one will do Python.
Then it's Perl and Ruby, and who knows what after that ...

In the future I plan to expand it to handle recursive FTP handling, but
that's on the back of several higher-priorities.

Matthew

P.S. Any PySequence gurus out there in D land? I may be about to step out of
my comfort zone ...


"Sean L. Palmer" <palmer.sean verizon.net> wrote in message
news:bul8so$2j4i$1 digitaldaemon.com...
 Sure!

 Hey, Matthew, thanks alot for making that recls library.  I often want
 something like that but end up having to write it myself, in hacked,

 form, every time.

 for (all files mathing pattern in subdirectory, recursive) do something();

 Sean

 "Matthew" <matthew.hat stlsoft.dot.org> wrote in message
 news:bu33kk$8pf$1 digitaldaemon.com...
 Hmm. I reckon it could do with a nice memory-mapped file IO module. ;)

 "Walter" <walter digitalmars.com> wrote in message
 news:bu31vg$6bm$1 digitaldaemon.com...
 Mainly bug fixes.

 http://www.digitalmars.com/d/changelog.html



Jan 21 2004
prev sibling parent reply ssuukk <ssuukk .go2.pl> writes:
Walter wrote:
 Mainly bug fixes.
 
 http://www.digitalmars.com/d/changelog.html
 

pieces of code that cause problems? If yes, where should I send them?
Jan 14 2004
parent reply J Anderson <REMOVEanderson badmama.com.au> writes:
ssuukk wrote:

 Walter wrote:

 Mainly bug fixes.

 http://www.digitalmars.com/d/changelog.html

pieces of code that cause problems? If yes, where should I send them?

at your bug report and tell you if it is actually a bug. Also it helps reduce double reporting. I personally use this format: [Bug] The bug. because it makes them easier to find. -Anderson
Jan 14 2004
parent reply ssuukk <ssuukk .go2.pl> writes:
 That's one of the reasons for this group. That way other users can look 
 at your bug report and tell you if it is actually a bug. Also it helps 
 reduce double reporting.
 
 I personally use this format:
 [Bug] The bug.
 because it makes them easier to find.
 

I don't think I should post whole code (which consists of several file) that causes this bug to the newsgroup :-) And I guess Walter needs this code to replicate this problem...
Jan 14 2004
next sibling parent J Anderson <REMOVEanderson badmama.com.au> writes:
ssuukk wrote:

 That's one of the reasons for this group. That way other users can 
 look at your bug report and tell you if it is actually a bug. Also it 
 helps reduce double reporting.

 I personally use this format:
 [Bug] The bug.
 because it makes them easier to find.

But I don't think I should post whole code (which consists of several file) that causes this bug to the newsgroup :-) And I guess Walter needs this code to replicate this problem...

on what is appropriate, this newsgroup can handle much larger files ~ 700kb) it should be ok to send it as an attachment. Otherwise send it to Walters email. Walter prefers it if you can reduce the problem down to the critical code. Anyway, the more bug reports the better. We've gotta get the compiler right.
Jan 14 2004
prev sibling parent reply "Walter" <walter digitalmars.com> writes:
"ssuukk" <ssuukk .go2.pl> wrote in message
news:bu3op2$1aqh$1 digitaldaemon.com...
 Well my bug with static struct pseudo-constructors was posted here. But
 I don't think I should post whole code (which consists of several file)
 that causes this bug to the newsgroup :-) And I guess Walter needs this
 code to replicate this problem...

Pseudo-code doesn't work for me. Realistically, I'm not going to try and recreate a large amount of code to replicate the problem. I need reproducible examples, so email them if they're large. Also, the smaller the source code can be whittled down to to show the problem, frankly, the more likely it is it will get fixed. In my experience, about 98% of problems can be cut down to 10 lines of code or less. Thanks!
Jan 14 2004
next sibling parent reply ssuukk <ssuukk .go2.pl> writes:
Well my bug with static struct pseudo-constructors was posted here. But
I don't think I should post whole code (which consists of several file)
that causes this bug to the newsgroup :-) And I guess Walter needs this
code to replicate this problem...

Pseudo-code doesn't work for me. Realistically, I'm not going to try and recreate a large amount of code to replicate the problem. I need reproducible examples, so email them if they're large. Also, the smaller the source code can be whittled down to to show the problem, frankly, the more likely it is it will get fixed. In my experience, about 98% of problems can be cut down to 10 lines of code or less.

(not less!) because it occurs only, when using modules! Single file compiles without problems, only when I include another module it reports error thinking that "myvector.make(xxx)" is module name instead of static function call! I SUSPECT that this is because the file name in which I define "myvector" struct is also "myvector.d", but still - compier should know when "myvector.make" is class path and when function call, or am I wrong?
Jan 15 2004
parent "Walter" <walter digitalmars.com> writes:
"ssuukk" <ssuukk .go2.pl> wrote in message
news:bu5hd9$14ts$1 digitaldaemon.com...
 I SUSPECT that this is because the file name in which I define
 "myvector" struct is also "myvector.d", but still - compier should know
 when "myvector.make" is class path and when function call, or am I wrong?

The language follows a pretty uniform symbol lookup rule, it does not ignore symbols even if they are obviously wrong.
Jan 15 2004
prev sibling parent reply "Sean L. Palmer" <palmer.sean verizon.net> writes:
Yeah, and aren't the ones that fall into that other 2% a royal bitch!

Occasionally a problem will be such that making a small reprodicible sample
would be 100x more work than you hitting the code in the debugger, seeing
the obvious and writing a quick fix.  Sometimes you may never be able to
send a reproducible sample (machine-specific wierdness)

Sean

"Walter" <walter digitalmars.com> wrote in message
news:bu44bb$1u2r$1 digitaldaemon.com...
 "ssuukk" <ssuukk .go2.pl> wrote in message
 news:bu3op2$1aqh$1 digitaldaemon.com...
 Well my bug with static struct pseudo-constructors was posted here. But
 I don't think I should post whole code (which consists of several file)
 that causes this bug to the newsgroup :-) And I guess Walter needs this
 code to replicate this problem...

Pseudo-code doesn't work for me. Realistically, I'm not going to try and recreate a large amount of code to replicate the problem. I need reproducible examples, so email them if they're large. Also, the smaller

 source code can be whittled down to to show the problem, frankly, the more
 likely it is it will get fixed. In my experience, about 98% of problems

 be cut down to 10 lines of code or less.

 Thanks!

Jan 20 2004
parent "Walter" <walter digitalmars.com> writes:
"Sean L. Palmer" <palmer.sean verizon.net> wrote in message
news:bul93s$2jec$1 digitaldaemon.com...
 Yeah, and aren't the ones that fall into that other 2% a royal bitch!

Yup. Fortunately, they are rare.
 Occasionally a problem will be such that making a small reprodicible

 would be 100x more work than you hitting the code in the debugger, seeing
 the obvious and writing a quick fix.

I still need it reduced down. One reason is that after I fix it, it gets adapted into the D test suite so it never rears its nasty head again.
 Sometimes you may never be able to
 send a reproducible sample (machine-specific wierdness)

That can happen with some kinds of products, but rarely with batch-oriented programs like compilers. From a pragmatic point of view, I'm much more likely to spend time working to fix an obvious problem reproducible in a few lines than a vague problem that comes with 300k of unfamiliar source across dozens of files and some complicated build process that will take a lot of time to figure out. My plate is pretty full <g>, and I am forced to triage things into what's the best return on the time invested.
Jan 21 2004