digitalmars.D.learn - What is wrong with this boilerplate mixin?

AF (51/51) Oct 22 2006 Hello,

Max Samuha (10/24) Oct 23 2006 The mixed-in WinMain is mangled like

AF (13/13) Oct 23 2006 Thank you very much. But, at the moment, I would like to stay in

Chris Nicholson-Sauls (7/22) Oct 23 2006 Actually, you /can/ use just main(), which is my personal preferance. J...

AF (11/11) Oct 23 2006 Thanks for the hint. It was the hInstance I was missing up without

Don Clugston (7/22) Oct 23 2006 If this is exactly what you typed, the reason is simple -- dmd doesn't
Carlos Santander (4/22) Oct 23 2006 D:\temp\dlang5>dmd appwin.d modwin.d

Max Samuha (6/26) Oct 23 2006 Oops. I didn't notice that the second file was not included.

Carlos Santander (7/36) Oct 23 2006 I don't use Windows, so I can't test your code, but I think it should wo...

AF (2/2) Oct 23 2006 Thanks, but I think simpler than that is almost impossible: all I

BCS (4/8) Oct 23 2006 you might try:

Max Samuha (37/37) Oct 23 2006 begin 644 appwin.d

AF (17/17) Oct 24 2006 Thanks for the code. I also implemented a simple win app using the

Max Samuha (28/45) Oct 24 2006 Do you know how to access nCmdShow param? User may set the initial

AF (4/4) Oct 24 2006 No, I don't know how to access the nCmdShow parameter.

Max Samuha (4/8) Oct 26 2006 Sorry, I failed to figure out how to access nCmdShow from main().

Serg Kovrov (6/10) Nov 04 2006 You could use Windows API GetStartupInfo()

AF (6/6) Nov 05 2006 Thanks. I will do some further reading on that API.

AF <noemail noemail.com> writes:

Hello,

 To make Win programming simpler, I divided sample application
(winsample.d) in a standard module (modwin.d) containing the
boilerplate code, and a application (appwin.d) file.
 Both files resides in the same directory.
 However, it does not link:

 D:\temp\dlang5>dmd appwin.d
c:\dmd\bin\..\..\dm\bin\link.exe appwin,,,user32+kernel32/noi;
OPTLINK (R) for Win32  Release 7.50B1
Copyright (C) Digital Mars 1989 - 2001  All Rights Reserved

c:\dm\bin\..\lib\SNN.lib(winstart)
 Error 42: Symbol Undefined _WinMain 16

 So, what to do? And, 2nd, could things be made simpler? Attached
are modwin.d and appwin.d.
begin 644 appwin.d
M:6UP;W)T(&UO9'=I;CL-"FEM<&]R="!S=&0N8RYW:6YD;W=S+G=I;F1O=W,[


M;61,:6YE+&EN="!N0VUD4VAO=RD-"GL-" E-97-S86=E0F]X02AN=6QL+")-

M+BXN(&EN<V5R="!U<V5R(&-O9&4 :&5R92`N+BX *B\-"B` ("!R971U<FX 
%,#L-"GT`
`
end
begin 644 modwin.d
M;6]D=6QE(&UO9'=I;CL-" T*<')I=F%T92!I;7!O<G0 <W1D+F,N=VEN9&]W


M:70H*3L-"F5X=&5R;B`H0RD =F]I9"!?;6]D=6QE0W1O<B I.PT*97AT97)N


M=&5R;B`H5VEN9&]W<RD-" EI;G0 5VEN36%I;BA(24Y35$%.0T4 :$EN<W1A


M8U]I;FET*"D["0D)+R\ :6YI=&EA;&EZ92!G87)B86=E(&-O;&QE8W1O< T*
M"2` ("!?;6EN:70H*3L)"0DO+R!I;FET:6%L:7IE(&UO9'5L92!C;VYS=')U
M8W1O<B!T86)L90T*"0T*"2` ("!T<GD-" D ("` >PT*"0E?;6]D=6QE0W1O

M;FET5&5S=',H*3L)+R\ <G5N('5N:70 =&5S=', *&]P=&EO;F%L*0T*"0T*
M"0ER97-U;'0 /2!M>5=I;DUA:6XH:$EN<W1A;F-E+"!H4')E=DEN<W1A;F-E


M8V%T8V  *$]B:F5C="!O*0D)+R\ 8V%T8V  86YY('5N8V%U9VAT(&5X8V5P
M=&EO;G,-" D ("` >PT*"0E-97-S86=E0F]X02AN=6QL+"!C87-T*&-H87( 


M("` ('T-" D-" D ("` 9V-?=&5R;2 I.PD)"2\O(')U;B!F:6YA;&EZ97)S
M.R!T97)M:6YA=&4 9V%R8F%G92!C;VQL96-T;W(-" D ("` <F5T=7)N(')E
,<W5L=#L-
`
end

Oct 22 2006

Max Samuha <maxter i.com.ua> writes:

On Mon, 23 Oct 2006 05:56:08 +0000 (UTC), AF <noemail noemail.com>
wrote:

Hello,

 To make Win programming simpler, I divided sample application
(winsample.d) in a standard module (modwin.d) containing the
boilerplate code, and a application (appwin.d) file.
 Both files resides in the same directory.
 However, it does not link:

 D:\temp\dlang5>dmd appwin.d
c:\dmd\bin\..\..\dm\bin\link.exe appwin,,,user32+kernel32/noi;
OPTLINK (R) for Win32  Release 7.50B1
Copyright (C) Digital Mars 1989 - 2001  All Rights Reserved

c:\dm\bin\..\lib\SNN.lib(winstart)
 Error 42: Symbol Undefined _WinMain 16

 So, what to do? And, 2nd, could things be made simpler? Attached
are modwin.d and appwin.d.

The mixed-in WinMain is mangled like
__D6appwin11__T6WinAppZ7WinMainWT3std1c7windows7windows6HANDLET3std1c7windows7windows6HANDLEPaiZi 16
instead of _WinMain 16. This might be because the compiler doesn't
handle extern(Windows) properly in the template. You could declare a
global delegate in modwin which will be called in WinMain (instead of
directly calling your myWinMain) and attach myWinMain to it in the
static constructor of appwin. Or you could use DFL or other
application framework.

Oct 23 2006

AF <noemail noemail.com> writes:

 Thank you very much. But, at the moment, I would like to stay in
vanilla win32api framework.
 Second, I do not really need an workaround: it is the intended
behaviour of dmd to mangle functions that way, or it is improper
use of syntax (i.e. my fault)?.
 I simply find ugly to bear all that gc boilerplate code with any
application when things could be simpler. Any reason why not all gc
code should be directly integrated in phobos (or dmd) WinMain
function? (actually, why have WinMain() at all and not just main()?)
 As for delegates, could you (or someone else) be so kind to
provide my an example based on the code and ideea I submitted?

 Thanks in advance.

 AF

Oct 23 2006

Chris Nicholson-Sauls <ibisbasenji gmail.com> writes:

AF wrote:
  Thank you very much. But, at the moment, I would like to stay in
 vanilla win32api framework.
  Second, I do not really need an workaround: it is the intended
 behaviour of dmd to mangle functions that way, or it is improper
 use of syntax (i.e. my fault)?.
  I simply find ugly to bear all that gc boilerplate code with any
 application when things could be simpler. Any reason why not all gc
 code should be directly integrated in phobos (or dmd) WinMain
 function? (actually, why have WinMain() at all and not just main()?)
  As for delegates, could you (or someone else) be so kind to
 provide my an example based on the code and ideea I submitted?
 
  Thanks in advance.
 
  AF

Actually, you /can/ use just main(), which is my personal preferance.  Just a
couple of 
things to consider.  First, in order to ensure you get an exe which doesn't pop
up a 
console window, pass '-L/exet:nt/su:windows:4.0' to the compiler.  (Or whatever
would be 
most appropriate).  Second, to get your hInstance you will need to call 
GetModuleHandle(NULL) and store its return.

-- Chris Nicholson-Sauls

Oct 23 2006

AF <noemail noemail.com> writes:

Thanks for the hint. It was the hInstance I was missing up without
WinMain.

I think the official recommandation (and example) should be with
main() not with WinMain(). For all old Win programmers, WinMain
could be obvious. However, for a novice it seems pretty confusing
to change paradigm according to OS and maybe bracket everything
with version(){}.

My opinion, however.

Thanks for the submitted code (with function pointers) and for
overall help. I will give it a try.

AF

Oct 23 2006

Don Clugston <dac nospam.com.au> writes:

AF wrote:
 Hello,
 
  To make Win programming simpler, I divided sample application
 (winsample.d) in a standard module (modwin.d) containing the
 boilerplate code, and a application (appwin.d) file.
  Both files resides in the same directory.
  However, it does not link:
 
  D:\temp\dlang5>dmd appwin.d
 c:\dmd\bin\..\..\dm\bin\link.exe appwin,,,user32+kernel32/noi;
 OPTLINK (R) for Win32  Release 7.50B1
 Copyright (C) Digital Mars 1989 - 2001  All Rights Reserved
 
 c:\dm\bin\..\lib\SNN.lib(winstart)
  Error 42: Symbol Undefined _WinMain 16

If this is exactly what you typed, the reason is simple -- dmd doesn't 
automatically link the modwin.d file.
Try:
dmd appwin.d modwin.d

or download build from dsource, and type
build appwin.d

Oct 23 2006

Carlos Santander <csantander619 gmail.com> writes:

AF escribió:
 Hello,
 
  To make Win programming simpler, I divided sample application
 (winsample.d) in a standard module (modwin.d) containing the
 boilerplate code, and a application (appwin.d) file.
  Both files resides in the same directory.
  However, it does not link:
 
  D:\temp\dlang5>dmd appwin.d
 c:\dmd\bin\..\..\dm\bin\link.exe appwin,,,user32+kernel32/noi;
 OPTLINK (R) for Win32  Release 7.50B1
 Copyright (C) Digital Mars 1989 - 2001  All Rights Reserved
 
 c:\dm\bin\..\lib\SNN.lib(winstart)
  Error 42: Symbol Undefined _WinMain 16
 
  So, what to do? And, 2nd, could things be made simpler? Attached
 are modwin.d and appwin.d.

D:\temp\dlang5>dmd appwin.d modwin.d

-- 
Carlos Santander Bernal

Oct 23 2006

Max Samuha <maxter i.com.ua> writes:

On Mon, 23 Oct 2006 07:54:30 -0500, Carlos Santander
<csantander619 gmail.com> wrote:

AF escribio:
 Hello,
 
  To make Win programming simpler, I divided sample application
 (winsample.d) in a standard module (modwin.d) containing the
 boilerplate code, and a application (appwin.d) file.
  Both files resides in the same directory.
  However, it does not link:
 
  D:\temp\dlang5>dmd appwin.d
 c:\dmd\bin\..\..\dm\bin\link.exe appwin,,,user32+kernel32/noi;
 OPTLINK (R) for Win32  Release 7.50B1
 Copyright (C) Digital Mars 1989 - 2001  All Rights Reserved
 
 c:\dm\bin\..\lib\SNN.lib(winstart)
  Error 42: Symbol Undefined _WinMain 16
 
  So, what to do? And, 2nd, could things be made simpler? Attached
 are modwin.d and appwin.d.

D:\temp\dlang5>dmd appwin.d modwin.d

Oops. I didn't notice that the second file was not included.

Anyway, even if you include the file, the definition of WinMain will
not be found because of mangling. I attached the code that uses a
function pointer (i called it delegate mistakingly).

Oct 23 2006

Carlos Santander <csantander619 gmail.com> writes:

Max Samuha escribi�:
 On Mon, 23 Oct 2006 07:54:30 -0500, Carlos Santander
 <csantander619 gmail.com> wrote:
 
 AF escribio:
 Hello,

  To make Win programming simpler, I divided sample application
 (winsample.d) in a standard module (modwin.d) containing the
 boilerplate code, and a application (appwin.d) file.
  Both files resides in the same directory.
  However, it does not link:

  D:\temp\dlang5>dmd appwin.d
 c:\dmd\bin\..\..\dm\bin\link.exe appwin,,,user32+kernel32/noi;
 OPTLINK (R) for Win32  Release 7.50B1
 Copyright (C) Digital Mars 1989 - 2001  All Rights Reserved

 c:\dm\bin\..\lib\SNN.lib(winstart)
  Error 42: Symbol Undefined _WinMain 16

  So, what to do? And, 2nd, could things be made simpler? Attached
 are modwin.d and appwin.d.

 D:\temp\dlang5>dmd appwin.d modwin.d

 
 Oops. I didn't notice that the second file was not included.
 
 Anyway, even if you include the file, the definition of WinMain will
 not be found because of mangling. I attached the code that uses a
 function pointer (i called it delegate mistakingly). 

I don't use Windows, so I can't test your code, but I think it should work. Why 
don't you try going from the beginning? Just a simple module with a WinMain,
see 
if it works. Then try to use the function pointer from within the same module, 
see if it works. And then split it. Good luck.

-- 
Carlos Santander Bernal

Oct 23 2006

AF <noemail noemail.com> writes:

Thanks, but I think simpler than that is almost impossible: all I
did was to cut & paste...

Oct 23 2006

BCS <BCS pathlink.com> writes:

Max Samuha wrote:
 
 Anyway, even if you include the file, the definition of WinMain will
 not be found because of mangling. I attached the code that uses a
 function pointer (i called it delegate mistakingly). 

you might try:

extern(C) WinMain

But that's just a wild guess

Oct 23 2006

Max Samuha <maxter i.com.ua> writes:

begin 644 appwin.d
M:6UP;W)T(&UO9'=I;CL-"FEM<&]R="!S=&0N8RYW:6YD;W=S+G=I;F1O=W,[

M"GT-" T*:6YT(&UY5VEN36%I;BA(24Y35$%.0T4 :$EN<W1A;F-E+$A)3E-4


M<V%G92!T:71L92(L34)?3TLI.PT*("` ("\J("XN+B!I;G-E<G0 =7-E<B!C

`
end

begin 644 modwin.d
M;6]D=6QE(&UO9'=I;CL-" T*<')I=F%T92!I;7!O<G0 <W1D+F,N=VEN9&]W


M:70H*3L-"F5X=&5R;B`H0RD =F]I9"!?;6]D=6QE0W1O<B I.PT*97AT97)N


M;G-T86YC92P 2$E.4U1!3D-%(&A0<F5V26YS=&%N8V4L($Q04U12(&QP0VUD










M;6]D=6QE1'1O<B I.PD)+R\ 8V%L;"!M;V1U;&4 9&5S=')U8W1O<G,-" D 






`
end

Oct 23 2006

AF <noemail noemail.com> writes:

Thanks for the code. I also implemented a simple win app using the
main() function (see below file swapp.d).
 While I preffer this simpler form, what I need to know if I will miss
some functionality specific to the WinMain paradigm. File compilation
uses the -L/exet:nt/su:windows:4.0 parameter.

Thanks in advance.

 AF

-------------file swapp.d-------
import std.c.windows.windows;

HINSTANCE hInstance;

int main(char[][] args) {
	hInstance = GetModuleHandleA(null); //obtain the hInstance
parameter
	MessageBoxA(null,"Message text","Message title",MB_OK);
	return 0;
}

-------------end file swapp.d-----------

Oct 24 2006

Max Samuha <maxter i.com.ua> writes:

On Tue, 24 Oct 2006 19:00:55 +0000 (UTC), AF <noemail noemail.com>
wrote:

Thanks for the code. I also implemented a simple win app using the
main() function (see below file swapp.d).
 While I preffer this simpler form, what I need to know if I will miss
some functionality specific to the WinMain paradigm. File compilation
uses the -L/exet:nt/su:windows:4.0 parameter.

Thanks in advance.

 AF

-------------file swapp.d-------
import std.c.windows.windows;

HINSTANCE hInstance;

int main(char[][] args) {
	hInstance = GetModuleHandleA(null); //obtain the hInstance
parameter
	MessageBoxA(null,"Message text","Message title",MB_OK);
	return 0;
}

-------------end file swapp.d-----------

Do you know how to access nCmdShow param? User may set the initial
state of the app's window (maximized, etc.) in a shortcut to your app
and you'd better handle this properly.

there is also a rather hackish way to use WinMain without the function
pointer:

modwin.d:

extern(Windows) int winMain(HINSTANCE hInstance, HINSTANCE
hPrevInstance, LPSTR lpCmdLine, int nCmdShow);
// or you could try extern(C) to hack the D mangling :))

extern(Windows) export int WinMain(HINSTANCE hInstance, HINSTANCE
hPrevInstance, LPSTR lpCmdLine,int nCmdShow)
{
	...
	result = winMain(hInstance, hPrevInstance,
lpCmdLine,nCmdShow);	
}


appwin.d:

import modwin.d

extern(Windows) int winMain(HINSTANCE hInstance, HINSTANCE
hPrevInstance, LPSTR lpCmdLine, int nCmdShow)
{
...
}

Well, that's insane...

BTW, why methods with external linkage defined in mixins use D
mangling? Is it a bug or feature?

Oct 24 2006

AF <noemail noemail.com> writes:

 No, I don't know how to access the nCmdShow parameter.
 Is there any possibility?

 On the other hand, about linkage and magling, I simply do not know.

 Thanks for the new code, I will give it a try.

Oct 24 2006

Max Samuha <maxter i.com.ua> writes:

On Wed, 25 Oct 2006 05:50:01 +0000 (UTC), AF <noemail noemail.com>
wrote:

 No, I don't know how to access the nCmdShow parameter.
 Is there any possibility?

 On the other hand, about linkage and magling, I simply do not know.

 Thanks for the new code, I will give it a try.

Sorry, I failed to figure out how to access nCmdShow from main().
Maybe somebody else could help? I'm sure Walter knows the answer.

Oct 26 2006

Serg Kovrov <kovrov no.spam> writes:

Max Samuha wrote:
 On Wed, 25 Oct 2006 05:50:01 +0000 (UTC), AF <noemail noemail.com>
 wrote:
 Sorry, I failed to figure out how to access nCmdShow from main().
 Maybe somebody else could help? I'm sure Walter knows the answer.   

You could use Windows API GetStartupInfo() 
(http://windowssdk.msdn.microsoft.com/library/ms683230)
I believe STARTUPINFO.wShowWindow is what you need.

-- 
serg.

Nov 04 2006

AF <noemail noemail.com> writes:

Thanks. I will do some further reading on that API.

I wanted also to know if the main() version loses some functionality
at the gc level, comparatively with the WinMain() Walter-provided
boilerplate, but I hope the question is not critical.

Thanks again.

AF

Nov 05 2006

D Programming

C/C++ Programming

Other

digitalmars.D.learn - What is wrong with this boilerplate mixin?