grauzone wrote:
Charles Hixson wrote:
I replaced BlockFile.close with:
void close()
{ if (bf !is null) delete bf;//bf.close;
bf = null;
}
But that didn't alter the segmentation fault. (Did you try it under
D1 or D2?)
Your destructor calls close(), and close()
Christopher Wright wrote:
Mike L. wrote:
If the compiler can tell that B!(int) is a type, why can't it tell
that it is a child class of A!(int) ?
This is a bug. In template specializations, : means equality. In static
if, : means convertibility.
This is only with template specializations in
On Fri, Jan 30, 2009 at 5:56 PM, jicman wrote:
> Greetings!
>
> I have done some research on the digitalmars.com for some d code showing UTF8
> to ANSI stuff, and there isn't anything that I can clearly use.
>
> Long story short, I have about 600+ files that I need to convert from UTF8 to
> ANSI
Greetings!
I have done some research on the digitalmars.com for some d code showing UTF8
to ANSI stuff, and there isn't anything that I can clearly use.
Long story short, I have about 600+ files that I need to convert from UTF8 to
ANSI. They have different languages characters. I can do open
On Fri, Jan 30, 2009 at 5:35 PM, BCS wrote:
> Correct me if I'm wrong but I thing that D's opApply is a form of the
> Visitor pattern where the calling function's stack frame is the visitor
> object.
Yeah. As far as I know it is.
Correct me if I'm wrong but I thing that D's opApply is a form of the Visitor
pattern where the calling function's stack frame is the visitor object.
This just occurred to me. Maybe I've been missing something re the visitor
pattern but I think this make for a nice, cool and easy way to describ
naama Wrote:
> How am I get a integer nimber from the user? (readln()?)
>
> the command line is:
> ???
import std.cstream;
int number;
din.readf( "%d", &number );
Steven Schveighoffer wrote:
"Don" wrote
Steven Schveighoffer wrote:
This is such a common "mistake", and really more of an annoyance, I
wonder if it might be better if pow were switched to a template that
called the actual pow after casting the first argument to real. Often
times, one does n
"Don" wrote
> Steven Schveighoffer wrote:
>> This is such a common "mistake", and really more of an annoyance, I
>> wonder if it might be better if pow were switched to a template that
>> called the actual pow after casting the first argument to real. Often
>> times, one does not use reals as
How am I get a integer nimber from the user? (readln()?)
the command line is:
???
I do it, but I also get same answer.
???
> Saaa Wrote:
>
> > Did you set the environment variables?
> > http://www.digitalmars.com/d/1.0/dmd-windows.html
> >
> > I do it, but I also get same answer.
> ???
>
Saaa Wrote:
> Did you set the environment variables?
> http://www.digitalmars.com/d/1.0/dmd-windows.html
>
> I do it, but I also get same answer.
???
Charles Hixson wrote:
I replaced BlockFile.close with:
void close()
{ if (bf !is null) delete bf;//bf.close;
bf = null;
}
But that didn't alter the segmentation fault. (Did you try it under D1
or D2?)
Your destructor calls close(), and close() accesses the refe
Mike L. wrote:
If the compiler can tell that B!(int) is a type, why can't it tell that it is a
child class of A!(int) ?
This is a bug. In template specializations, : means equality. In static
if, : means convertibility.
So, you can use:
template ADefaults(Type, AType)
{
static asser
Steven Schveighoffer wrote:
"Jarrett Billingsley" wrote
On Thu, Jan 29, 2009 at 6:15 PM, Saaa wrote:
That gives the same error.. only casting x to real works :/
That's more an issue with D's extremely (overly?) strict overload
resolution rules. Functions like sin() shouldn't be an issue, sin
15 matches
Mail list logo
