they do

"Carlos" <carlos8294@msn.com> wrote in message news:aeljej$dh8$1@digitaldaemon.com...
>
> "Carlos" <carlos8294@msn.com> escribió en el mensaje news:aelghu$act$2@digitaldaemon.com...
> >
> > "Sean L. Palmer" <seanpalmer@earthlink.net> escribió en el mensaje news:ae6pkd$1bem$1@digitaldaemon.com...
> > > Go to Pavel's DedicateD site and get his Windows.d api wrapper.  It's
> much
> > > more complete than the one that comes with the D compiler.
> > >
> > > Sean
> > >
> > are SetConsoleTextAttribute() and GetStdHandle() already implemented?
> > because i can't get them to work...
> >
> >
>
> ok, sorry. my mistake. they do work. this is what happened: i made a test program and named it color. so when i ran it, nothing happened. obviously! win xp (don't know if 2000 or nt have) has a color command itself!
>
>

On Mon, 17 Jun 2002 22:57:22 -0700 "Sean L. Palmer" <seanpalmer@earthlink.net> wrote:

> stopping adding features to D 1.0.  Unless anyone knows of anything seriously lacking in the language at present which needs immediate addressing.

Well, things that are in the specs but missing from the compiler are property gettors/settors (but I guess we'll see them soon), and inheritance for in & out blocks.

"Sean L. Palmer" <seanpalmer@earthlink.net> wrote in message news:aemhj8$1a3d$1@digitaldaemon.com...
> Walter:  what is the release timetable for D 1.0?  When is beta and
release
> scheduled?   Maybe so we can start debating D 2.0   ;)  Seriously this
seems
> to be gelling... a few bugs and maybe some more optimizations (don't want
to
> make D look bad right off the bat by being the "slow" language) but otherwise the compiler seems pretty solid and getting quite to the point
of
> stopping adding features to D 1.0.  Unless anyone knows of anything seriously lacking in the language at present which needs immediate addressing.

At the moment I think it just needs another go-round to fix the reported bugs, do the property gettor/settor, and it should be beta-able.

Weeee!

"Walter" <walter@digitalmars.com> wrote in message news:aenrvg$2mqr$2@digitaldaemon.com...
>
> At the moment I think it just needs another go-round to fix the reported bugs, do the property gettor/settor, and it should be beta-able.

"Sean L. Palmer" <seanpalmer@earthlink.net> escribió en el mensaje news:aemhj8$1a3d$1@digitaldaemon.com...
> You would also have to link with the Windows DLL which implements GetConsoleScreenBufferInfo and FillConsoleOutputCharacterW.  I believe that's kernel32.dll... so you need an import library kernel32.lib.
Luckily
> it's distributed with D (or should be... on Pavel's site same place as the
> windows.d if not).
>
> Some kind of command like:
>
> c:\dmd\bin\dmd.exe myapp.d kernel32.lib
>
Well, I did that, but nothing else happened. Then I started trying other .lib files (since you said "I believe that's kernel32.dll"), but nothing happened. I even tried this:

dmd myapp *.lib

But it was the same. Another idea?

"Carlos" <carlos8294@msn.com> wrote in message news:aelp0m$imq$1@digitaldaemon.com...

> What's wrong with this code?
>
> void gotoxy(int x, int y) {
>     COORD c;
>     c.X = x - 1;
>     c.Y = y - 1;
>     SetConsoleCursorPosition (GetStdHandle(STD_OUTPUT_HANDLE), c);
> }
>
> by itself, it generates an error (Error 42: Symbol Undefined _SetConsoleCursorPosition@12). what does the @ mean? it's not the line number...

   The @ separates the name from the number of bytes of stack used. It's
generally used for functions that clean up the stack themselves (was that
pascal calling conventions?), I believe. All the windows API functions use
that convention.

   So, the compiler thinks that SetConsoleCursorPosition() accepts 12 bytes,
or three dword parameters. In fact, that API function accepts 8 bytes (2
dwords). COORD contains two SHORT values, which are 16 bits each. So, I
believe it's the wrapper that's wrong.

   In fact, it is. I just went to pavel's site, and downloaded it, and in
line 63:

alias int SHORT;

   this should be... whichever type is a 16-bit signed integer in D. It does
have one, I hope...

Salutaciones,
                         JCAB

>
>    In fact, it is. I just went to pavel's site, and downloaded it, and in
> line 63:
>
> alias int SHORT;
>
>    this should be... whichever type is a 16-bit signed integer in D. It
does
> have one, I hope...
>
> Salutaciones,
>                          JCAB
>
>
so... it should be

alias short SHORT;

?

"Carlos" <carlos8294@msn.com> escribió en el mensaje news:aeo6ie$hq$1@digitaldaemon.com...
> >
> >    In fact, it is. I just went to pavel's site, and downloaded it, and
in
> > line 63:
> >
> > alias int SHORT;
> >
> >    this should be... whichever type is a 16-bit signed integer in D. It
> does
> > have one, I hope...
> >
> > Salutaciones,
> >                          JCAB
> >
> >
> so... it should be
>
> alias short SHORT;
>
> ?
>
Thank you, Juan Carlos! It worked! Pavel, there's a mistake in windows.d

"Carlos" <carlos8294@msn.com> escribió en el mensaje news:aeo6ie$hq$1@digitaldaemon.com...
> >
> >    In fact, it is. I just went to pavel's site, and downloaded it, and
in
> > line 63:
> >
> > alias int SHORT;
> >
> >    this should be... whichever type is a 16-bit signed integer in D. It
> does
> > have one, I hope...
> >
> > Salutaciones,
> >                          JCAB
> >
> >
> so... it should be
>
> alias short SHORT;
>
> ?
>
Know what? wherey() also worked!

"Carlos" <carlos8294@msn.com> wrote in message news:aeo6q5$108$1@digitaldaemon.com...

> > alias short SHORT;
> >
> > ?
> >
> Know what? wherey() also worked!

   :) Cool.

Salutaciones,
                         JCAB