dev-cpp-users Mailing List for Dev-C++

One more time, I find the absurd error of invalid window handle when it 
has no sense, when using a function that works for determine the file 
name for the file which will be used and adding a MessageBox in some 
points with hwnd or NULL as HWND.

And once more it makes me mad the GetLastError() or how you win the 
Heaven or know what the hell shall be. So it makes me so bad mood I will 
reflect it in the message, with your permission, just as a vengeance for 
it against the keyboard. In fact, this criminal function deserves a very 
harder treatment, only that function makes programming very frustrating 
when it comes to need its output.

GetLastError is supposed to catch the error code as it is generated when 
certain functions work. So, eg, GetDIBits finds that the pointer is not 
big enough. So you getlasterror and it says, "hey, you had no space there!".
But since I started programming I've found invariably this: when some 
function generates an error and doesn't work, windows closes it before 
GetLastError has a chance to do something and pass the result to a 
message box. So, if when something fails, it lets no chance to 
GetLastError, what in the hell is it intended for????
How shall it be used? Shall I build a time machine, so it travels 
backwards in time, to came back and say "Heeeeeeyyyyy diuúd, Ai travleed 
through space and time, bate I got so sead that to hour that I must go 
to sleep the female monkey"?????.
It has only worked twice, once saying that there was no memory to 
SetDIBits, but the bitmap was there as it should be in case it worked, 
and another time it said the file couldn't be created, but the file was 
created and written.
So I alone it's male pear, these uncles make something packasgo works.

Mauricio Krisna (Merry Christmas)

P.S.- The ununderstandeable things are, as you can see, not needed for 
the message. Those are witticisms (I think my dictionary is not right in 
this translation) in letting the steam off. Witticisms for spanish speakers.

Hum, I think when you asked that, and said the exclamation next, it 
sounds like you're saying that guy that he's a dumb guy and he should 
learn again, not that you say you feel like needing to re-read some 
books. And he got offended. Indeed, your phrase sounds a little hard to 
my ears.
However, his answer is still too hard, I think.

María Cristina Ma. Er, no, Merry Christmas.

Maya wrote:

> I apologize if you felt offended. Perhaps you are a much better 
> programmer than I am, at least that is what you presume; as you said, 
> you have the programming knowledge and experience that most people in 
> this mail list would only dream of having. If only a little bit of 
> good manners and a better knowledge of the English language would 
> accompany your "outstanding" knowledge of C++ programming,  I am sure 
> you would be a much, much better person.
> To the other members here I say, pd...@xs... does not by any means 
> represent the good nature and/or mature behaviour we adhere to here. 
> I, as most serious programmers in here, will block any farther 
> communication with this individual.
> Best regards, and have a Merry Christmas.
>
> pd...@xs... wrote:
>
>> Don't get cocky you little shit, you're the one having problems, not 
>> me. I
>> have more programming knowledge and experience than you could ever 
>> hope to
>> acquire, so you'd better just shut up.
>> I tried giving you friendly advice, you spit it in my face, so now 
>> you can
>> just fuck off and die for all I care, asshole.
>>
>>
>> -----Original Message-----
>> From: Maya [mailto:Esc...@ne...] Sent: Thursday, 
>> December 18, 2003 9:34 PM
>> To: pd...@xs...; gtk...@gn...; C/C++ Programmers; Dev - C++; 
>> Gtk+
>> mailing list
>> Subject: Re: [Dev-C++] Demystifying namespace
>>
>> I want to replace the word __func__ with the word file, and you are 
>> telling me to assign the value of __func__ to the std::string variable?
>>
>> Gotta check those books again, eh!
>>
>> pd...@xs... wrote:
>>
>>  
>>
>>> You shouldn't use #defines. #defines are cross-everything, they 
>>> don't care
>>> about scope, namespaces, functions, whatever. It's just a simple global
>>> search&replace operation performed by the preprocessor. If you want 
>>> your
>>> namespace code to work, change it to something like:
>>>
>>> namespace foo{
>>>   const std::string file = __func__;
>>>   const size_t      line = __LINE__;
>>> }
>>> Note that I didn't test this though, but it should work (and didn't you
>>>   
>>
>> mean
>>  
>>
>>> __FILE__ instead of __func__ there?)
>>>
>>> Regards,
>>>
>>>
>>> Paul
>>>
>>> -----Original Message-----
>>> From: dev...@li...
>>> [mailto:dev...@li...] On Behalf Of Maya
>>> Sent: Thursday, December 18, 2003 7:49 AM
>>> To: C/C++ Programmers; Dev - C++
>>> Subject: [Dev-C++] Demystifying namespace
>>>
>>> I have a little bit of a problem with 'namespace'. Here is my problem:
>>> namespace foo{
>>>    #define file __func__
>>>    #define line __LINE__
>>>    enum error_t {one, two, three};
>>> }
>>> namespace foo{
>>>   class loo{
>>>      public:
>>>         loo(){
>>>            std::string f = foo::file;
>>>            size_t l = foo::line;
>>>            std::cout << "file: " << f << " line: " << l << std::endl;
>>>            std::cout << foo::one << foo::two << foo::three << 
>>> std::endl;
>>>         }
>>>   };
>>> }
>>> These std::cout's give me a parse error, what am I doing wrong?
>>>
>>>
>>>   
>>
>>
>>  
>>
>

I apologize if you felt offended. Perhaps you are a much better 
programmer than I am, at least that is what you presume; as you said, 
you have the programming knowledge and experience that most people in 
this mail list would only dream of having. If only a little bit of good 
manners and a better knowledge of the English language would accompany 
your "outstanding" knowledge of C++ programming,  I am sure you would be 
a much, much better person.
To the other members here I say, pd...@xs... does not by any means 
represent the good nature and/or mature behaviour we adhere to here. I, 
as most serious programmers in here, will block any farther 
communication with this individual.
Best regards, and have a Merry Christmas.

pd...@xs... wrote:

>Don't get cocky you little shit, you're the one having problems, not me. I
>have more programming knowledge and experience than you could ever hope to
>acquire, so you'd better just shut up.
>I tried giving you friendly advice, you spit it in my face, so now you can
>just fuck off and die for all I care, asshole.
>
>
>-----Original Message-----
>From: Maya [mailto:Esc...@ne...] 
>Sent: Thursday, December 18, 2003 9:34 PM
>To: pd...@xs...; gtk...@gn...; C/C++ Programmers; Dev - C++; Gtk+
>mailing list
>Subject: Re: [Dev-C++] Demystifying namespace
>
>I want to replace the word __func__ with the word file, and you are 
>telling me to assign the value of __func__ to the std::string variable?
>
>Gotta check those books again, eh!
>
>pd...@xs... wrote:
>
>  
>
>>You shouldn't use #defines. #defines are cross-everything, they don't care
>>about scope, namespaces, functions, whatever. It's just a simple global
>>search&replace operation performed by the preprocessor. If you want your
>>namespace code to work, change it to something like:
>>
>>namespace foo{
>>   const std::string file = __func__;
>>   const size_t      line = __LINE__;
>>} 
>>
>>Note that I didn't test this though, but it should work (and didn't you
>>    
>>
>mean
>  
>
>>__FILE__ instead of __func__ there?)
>>
>>Regards,
>>
>>
>>Paul
>>
>>-----Original Message-----
>>From: dev...@li...
>>[mailto:dev...@li...] On Behalf Of Maya
>>Sent: Thursday, December 18, 2003 7:49 AM
>>To: C/C++ Programmers; Dev - C++
>>Subject: [Dev-C++] Demystifying namespace
>>
>>I have a little bit of a problem with 'namespace'. Here is my problem:
>>namespace foo{
>>    #define file __func__
>>    #define line __LINE__
>>    enum error_t {one, two, three};
>>}
>>namespace foo{
>>   class loo{
>>      public:
>>         loo(){
>>            std::string f = foo::file;
>>            size_t l = foo::line;
>>            std::cout << "file: " << f << " line: " << l << std::endl;
>>            std::cout << foo::one << foo::two << foo::three << std::endl;
>>         }
>>   };
>>}
>>These std::cout's give me a parse error, what am I doing wrong?
>> 
>>
>>    
>>
>
>  
>

-- 

FYI
http://www.astro.umd.edu/~marshall/abbrev.html

E-Mail Policy
http://www.vif.com/users/escalante/Email_Policy.html

* You cannot exercise your power to a point of humiliation.
                               - Jean Chretien

* The media's the most powerful entity on earth. They have the 
  power to make the innocent guilty and to make the guilty 
  innocent, and that's power. 
                                - Malcom X
* "Innocent until proven guilty", no... not in Canada!!

Yeah, I understand that perfectly.
I understood the last maya's question as "passing them (__func__ and 
__line__) to a srting!!!??? What you say passes the value, I wanted to 
pass the variable name*". The answer, is that her code, was intending to 
do just that an std:string variable to which a __func__ or __liner__ 
were to be passed..
It was like her was thinking that when passing the #defined name for 
them the item passed to her string variables where something like the 
name of the "definition" variable, which has no sense. Hum, in that 
moment I saw that sense of her question clearly, know, I wonder if I 
really understood her question.

And yes, the errors should appear there, but I've noticed mingw has some 
tendency to point the errors related to #defined thing in the next 
lines; and thos related to missing ';' in headers to the begining of the 
source file which includes the header.

Thanks.

P.S. - The high cross-posting comes from her message, I simply clicked 
'reply all'

*which translated to code, say
 __line__ = "this is the line blah" (sorry if this has no sense, but I'd 
never used this);
She thinks,
if #define foo __line__
std::string yuu = foo; ----> yuu = "__line__" (which makes no sense) 
instead of "this is the line blah".

Lars Hallberg wrote:

> Carlos García del Monte wrote:
>
>> For what I see, your code is doing exactly the same, but without 
>> using those #defines
>
>
>
> The strange thing is that You get the error in the std::cout. You 
> suposed tho get them erlier.
>
> #define declare preprosessor constant ('dumb' text string constants) 
> that is global, they shuld not care about scope. They are replaced 
> litary as text. Your code:
>
>            std::string f = foo::file;
>            size_t l = foo::line;
>
> Transforme to:
>
>            std::string f = foo::__func__;
>            size_t l = foo::__LINE__;
>
> or rather, the value of thes 'special' constants at the #define. The 
> compile shuld likely find errors there :-/
>
> Maya:s code actuly declare thes constants as 'real' constants in the 
> scoop foo, shuld make all the differens!
>
> PS Litle *too* much crosposting this, is it not? DS
>
> HTH /LaH
>
>>
>> Maya wrote:
>>
>>> I want to replace the word __func__ with the word file, and you are 
>>> telling me to assign the value of __func__ to the std::string variable? 
>>
>

Hello good people, is C++ suitable for mobile phone application
development? All i hear about is Java. How popular is C++ when it comes
to developing applications for the mobile phone with regards to the
curent OS available.

Thanks.


__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/

For what I see, your code is doing exactly the same, but without using 
those #defines

Maya wrote:

> I want to replace the word __func__ with the word file, and you are 
> telling me to assign the value of __func__ to the std::string variable?
>
> Gotta check those books again, eh!
>
> pd...@xs... wrote:
>
>> You shouldn't use #defines. #defines are cross-everything, they don't 
>> care
>> about scope, namespaces, functions, whatever. It's just a simple global
>> search&replace operation performed by the preprocessor. If you want your
>> namespace code to work, change it to something like:
>>
>> namespace foo{
>>    const std::string file = __func__;
>>    const size_t      line = __LINE__;
>> }
>> Note that I didn't test this though, but it should work (and didn't 
>> you mean
>> __FILE__ instead of __func__ there?)
>>
>> Regards,
>>
>>
>> Paul
>>
>> -----Original Message-----
>> From: dev...@li...
>> [mailto:dev...@li...] On Behalf Of Maya
>> Sent: Thursday, December 18, 2003 7:49 AM
>> To: C/C++ Programmers; Dev - C++
>> Subject: [Dev-C++] Demystifying namespace
>>
>> I have a little bit of a problem with 'namespace'. Here is my problem:
>> namespace foo{
>>     #define file __func__
>>     #define line __LINE__
>>     enum error_t {one, two, three};
>> }
>> namespace foo{
>>    class loo{
>>       public:
>>          loo(){
>>             std::string f = foo::file;
>>             size_t l = foo::line;
>>             std::cout << "file: " << f << " line: " << l << std::endl;
>>             std::cout << foo::one << foo::two << foo::three << 
>> std::endl;
>>          }
>>    };
>> }
>> These std::cout's give me a parse error, what am I doing wrong?
>>  
>>
>

I want to replace the word __func__ with the word file, and you are 
telling me to assign the value of __func__ to the std::string variable?

Gotta check those books again, eh!

pd...@xs... wrote:

>You shouldn't use #defines. #defines are cross-everything, they don't care
>about scope, namespaces, functions, whatever. It's just a simple global
>search&replace operation performed by the preprocessor. If you want your
>namespace code to work, change it to something like:
>
>namespace foo{
>    const std::string file = __func__;
>    const size_t      line = __LINE__;
>} 
>
>Note that I didn't test this though, but it should work (and didn't you mean
>__FILE__ instead of __func__ there?)
>
>Regards,
>
>
>Paul
>
>-----Original Message-----
>From: dev...@li...
>[mailto:dev...@li...] On Behalf Of Maya
>Sent: Thursday, December 18, 2003 7:49 AM
>To: C/C++ Programmers; Dev - C++
>Subject: [Dev-C++] Demystifying namespace
>
>I have a little bit of a problem with 'namespace'. Here is my problem:
>namespace foo{
>     #define file __func__
>     #define line __LINE__
>     enum error_t {one, two, three};
>}
>namespace foo{
>    class loo{
>       public:
>          loo(){
>             std::string f = foo::file;
>             size_t l = foo::line;
>             std::cout << "file: " << f << " line: " << l << std::endl;
>             std::cout << foo::one << foo::two << foo::three << std::endl;
>          }
>    };
>}
>These std::cout's give me a parse error, what am I doing wrong?
>  
>

-- 

FYI
http://www.astro.umd.edu/~marshall/abbrev.html

E-Mail Policy
http://www.vif.com/users/escalante/Email_Policy.html

* You cannot exercise your power to a point of humiliation.
                               - Jean Chretien

* The media's the most powerful entity on earth. They have the 
  power to make the innocent guilty and to make the guilty 
  innocent, and that's power. 
                                - Malcom X
* "Innocent until proven guilty", no... not in Canada!!

You shouldn't use #defines. #defines are cross-everything, they don't care
about scope, namespaces, functions, whatever. It's just a simple global
search&replace operation performed by the preprocessor. If you want your
namespace code to work, change it to something like:

namespace foo{
    const std::string file = __func__;
    const size_t      line = __LINE__;
} 

Note that I didn't test this though, but it should work (and didn't you mean
__FILE__ instead of __func__ there?)

Regards,


Paul

-----Original Message-----
From: dev...@li...
[mailto:dev...@li...] On Behalf Of Maya
Sent: Thursday, December 18, 2003 7:49 AM
To: C/C++ Programmers; Dev - C++
Subject: [Dev-C++] Demystifying namespace

I have a little bit of a problem with 'namespace'. Here is my problem:
namespace foo{
     #define file __func__
     #define line __LINE__
     enum error_t {one, two, three};
}
namespace foo{
    class loo{
       public:
          loo(){
             std::string f = foo::file;
             size_t l = foo::line;
             std::cout << "file: " << f << " line: " << l << std::endl;
             std::cout << foo::one << foo::two << foo::three << std::endl;
          }
    };
}
These std::cout's give me a parse error, what am I doing wrong?
-- 

FYI
http://www.astro.umd.edu/~marshall/abbrev.html

E-Mail Policy
http://www.vif.com/users/escalante/Email_Policy.html

* You cannot exercise your power to a point of humiliation.
                                - Jean Chretien

* The media's the most powerful entity on earth. They have the
   power to make the innocent guilty and to make the guilty
   innocent, and that's power.
                                 - Malcom X
* "Innocent until proven guilty", no... not in Canada!!




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&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

I have a little bit of a problem with 'namespace'. Here is my problem:
namespace foo{
     #define file __func__
     #define line __LINE__
     enum error_t {one, two, three};
}
namespace foo{
    class loo{
       public:
          loo(){
             std::string f = foo::file;
             size_t l = foo::line;
             std::cout << "file: " << f << " line: " << l << std::endl;
             std::cout << foo::one << foo::two << foo::three << std::endl;
          }
    };
}
These std::cout's give me a parse error, what am I doing wrong?
-- 

FYI
http://www.astro.umd.edu/~marshall/abbrev.html

E-Mail Policy
http://www.vif.com/users/escalante/Email_Policy.html

* You cannot exercise your power to a point of humiliation.
                                - Jean Chretien

* The media's the most powerful entity on earth. They have the
   power to make the innocent guilty and to make the guilty
   innocent, and that's power.
                                 - Malcom X
* "Innocent until proven guilty", no... not in Canada!!

Murphy escribió:

> I need access to Port  IO. I am looking for the
> equivalent of - outportb, outb, inportb, inpb in Dev cpp.
>  
> I am running WIN2000 and have a driver that gives me direct access to 
> IO ports.

I´m afraid Dev-C++ doesn´t have these functions

Try this link http://www.internals.com/
Search for winIo library (the very first of the page)

Regards
-- 

---------------------------------------------------
     Ricardo Amores Hernández 
	ICQ: 19463735
	MSN: zheo_ (at) hotmail (dot) es
---------------------------------------------------

Jack Chen escribió:

>Thank you, THANK YOU, Sir. Problem solved!
>
>How did you know it's the arguments in Main() that's causing all the
>trouble? Man I've been searching on the net for 4 hours, on GCC,
>Cygwin, MingW, SDL, and whole bunch of tutorials just to get my simple
>OpenGL triangle to compile.
>  
>
Humm are you sure you really searched that long?
http://www.libsdl.org/faq.php?action=listentries&category=4#48

When everything fails, use the FAQs ;)

Regards

-- 
---------------------------------------------------
     Ricardo Amores Hernández 
	ICQ: 19463735
	MSN: zheo_ (at) hotmail (dot) es
---------------------------------------------------