Mainly bug fixes.

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

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

Walter wrote:
> Mainly bug fixes.
> 
> http://www.digitalmars.com/d/changelog.html
> 
Since you're going (as I see) into heavy de-bugging, do you want any pieces of code that cause problems? If yes, where should I send them?

ssuukk wrote:

> Walter wrote:
>
>> Mainly bug fixes.
>>
>> http://www.digitalmars.com/d/changelog.html
>>
> Since you're going (as I see) into heavy de-bugging, do you want any pieces of code that cause problems? If yes, where should I send them?
>
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.

-Anderson

> 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.
> 
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...

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.
>>
> 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...
>
This is a binary newsgroup so if it's < 200kb (this is just a wild guess 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.

"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!

>>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.
> 
Heh... In this case it is possible to reduce this problem to two files (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?

"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.

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