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
(9) |
2
(5) |
3
(7) |
4
(1) |
|
5
(1) |
6
(4) |
7
(8) |
8
(7) |
9
(10) |
10
(1) |
11
(7) |
|
12
(6) |
13
(6) |
14
(2) |
15
(8) |
16
(3) |
17
(2) |
18
(6) |
|
19
(6) |
20
|
21
(14) |
22
(5) |
23
|
24
(5) |
25
(5) |
|
26
(3) |
27
(12) |
28
(4) |
29
(4) |
30
(7) |
|
|
|
From: Michal M. <mi...@mo...> - 2004-09-07 23:34:58
|
OROSZI Balázs wrote: > Hello again! > > I've read another VERY interesting post from that guy, who originally > wrote about DirectX-MinGW license problems. Now he writes about GNU C++ > library problems. He sais, that the GNU C++ library is distributed under > the GPL, and as such, derived works can only be distributed under the > GPL. So this means, that whoever wants to write commercial programs with > the GNU C++ compiler using it's C++ library MUST open it's source code? > And this would also mean, that whoever wants to write programs for Linux > (in C++ using G++), must open the source code? > > Any comments on this? If you mean libstdc++ than I don't understand why you haven't look at the official documentation: http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/license.html it's absolutely clearly explained there Regards, Michal |
|
From: Scott S. <age...@co...> - 2004-09-07 22:07:14
|
Works using the GNU C++ Compile do not have to be released under the GNU GPL. Only derived works of your program must be derived from the GNU GPL. You are free to use other licenses instead. OROSZI Balázs wrote: > Hello again! > > I've read another VERY interesting post from that guy, who originally > wrote about DirectX-MinGW license problems. Now he writes about GNU > C++ library problems. He sais, that the GNU C++ library is distributed > under the GPL, and as such, derived works can only be distributed > under the GPL. So this means, that whoever wants to write commercial > programs with the GNU C++ compiler using it's C++ library MUST open > it's source code? > And this would also mean, that whoever wants to write programs for > Linux (in C++ using G++), must open the source code? > > Any comments on this? > > -- > Greetings, > Balázs > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_idP47&alloc_id808&op=click > _______________________________________________ > Dev-cpp-users mailing list > Dev...@li... > TO UNSUBSCRIBE: http://www23.brinkster.com/noicys/devcpp/ub.htm > https://lists.sourceforge.net/lists/listinfo/dev-cpp-users > -- --Scott Simontis-- |
|
From: Per W. <pw...@ia...> - 2004-09-07 21:36:01
|
Notice the _very_ big difference between GPL and LGPL. The library is using the LGBL (formerly known as Library GPL, now Lesser GPL). So, there isn't a problem with the GNU library. LGPL doesn't have the "black-hole" properties of the GPL licence, dragging everything into GPL licences. /Per W On Tue, 7 Sep 2004, [ISO-8859-2] OROSZI Bal=E1zs wrote: > Hello again! > > I've read another VERY interesting post from that guy, who originally wro= te about > DirectX-MinGW license problems. Now he writes about GNU C++ library probl= ems. He sais, > that the GNU C++ library is distributed under the GPL, and as such, deriv= ed works can only > be distributed under the GPL. So this means, that whoever wants to write = commercial > programs with the GNU C++ compiler using it's C++ library MUST open it's = source code? > And this would also mean, that whoever wants to write programs |
|
From: <or...@vp...> - 2004-09-07 20:05:03
|
Hello again! I've read another VERY interesting post from that guy, who originally wro= te about=20 DirectX-MinGW license problems. Now he writes about GNU C++ library probl= ems. He sais,=20 that the GNU C++ library is distributed under the GPL, and as such, deriv= ed works can only=20 be distributed under the GPL. So this means, that whoever wants to write = commercial=20 programs with the GNU C++ compiler using it's C++ library MUST open it's = source code? And this would also mean, that whoever wants to write programs for Linux = (in C++ using=20 G++), must open the source code? Any comments on this? -- Greetings, Bal=E1zs |
|
From: Mike C. <mi...@si...> - 2004-09-07 17:00:12
|
Dear all, I am conducting a survey on open source for my university coursework and would like to have your support and participation in the questionnaire. The URL for the questionnaire is http://web.singnet.com.sg/~mikecck/opensource/WebFormA1.htm Thank you very much. Mike Chan |
|
From: Per W. <pw...@ia...> - 2004-09-07 06:27:47
|
Some versions of Dev-C++ have had a bit of problem to parse the constantly
varying error messages emitted by the MinGW compiler. This has resulted in
a bit strange errors in the 'Compiler' tab. If switching to the 'Compiler
Log' tab, you should have the full messages.
Too bad that different versions of MinGW gives different error messages :(
The problem parsing the error messages - and also the impossibility of the
Dev-C++ project to keep a list of all gcc error messages can be clearly
seen from the following tests runs with a couple of versions of the MinGW
compiler - all of them separately installed, i.e. not from a Dev-C++
installation package.
gcc 2.95.3-6 gives:
fnkptr.cpp: In function `int main()':
fnkptr.cpp:29: assuming & on `Dog::Speak'
fnkptr.cpp:29: assuming & on `Dog::Move'
fnkptr.cpp:29: assuming & on `Dog::Eat'
fnkptr.cpp:29: assuming & on `Dog::Growl'
fnkptr.cpp:29: assuming & on `Dog::Whimper'
fnkptr.cpp:29: assuming & on `Dog::RollOver'
fnkptr.cpp:29: assuming & on `Dog::PlayDead'
fnkptr.cpp:29: Internal compiler error in `const_hash', at varasm.c:2373
gcc 3.2 (mingw special 20020817-1) gives:
fnkptr.cpp: In function `int main()':
fnkptr.cpp:29: assuming pointer to member `void Dog::Speak() const'
fnkptr.cpp:29: (a pointer to member can only be formed with `&Dog::Speak()
const')
gcc 3.3.3 (mingw special) gives:
fnkptr.cpp: In function `int main()':
fnkptr.cpp:29: error: assuming pointer to member `void Dog::Speak() const'
fnkptr.cpp:29: error: (a pointer to member can only be formed with
`&Dog::Speak
')
gcc 3.4.1 (mingw special) gives:
fnkptr.cpp: In function `int main()':
fnkptr.cpp:22: error: invalid use of non-static member function `void
Dog::Speak() const'
fnkptr.cpp:23: error: invalid use of non-static member function `void
Dog::Move() const'
fnkptr.cpp:24: error: invalid use of non-static member function `void
Dog::Eat() const'
fnkptr.cpp:25: error: invalid use of non-static member function `void
Dog::Growl() const'
fnkptr.cpp:26: error: invalid use of non-static member function `void
Dog::Whimper() const'
fnkptr.cpp:27: error: invalid use of non-static member function `void
Dog::RollOver() const'
fnkptr.cpp:29: error: invalid use of non-static member function `void
Dog::PlayDead() const'
fnkptr.cpp:29: error: invalid use of non-static member function
As can be seen from the above, gcc 3.4.1 is the least helpful, since it is
the only one not suggesting a & before the function names...
/Per W
On Mon, 6 Sep 2004, Roger Furer wrote:
> Aloha from Honolulu,
> Thank You Per, once again you have made my life easier and increased
> my knowledge. Still, I have this question: How did you know what the
> complete error message said? All that comes up in my compiler messages
> is "assuming" on the first line and "(a" on the 2nd. Yes that is an
> open parentesis and a lower case a; and nothing else. I tried copying
> the line and pasting it into a Notebook file and got the same result.
> Where does one find these answers?
> Thanks Again,
> Roger
>
> Per Westermark wrote:
>
> >1) The complete error messages are:
> >fnkptr.cpp:29: error: assuming pointer to member `void Dog::Speak() const'
> >fnkptr.cpp:29: error: (a pointer to member can only be formed with `&Dog::Speak() const')
> >
> >Just add a & before eacn function name, just as the error message suggest,
> >and the compiler will be happy.
> >
> >2) Notice that Dev-C++ is an integrated development environment, not a
> >compiler. It is the gcc team - or possibly the MinGW team - that is
> >responsible for which error messages are emitted by the compiler. By the
> >way, 99.9% if the error messages I have seen have been quite obvious.
> >
> >3) windef.h is a file seldom directly included in a program. However, a
> >number of other include files recursively requests the windef.h file. If
> >you check again, you should be able to find out why the compiler mentioned
> >it. The compiler never makes this kind of mistake. The only reason it said
> >BOOL was already defined in windef.h was that the program directly or
> >indirectly did include windef.h
> >
> >/Per W
> >
> >On Sun, 5 Sep 2004, Roger Furer wrote:
> >
> >
> >
> >>Aloha from Honolulu,
> >> The following was taken from Sams Teach Yourself C++ and refuses to
> >>compile. The compiler reports the error at the line following
> >>"Dog::PlayDead" which is the closing brace and semi-colon for the "PDF
> >>DogFunctions...". I have marked it with an exclamation point ! here.
> >>While I do need to know what the code's problem is, more vexing is that
> >>in the compiler report window under messages is listed "assuming" and on
> >>the next line "(a". Nowhere have I been able to find a list of the
> >>various messages. I looked under the Help window of the program
> >>(Version 4.9.8.0) and also on the Bloodshed site, but no luck there
> >>either. I would suggest that a comprehensive list of error messages
> >>would benefit most everyone using these programs.
> >> A further note: earlier in the lesson was a line: enum BOOL {FALSE,
> >>TRUE}; that generated the folowing error messages: "conflicting" and
> >>then: (copied from the compiler report window)
> >>227 C:\Dev-Cpp\include\windef.h previous declaration as `typedef
> >>WINBOOL BOOL'
> >> My solution was to comment it out, but why did the message appear
> >>when windef.h was never included in the code?
> >>Thanks in advance,
> >>Mahalo,
> >>Roger
> >>
> >>
> >>//Listing 20.10 Array of pointers to member functions
> >>#include <iostream>
> >>class Dog
> >>{
> >> public:
> >> void Speak()const { std::cout << "Woof!\n"; }
> >> void Move() const { std::cout << "Walking to heel...\n"; }
> >> void Eat() const { std::cout << "Gobbling food...\n"; }
> >> void Growl() const { std::cout << "Grrrrr\n"; }
> >> void Whimper() const { std::cout << "Whining noises...\n"; }
> >> void RollOver() const { std::cout << "Rolling over...\n"; }
> >> void PlayDead() const
> >> { std::cout << "Is this the end of Little Caeser?\n"; }
> >>};
> >>
> >>typedef void (Dog::*PDF)()const ;
> >>
> >>int main()
> >>{
> >> const int MaxFuncs = 7;
> >> PDF DogFunctions[MaxFuncs] =
> >> { Dog::Speak,
> >> Dog::Move,
> >> Dog::Eat,
> >> Dog::Growl,
> >> Dog::Whimper,
> >> Dog::RollOver,
> >> Dog::PlayDead
> >>! };
> >> Dog* pDog =0;
> >> int Method;
> >> bool fQuit = false;
> >> while (!fQuit)
> >> {
> >> std::cout << "(0)Quit (1)Speak (2)Move (3)Eat (4)Growl";
> >> std::cout << " (5)Whimper (6)Roll Over (7)Play Dead: ";
> >> std::cin >> Method;
> >> if (Method == 0)
> >> {
> >> fQuit = true;
> >> break;
> >> }
> >> else
> >> {
> >> pDog = new Dog;
> >> (pDog->*DogFunctions[Method-1])();
> >> delete pDog;
> >> }
> >> }
> >> return 0;
> >>}
> >>
> >>
> >>
> >>-------------------------------------------------------
> >>This SF.Net email is sponsored by BEA Weblogic Workshop
> >>FREE Java Enterprise J2EE developer tools!
> >>Get your free copy of BEA WebLogic Workshop 8.1 today.
> >>http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> >>_______________________________________________
> >>Dev-cpp-users mailing list
> >>Dev...@li...
> >>TO UNSUBSCRIBE: http://www23.brinkster.com/noicys/devcpp/ub.htm
> >>https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
> >>
> >>
> >>
> >
> >
> >
> >
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> TO UNSUBSCRIBE: http://www23.brinkster.com/noicys/devcpp/ub.htm
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
>
|
|
From: Roger F. <ra...@ha...> - 2004-09-07 06:21:00
|
Aloha from Honolulu, Uh Oh, and ooops! Never mind my last reply. I found my own answer. For anyone else wondering the same thing (if there is anyone else), the complete compiler message is printed in the Compile Log. Why it isn't also in the message window is something the only developers know. Thanks for your attention. Mahalo, Roger |
|
From: Roger F. <ra...@ha...> - 2004-09-07 00:22:16
|
Aloha from Honolulu,
Thank You Per, once again you have made my life easier and increased
my knowledge. Still, I have this question: How did you know what the
complete error message said? All that comes up in my compiler messages
is "assuming" on the first line and "(a" on the 2nd. Yes that is an
open parentesis and a lower case a; and nothing else. I tried copying
the line and pasting it into a Notebook file and got the same result.
Where does one find these answers?
Thanks Again,
Roger
Per Westermark wrote:
>1) The complete error messages are:
>fnkptr.cpp:29: error: assuming pointer to member `void Dog::Speak() const'
>fnkptr.cpp:29: error: (a pointer to member can only be formed with `&Dog::Speak() const')
>
>Just add a & before eacn function name, just as the error message suggest,
>and the compiler will be happy.
>
>2) Notice that Dev-C++ is an integrated development environment, not a
>compiler. It is the gcc team - or possibly the MinGW team - that is
>responsible for which error messages are emitted by the compiler. By the
>way, 99.9% if the error messages I have seen have been quite obvious.
>
>3) windef.h is a file seldom directly included in a program. However, a
>number of other include files recursively requests the windef.h file. If
>you check again, you should be able to find out why the compiler mentioned
>it. The compiler never makes this kind of mistake. The only reason it said
>BOOL was already defined in windef.h was that the program directly or
>indirectly did include windef.h
>
>/Per W
>
>On Sun, 5 Sep 2004, Roger Furer wrote:
>
>
>
>>Aloha from Honolulu,
>> The following was taken from Sams Teach Yourself C++ and refuses to
>>compile. The compiler reports the error at the line following
>>"Dog::PlayDead" which is the closing brace and semi-colon for the "PDF
>>DogFunctions...". I have marked it with an exclamation point ! here.
>>While I do need to know what the code's problem is, more vexing is that
>>in the compiler report window under messages is listed "assuming" and on
>>the next line "(a". Nowhere have I been able to find a list of the
>>various messages. I looked under the Help window of the program
>>(Version 4.9.8.0) and also on the Bloodshed site, but no luck there
>>either. I would suggest that a comprehensive list of error messages
>>would benefit most everyone using these programs.
>> A further note: earlier in the lesson was a line: enum BOOL {FALSE,
>>TRUE}; that generated the folowing error messages: "conflicting" and
>>then: (copied from the compiler report window)
>>227 C:\Dev-Cpp\include\windef.h previous declaration as `typedef
>>WINBOOL BOOL'
>> My solution was to comment it out, but why did the message appear
>>when windef.h was never included in the code?
>>Thanks in advance,
>>Mahalo,
>>Roger
>>
>>
>>//Listing 20.10 Array of pointers to member functions
>>#include <iostream>
>>class Dog
>>{
>> public:
>> void Speak()const { std::cout << "Woof!\n"; }
>> void Move() const { std::cout << "Walking to heel...\n"; }
>> void Eat() const { std::cout << "Gobbling food...\n"; }
>> void Growl() const { std::cout << "Grrrrr\n"; }
>> void Whimper() const { std::cout << "Whining noises...\n"; }
>> void RollOver() const { std::cout << "Rolling over...\n"; }
>> void PlayDead() const
>> { std::cout << "Is this the end of Little Caeser?\n"; }
>>};
>>
>>typedef void (Dog::*PDF)()const ;
>>
>>int main()
>>{
>> const int MaxFuncs = 7;
>> PDF DogFunctions[MaxFuncs] =
>> { Dog::Speak,
>> Dog::Move,
>> Dog::Eat,
>> Dog::Growl,
>> Dog::Whimper,
>> Dog::RollOver,
>> Dog::PlayDead
>>! };
>> Dog* pDog =0;
>> int Method;
>> bool fQuit = false;
>> while (!fQuit)
>> {
>> std::cout << "(0)Quit (1)Speak (2)Move (3)Eat (4)Growl";
>> std::cout << " (5)Whimper (6)Roll Over (7)Play Dead: ";
>> std::cin >> Method;
>> if (Method == 0)
>> {
>> fQuit = true;
>> break;
>> }
>> else
>> {
>> pDog = new Dog;
>> (pDog->*DogFunctions[Method-1])();
>> delete pDog;
>> }
>> }
>> return 0;
>>}
>>
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by BEA Weblogic Workshop
>>FREE Java Enterprise J2EE developer tools!
>>Get your free copy of BEA WebLogic Workshop 8.1 today.
>>http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
>>_______________________________________________
>>Dev-cpp-users mailing list
>>Dev...@li...
>>TO UNSUBSCRIBE: http://www23.brinkster.com/noicys/devcpp/ub.htm
>>https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
>>
>>
>>
>
>
>
>
|