dev-cpp-users Mailing List for Dev-C++
Open Source C & C++ IDE for Windows
Brought to you by:
claplace
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(15) |
Oct
(115) |
Nov
(154) |
Dec
(258) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(377) |
Feb
(260) |
Mar
(249) |
Apr
(188) |
May
(152) |
Jun
(150) |
Jul
(195) |
Aug
(202) |
Sep
(200) |
Oct
(286) |
Nov
(242) |
Dec
(165) |
| 2002 |
Jan
(245) |
Feb
(241) |
Mar
(239) |
Apr
(346) |
May
(406) |
Jun
(369) |
Jul
(418) |
Aug
(357) |
Sep
(362) |
Oct
(597) |
Nov
(455) |
Dec
(344) |
| 2003 |
Jan
(446) |
Feb
(397) |
Mar
(515) |
Apr
(524) |
May
(377) |
Jun
(387) |
Jul
(532) |
Aug
(364) |
Sep
(294) |
Oct
(352) |
Nov
(295) |
Dec
(327) |
| 2004 |
Jan
(416) |
Feb
(318) |
Mar
(324) |
Apr
(249) |
May
(259) |
Jun
(218) |
Jul
(212) |
Aug
(259) |
Sep
(158) |
Oct
(162) |
Nov
(214) |
Dec
(169) |
| 2005 |
Jan
(111) |
Feb
(165) |
Mar
(199) |
Apr
(147) |
May
(131) |
Jun
(163) |
Jul
(235) |
Aug
(136) |
Sep
(84) |
Oct
(88) |
Nov
(113) |
Dec
(100) |
| 2006 |
Jan
(85) |
Feb
(119) |
Mar
(33) |
Apr
(31) |
May
(56) |
Jun
(68) |
Jul
(18) |
Aug
(62) |
Sep
(33) |
Oct
(55) |
Nov
(19) |
Dec
(40) |
| 2007 |
Jan
(22) |
Feb
(49) |
Mar
(34) |
Apr
(51) |
May
(66) |
Jun
(43) |
Jul
(116) |
Aug
(57) |
Sep
(70) |
Oct
(69) |
Nov
(97) |
Dec
(86) |
| 2008 |
Jan
(32) |
Feb
(47) |
Mar
(106) |
Apr
(67) |
May
(28) |
Jun
(39) |
Jul
(31) |
Aug
(25) |
Sep
(18) |
Oct
(25) |
Nov
(5) |
Dec
(21) |
| 2009 |
Jan
(33) |
Feb
(27) |
Mar
(27) |
Apr
(22) |
May
(22) |
Jun
(10) |
Jul
(17) |
Aug
(9) |
Sep
(21) |
Oct
(13) |
Nov
(4) |
Dec
(11) |
| 2010 |
Jan
(10) |
Feb
(8) |
Mar
(4) |
Apr
(1) |
May
|
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(8) |
Oct
(26) |
Nov
(9) |
Dec
(1) |
| 2011 |
Jan
(21) |
Feb
(16) |
Mar
(4) |
Apr
(19) |
May
(26) |
Jun
(9) |
Jul
(6) |
Aug
|
Sep
(4) |
Oct
(3) |
Nov
(2) |
Dec
(1) |
| 2012 |
Jan
(4) |
Feb
(7) |
Mar
(4) |
Apr
|
May
(1) |
Jun
(10) |
Jul
(1) |
Aug
(1) |
Sep
(18) |
Oct
(3) |
Nov
(1) |
Dec
(1) |
| 2013 |
Jan
(4) |
Feb
(2) |
Mar
(15) |
Apr
(6) |
May
(1) |
Jun
(3) |
Jul
(1) |
Aug
(2) |
Sep
(4) |
Oct
|
Nov
(9) |
Dec
|
| 2014 |
Jan
(4) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
(4) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(4) |
| 2015 |
Jan
(2) |
Feb
(3) |
Mar
(1) |
Apr
(2) |
May
(1) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(2) |
Oct
(9) |
Nov
(35) |
Dec
(6) |
| 2016 |
Jan
(7) |
Feb
(10) |
Mar
(10) |
Apr
(9) |
May
(13) |
Jun
(9) |
Jul
(1) |
Aug
(3) |
Sep
(3) |
Oct
(1) |
Nov
(1) |
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
(1) |
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
1
(13) |
2
(19) |
3
(28) |
4
(10) |
|
5
(2) |
6
(6) |
7
(9) |
8
(16) |
9
(14) |
10
(11) |
11
(7) |
|
12
(2) |
13
(9) |
14
(12) |
15
(6) |
16
(12) |
17
(12) |
18
(4) |
|
19
(8) |
20
(3) |
21
(3) |
22
(4) |
23
(8) |
24
(17) |
25
(16) |
|
26
(14) |
27
(10) |
28
(29) |
29
(28) |
30
(5) |
31
(15) |
|
|
From: Per W. <pw...@ia...> - 2003-10-13 21:38:03
|
One note. Since globally declared static variables are only accessible in a single compilation unit, they are normally not declared in any include file. If they are declared in an include file, every C or C++ file that included the file would get it's own copy of a static variable. /Per W On Sun, 12 Oct 2003, xRxIxPx wrote: > In general, you should only have const, static and extern variable > declarations in your header files, and in ONE .cpp file the definition for > your extern variables. > |
|
From: xRxIxPx <xr...@gm...> - 2003-10-13 21:19:56
|
At 08:15 AM 10/12/2003 -0400, Matthews wrote: >Guard statements are lines like these in your header files: > >#ifndef FOOHEADER_H >#define FOOHEADER_H > >int foo; >char *foostring; >//... That should not happen! If you include this header in two different compile units (means .cpp files), your global objects will be defined in 2 object files making the linker bailing out errornously. In general, you should only have const, static and extern variable declarations in your header files, and in ONE .cpp file the definition for your extern variables. >#endif > >Then if two files include foo.h, it won't be recompiled because FOOHEADER_H >has already been defined. Only true for one compile unit. Better have: #ifndef FOOHEADER_H #define FOOHEADER_H extern int foo; extern char *foostring; //... #endif foo1.cpp #include "fooheader.h" foo2.cpp #include "fooheader1.h" int foo=631; char* foostring=0; Cheers. |
|
From: sgifan67 <sgi...@fr...> - 2003-10-13 20:50:24
|
Hello all, Does anyone have compiled a libsigC++ 1.0.x package for DevCpp (a devpak) or has makefile adapted to DevCpp, it is a bit a hell to compile from the standard tazr.gz archive Thanks in advance |
|
From: <ten...@ne...> - 2003-10-13 18:08:14
|
|
From: Paul I. <pi...@ot...> - 2003-10-13 17:23:34
|
Matthews <dem...@uw...> wrote: > Guard statements are lines like these in your header files: >=20 > #ifndef FOOHEADER_H > #define FOOHEADER_H >=20 > int foo; > char *foostring; > //... >=20 > #endif >=20 > Then if two files include foo.h, it won't be recompiled because FOOHEAD= ER_H > has already been defined. I think this answer is confusing to all the newbees out there... First point: Of course the header file will be compiled-in with each .cpp/.c that incl= udes=20 it. If you check the makefile, each .cpp is compiled by it self and there= is=20 no way for the compiler to know if the header has already been included a= nd=20 thus compiled... Second point: The guard statements mentioned prevent the same header from being include= d=20 more than once during the compilation of _one_ .cpp=B4. Consider the foll= owing: file1.h #include "file2.h" .... file2.h #include "file1.h" ... Without the guard stetements file1.h would include file2.h whitch include= s=20 file1.h...=20 Third point: The example .h-file above contains definitions of variables. If you inclu= de=20 this file the variables foo and foostring would be instanciated as local = (file- scope) in each .cpp where the .h is included. Not very useful?! To make g= lobal=20 variables declare as _external_ in header fil and move the instansiation = to=20 the .cpp file. Regards, Paul. |
|
From: Kevin W. <ke...@me...> - 2003-10-13 09:38:17
|
Chris Sroka wrote: >I want to draw a bitmap (from a file on disk) into a part of the dialog >box. I have trawled the msdn.microsoft.com pages and haven't found a way >to do this successfully. > >Any suggestions? > >Thanks >Chris S Normally, you would draw a bitmap in response to the WM_PAINT or WM_ERASEBKGND messages, which pass a handle to the Device Context of the window (HDC). Use the DC functions to draw the bitmap (BitBlt, etc.) . If you don't have it already, download the Windows Developers' Reference (SDK help) from Microsoft. It is essential for Windows programming. Kev. |
|
From: Hossein H. <ult...@em...> - 2003-10-13 09:10:18
|
> I found DEV to be excellent for learning C++, but if you then move to visual > studio and microsoft's version of C++ (I am exaggerating) then it can be a > little confusing with templates. Not so much with MSVC7.1. So far, there hasn't been found so much problems in it (including in the templates issues). But, under any circumstances, I don't recommend using any of M$ products. > But do not worry, you will not go wrong. And post your questions to the > mailing list - I need to get better at C++ also!!! (too much cross-language > work!). So do I (after neerly a decade of C++ programming). Regards, --Hossein -- __________________________________________________________ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup CareerBuilder.com has over 400,000 jobs. Be smarter about your job search http://corp.mail.com/careers |
|
From: Chris S. <CS...@Ai...> - 2003-10-13 05:41:18
|
I have a dialog box defined manually in a resource script file:=20
............
ID_DIALOG_2 DIALOG 0, 0, 250, 90
STYLE WS_VISIBLE | WS_SYSMENU | WS_MINIMIZEBOX | WS_MAXIMIZEBOX | =
WS_POPUP | WS_CAPTION | DS_MODALFRAME
CAPTION "About"
FONT 8,"Helv"
BEGIN
DEFPUSHBUTTON "OK",ID_OK,180,10,50,14,WS_GROUP
END
.............
I want to draw a bitmap (from a file on disk) into a part of the dialog =
box. I have trawled the msdn.microsoft.com pages and haven't found a way =
to do this successfully.=20
Any suggestions?=20
Thanks=20
Chris S
|
|
From: <meh...@tu...> - 2003-10-13 00:55:25
|
*********************************************************************** Bu elektronik posta ve onunla iletilen b=FCt=FCn dosyalar sadece = g=F6ndericisi taraf=FDndan almas=FD ama=E7lanan yetkili ger=E7ek ya da = t=FCzel ki=FEinin kullan=FDm=FD i=E7indir.E=F0er s=F6z konusu yetkili = al=FDc=FD de=F0ilseniz bu elektronik postan=FDn i=E7eri=F0ini = a=E7=FDklaman=FDz,kopyalaman=FDz, y=F6nlendirmeniz ve kullanman=FDz = kesinlikle yasakt=FDr ve bu elektronik postay=FD derhal silmeniz = gerekmektedir TURKCELL bu mesaj=FDn i=E7erdi=F0i bilgilerin do=F0rulu=F0u veya = eksiksiz oldu=F0u konusunda herhangi bir garanti vermemektedir. Bu = nedenle bu bilgilerin ne =FEekilde olursa olsun i=E7eri=F0inden, = iletilmesinden, al=FDnmas=FDndan ve saklanmas=FDndan sorumlu de=F0ildir. = Bu mesajdaki g=F6r=FC=FEler yaln=FDzca g=F6nderen ki=FEiye aittir ve = TURKCELL'in g=F6r=FC=FElerini yans=FDtmayabilir Bu e-posta bilinen b=FCt=FCn bilgisayar vir=FCslerine kar=FE=FD = taranm=FD=FEt=FDr. *********************************************************************** This e-mail and any files transmitted with it are confidential and = intended solely for the use of the individual or entity to whom they are = addressed. If you are not the intended recipient you are hereby notified = that any dissemination, forwarding, copying or use of any of the = information is strictly prohibited, and the e-mail should immediately be = deleted. TURKCELL makes no warranty as to the accuracy or completeness of any = information contained in this message and hereby excludes any liability = of any kind for the information contained therein or for the information = transmission, reception, storage or use of such in any way = whatsoever.The opinions expressed in this message belong to sender alone = and may not necessarily reflect the opinions of TURKCELL. This e-mail has been scanned for all known computer viruses. *********************************************************************** |