On 10/04/10 18:55, Walter Bright wrote:
with Andrei to do a full day D tutorial. I'm not sure how connected I'll
be with email and stuff.
http://accu.org/index.php/conferences
I hope this goes well for you :) I'm looking forward to videos of the
day for those of us that can't be there, hopefu
with Andrei to do a full day D tutorial. I'm not sure how connected I'll be with
email and stuff.
http://accu.org/index.php/conferences
On 4/8/2010 5:15 AM, #ponce wrote:
Wormhol is a split-screen 3D snake game written in the D programming language.
It Needs Windows, OpenGL 2.0.
Download link: http://adinpsz.org/data/adinpsz_-_Wormhol.zip
Pouet page: http://pouet.net/prod.php?which=54549
I'm very interested in getting bug repor
On 4/9/2010 1:03 PM, digited wrote:
(why SDL?)
I've been asking myself that same question. I realized a few months ago
the only thing in Yage I use it for is to create a window and get input,
and it's kind of sucky at window creation--you can't have more than one
and switcing to/from fullsc
I'm really glad it works on your ATI!
> Beautiful game. Nice music too, where'd you get it?
The music is by maF (http://maf464.free.fr/). He has quite a lot of unrealeased
tracks, and will probably be happy to help out provided you give proper credits.
>
> The only thing I'd change would be t
> Works for me. WinXP sp3, Nvidia 8400M GS
> Quite a nice game).
> Several small problems found :
> 1. It always shows "You win" no matter who dies, even when the last
> survived player.
Yep, shoiuld be "player X win" and keep track of scores.
> 2. On spiky figure those worms sometimes
Eric Poggel Wrote:
> On 4/9/2010 1:03 PM, digited wrote:
> > (why SDL?)
Mostly, legacy :)
>
> I've been asking myself that same question. I realized a few months ago
> the only thing in Yage I use it for is to create a window and get input,
> and it's kind of sucky at window creation--you ca
What's the rationale behind this? (I don't like this).
The flexibility comes in handy now and then.
but isn't that an abstract form of hijacking then?
or an sideeffect smelling like that?
On 09/04/10 23:11, bearophile wrote:
BCS:
For example, having foo_linux.d and foo_win.d both claiming to be foo.
OK.
And I presume you don't want to use a single module with a mega version(linux)
{...} else {...} inside.
Thank you,
bearophile
No need for a huge module, or module names mism
"#ponce" ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ:
news:hpk6rq$fm...@digitalmars.com...
> Wormhol is a split-screen 3D snake game written in the D programming
> language.
> It Needs Windows, OpenGL 2.0.
>
> Download link: http://adinpsz.org/data/adinpsz_-_Wormhol.zip
> Pouet page: http://pouet.net
Hello bearophile,
BCS:
IIRC, all that does is make anything that imports you, import that as
well. It doesn't do anything to the names.
I meant to create a module named "foo" with inside:
module foo;
version (linux) public import foo_linux;
version (Windows) public import foo_win;
The modul
BCS:
> IIRC, all that does is make anything that imports you, import that as well.
> It doesn't do anything to the names.
I meant to create a module named "foo" with inside:
module foo;
version (linux) public import foo_linux;
version (Windows) public import foo_win;
The module system has numer
Hello bearophile,
BCS:
I don't think that works in one case; where you are forced to use
fully qualified name.
You can probably use a "public import".
IIRC, all that does is make anything that imports you, import that as well.
It doesn't do anything to the names.
--
... <
BCS:
> I don't think that works in one case; where you are forced to use fully
> qualified
> name.
You can probably use a "public import".
Bye,
bearophile
Hello Robert,
No need for a huge module, or module names mismatching file names:
module foo;
version (linux) import foo_linux;
version (Windows) import foo_win;
Sure it adds and extra file, it's a lot cleaner imo than having a huge
module with both implementations or mismatching file/m
BCS:
> For example, having foo_linux.d and foo_win.d both claiming to be foo.
OK.
And I presume you don't want to use a single module with a mega version(linux)
{...} else {...} inside.
Thank you,
bearophile
Walter Bright:
> The flexibility comes in handy now and then.
OK, I have never felt the need of such extra flexibility in my D programs, so I
trust your judgement.
Every time a a semantic hole is left in a language (and this is a little hole),
you have to pay a price, in terms for example of:
-
Hello Walter,
bearophile wrote:
Walter Bright:
Thank you for your answer.
The error is not a mismatched file name, which is perfectly
legitimate in D.
Do you mean that in D it is OK to have a file named "foo.d" with
inside it at the top written "module bar;" ?
Yes.
What's the rational
bearophile wrote:
Walter Bright:
Thank you for your answer.
The error is not a mismatched file name, which is perfectly legitimate in
D.
Do you mean that in D it is OK to have a file named "foo.d" with inside it at
the top written "module bar;" ?
Yes.
What's the rationale behind this? (I
Walter Bright:
Thank you for your answer.
> The error is not a mismatched file name, which is perfectly legitimate in D.
Do you mean that in D it is OK to have a file named "foo.d" with inside it at
the top written "module bar;" ?
What's the rationale behind this? (I don't like this).
>The er
Don wrote:
Please don't clutter the announce newsgroup with bug reports.
And in general, do NOT put multiple bugs in one report. In particular,
it's worth saying this to everyone: if something causes a compiler
segfault or an internal compiler error, ALWAYS put it in its own report.
In > 95% o
bearophile wrote:
Now I have tested this release a little better, it seems to work well. I have
to say two things:
1) The bug 3911 was a mix of two different bugs, Don has fixed one of them, so
I have closed the bug 3911 and I have opened a new cleaned bug report, number
4075:
Please don't
22 matches
Mail list logo
