dev-cpp-users — Dev-C++ users discussion list

[Dev-C++] A GUI for my program

[Maya <Esc...@ne...>]

Hey!
Using C++, I have written a small application  for which I'd like to add 
a GUI. I have been looking at FOX, FLTK GTK+ and wxWindows. It's been 
only for GTK+ that I have found a book, the other libraries have some 
virtual documentation, but most of it is not in sync with the version of 
the GUI tool kit. GTK+ has good documentation, but is written in 'C', 
and my program is in C++. So here is my question, is there a way to 
develop the GUI in GTK+ to be connected to a C++ program?

Thanks in advance

-- 

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!!

Re: [Dev-C++] C++ and mobile phone application programming.

[<de...@ci...>]

C++ is a good language for Symbian phones because the whole O/S is written 
in C++.

C++ software has more access to the phone facilities than Java.

However Symbian's use of C++ is carefully constrained to the small 
platform, and there are a number of quirks that must be learnt for 
successful programming.


In article <200...@we...>, 
n_a...@ya... (Napoleon Ahiable) wrote:

> 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/
> 

Re: [Dev-C++] Updating GCC

[Tim S. <ti...@we...>]

Hi Hossein,

Hossein Haeri wrote:

> Now, what should I do if I want to update it to GCC 3.3.2?

You have to download
http://prdownloads.sourceforge.net/mingw/gcc-g++-3.3.1-20030804-1.tar.gz?download

and

http://prdownloads.sourceforge.net/mingw/gcc-core-3.3.1-20030804-1.tar.gz?download

and extract the files to a temporary directory. Then copy the 
bin, include and lib directory into your Dev-Cpp directory and 
then you should check with C:\Dev-Cpp\bin\gcc.exe -v (Or where 
you have installed Dev-Cpp) the version, it *should* be 3.3.1. 
As far as I know there is nor 3.3.2 yet for mingw.

so long

Tim

-- 
WE ARE TEH BORG!
     RESSISTANCE IS FUTILE!
   http://we-are-teh-b.org/~tim/borg.key

Re: [Dev-C++] checking out the .asm

[Piotr O. Z.E.S. <co...@si...>]

----- Original Message ----- 
From: "P.T. Waugh MA" <pt...@ea...>
To: <dev...@li...>
Sent: Friday, December 19, 2003 9:55 AM
Subject: [Dev-C++] checking out the .asm


> Hi all,
> 
> Was wondering if it's possible, using the DEV-C++ IDE, to inspect the 
> asembly code generated by the compiler... ie have the compiler leave it, 
> rather than delete it when finished.
> 
> Thanks, Patrick
> 
> 

You can use -save-temps compiler option to keep temporary assembler files.

I use Project/Project Options/Files/tick Override build command
and add -save-temps to options line.
Compiler leaves temporary assembler file with name of source c/c++ file
and with *.s extention.

Greetings,
Collins

> 
> -------------------------------------------------------
> 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

Re: [Dev-C++] Demystifying namespace

[Maya <Esc...@ne...>]

Thanks!
That's what I call knowing stuff,  man!
One last question, in the case below, why is it that I get an error!
namespace jme{
   enum error_t{
       //Generic error codes

    MSG,               //Default message
    WARNING,           //Warning
    FATAL,             //Display fatal and exit
    .....
};

   class Someprogram{
      std::string* str_example;
         public:
            Someprogram(){
                try{str_example = new std::string;}
                catch(std::bad_alloc& x){
                   // This works!!!!
                   throw jme::SomeprogramEx(MSG, FILE, METHOD,LINE);
                   // This doesn't ?????
                   throw jme::SomeprogramEx(jme::MSG, FILE, METHOD, LINE);
                }

     }
  }; //Someprogram
} // namespace

By the way, Maya is the Sanskrit [ ancient Hindu language ] word for 
illusion. It's a hippy thing... I guess. :-\
pw...@ia... wrote:

>1)
>Please. Take as a custom to always use ALL CAPS when #define symbols. It
>is practically impossible to read the code if you don't. Since a #defined
>symbol might be just about any type of expansion it is really important
>when reading the code.
>
>2)
>Since a #defined symbol is a preprocessor construct, they are never - I
>repeat NEVER - inside any namespace. If the compiler have seen the
>#define, and it hasn't been terminated by an #undefine, it will be used.
>The compiler complains, since you try jme::file, jme::line, ... where file
>and line are #defines.
>
>When you write jme::file it represents jme::__FILE__ which is expanded to
>jme::"filename" which isn't a valid construct.
>
>/Per W
>
>On Thu, 18 Dec 2003, Maya wrote:
>
>  
>
-- 

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!!

[Dev-C++] Updating GCC

[Hossein H. <ult...@em...>]

Dear all,

I know that this may be one of the previousely (several times)
discussed topics, but let me ask it again; AFAIK, the GCC with
Dev-C++ 4.9.8.0+ is GCC 3.2, right? Now, what should I do if I
want to update it to GCC 3.3.2?

TIA,
--Hossein
-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm

Re: [Dev-C++] checking out the .asm

[Per W. <pw...@ia...>]

Add a -S to the compiler options, and the compiler will just emit
assembler files.

/Per W

On Fri, 19 Dec 2003, P.T. Waugh MA wrote:

> Hi all,
>
> Was wondering if it's possible, using the DEV-C++ IDE, to inspect the
> asembly code generated by the compiler... ie have the compiler leave it,
> rather than delete it when finished.
>
> Thanks, Patrick
>
>
>
> -------------------------------------------------------
> 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
>

[Dev-C++] checking out the .asm

[P.T. W. M. <pt...@ea...>]

Hi all,

Was wondering if it's possible, using the DEV-C++ IDE, to inspect the 
asembly code generated by the compiler... ie have the compiler leave it, 
rather than delete it when finished.

Thanks, Patrick

Re: [Dev-C++] HELP !!

[cwic <cw...@ma...>]

Hello Felix,

Friday, December 19, 2003, 9:03:55 AM, you wrote:

FA> This is very confusing. I don't understand what does  : undefined
FA> reference means. I use Dev C++ 4.9.8.5 on WinXP

You need to include appropriate cgicc library into your link process.

In headers (*.h) files you have the prototypes of functions, but the
'real meat' is in library file. Compiler need to know where to search
for function body.

-- 
Best regards,
 cwic                            mailto:cw...@ma...

[Dev-C++] HELP !!

[Felix A. <an...@cb...>]

Hi all, 

 

I'm a novice in C++ and I'm trying to use GNU cgicc library. I've a
problem like this :

 

I've installed the cgicc library in my include directory file, I assure
you that I can call the header file from my source code eg. #include
"cgicc/HTTPHTMLHeader.h"

But the error message like the below keep popping up.

 

C:\DOCUME~1\Felix\LOCALS~1\Temp\ccIpbaaa.o(.text+0x32)     [Warning] In
function `main':

[Linker error] undefined reference to
`cgicc::HTTPHTMLHeader::HTTPHTMLHeader()' 

[Linker error] undefined reference to
`_imp___ZN5cgicclsERSoRKNS_11MStreamableE' 

[Linker error] undefined reference to
`cgicc::HTTPHTMLHeader::~HTTPHTMLHeader()' 

[Linker error] undefined reference to
`cgicc::HTTPHTMLHeader::~HTTPHTMLHeader()' 

[Linker error] undefined reference to `_GLOBAL__I_main' 

[Linker error] undefined reference to `_GLOBAL__D_main'

 

my code is :

 

#include <iostream>

#include "cgicc/HTTPHTMLHeader.h"

 

using namespace std;

using namespace cgicc;

 

main()

{

 

cout << HTTPHTMLHeader() << endl << endl ;

cout << "Hello world" ;

return (0);

}

 

it should be right and return "Hello world" right ???

 

This is very confusing. I don't understand what does  : undefined
reference means. I use Dev C++ 4.9.8.5 on WinXP

 

Anyone can help ? Thank you very much

 

Sincerely

Felix Ang

[Dev-C++] Re: [Mingw-users] C++ and mobile phone application programming.

[Timothy S. <tis...@fa...>]

Napoleon Ahiable wrote:

> 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.
> 

See http://www.symbian.com/books/index.html for c++ development for  	
Symbian OS phones.

Timothy

Re: [Dev-C++] Copy constructor or assignment operator

[Per W. <pw...@ia...>]

Please - don't send your questions to zillions of mailing lists! Select
ONE (1) for your questions. I can't see what your question have with the
gtk+ or foxgui mailing list for example.

Anyway. When the input parameter is const, you may not change it or let a
non-const pointer or reference point to it. If the assignment was legal,
you would then be able to throw away the const, thereby allowing
assignment to the original Name object.

/Per W

On Thu, 18 Dec 2003, Maya wrote:

> Hey folks!
> I am having problems grasping the meaning of 'operator=' and copy
> constructor.
> In the following example
> namespcace jme{
>     class Name{
>           std::string str;
>        public:
>           Name(){}
>           Name(const jme::Name& rhs){ this->str = rhs.str;}
>           ~Name(){}
>           jme::Name& operator=(const jme::Name& rhs) {
>              if(this->str == rhs.str ) {
>              return *this;
>           }
>           this->str = rhs.str;
>           return *this;
>        }
>     };
>     class Person{
>        private:
>           jme::Name* name;
>           Init()throw(std::bad_alloc){
>              try{name = new jme::Name;}
>              catch(std::bad_alloc& x){ throw;}
>           }
>        public:
>
>           Person(const jme::Name& n){
>              try{ Init(); }
>              catch(std::bad_alloc& x){ throw; }
>              name = &n; // <<== Here is the problem
>          }
>     }
>
> I get an error saying: Invalid conversion 'const jme::Name*' to 'jme::Name*'
>
> If I change the parametized c'tor to jme::Person::Person(jme::Name& n) the
> constantness disapears and the program compiles, but that is not what I
> want.
> What I want if the c'tor to receive a reference to a constant jme::Name.
>
> Can someone please, help me understand what is that I am 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
>

[Dev-C++] Copy constructor or assignment operator

[Maya <Esc...@ne...>]

Hey folks!
I am having problems grasping the meaning of 'operator=' and copy 
constructor.
In the following example
namespcace jme{
    class Name{
          std::string str;
       public:
          Name(){}
          Name(const jme::Name& rhs){ this->str = rhs.str;}
          ~Name(){}
          jme::Name& operator=(const jme::Name& rhs) {
             if(this->str == rhs.str ) {
             return *this;
          }
          this->str = rhs.str;
          return *this;
       }
    };
    class Person{
       private:
          jme::Name* name;
          Init()throw(std::bad_alloc){
             try{name = new jme::Name;}
             catch(std::bad_alloc& x){ throw;}
          }
       public:

          Person(const jme::Name& n){
             try{ Init(); }
             catch(std::bad_alloc& x){ throw; }
             name = &n; // <<== Here is the problem
         }
    }

I get an error saying: Invalid conversion 'const jme::Name*' to 'jme::Name*'

If I change the parametized c'tor to jme::Person::Person(jme::Name& n) the
constantness disapears and the program compiles, but that is not what I 
want.
What I want if the c'tor to receive a reference to a constant jme::Name.

Can someone please, help me understand what is that I am 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!!

Re: [Dev-C++] Demystifying namespace

[Per W. <pw...@ia...>]

1)
Please. Take as a custom to always use ALL CAPS when #define symbols. It
is practically impossible to read the code if you don't. Since a #defined
symbol might be just about any type of expansion it is really important
when reading the code.

2)
Since a #defined symbol is a preprocessor construct, they are never - I
repeat NEVER - inside any namespace. If the compiler have seen the
#define, and it hasn't been terminated by an #undefine, it will be used.
The compiler complains, since you try jme::file, jme::line, ... where file
and line are #defines.

When you write jme::file it represents jme::__FILE__ which is expanded to
jme::"filename" which isn't a valid construct.

/Per W

On Thu, 18 Dec 2003, Maya wrote:

> Ok, see that there are a few misunderstandings here. I know that using
> the preprocessor '#define' means kind of "replace", so in my statement
> '#define  line      __LINE__' what I am saying is: the next time I use
> 'line' what I really mean is '__LINE__', but in my rush to finish the
> program I started to treat 'line' as a variable, i.e. std::cout <<
> jme::line << std::endl which of course is wrong, that is clear to me now.
>
> I have handed in the program at school, and even though it works, I
> still have a lot of questions about  'namespace'. I know what you are
> thinking, ask the teachers! that's what my dad tells me too. Well I
> have, but the teachers in my high school are too preoccupied with the
> Christmas stuff to explain it in way that makes sense to ME and not only
> to THEM. I mean. So,  any help from you guys will be appreciated.
>
> Please don't be rude if I ask questions that are very simple to you, and
> above all, don't take me wrong if I say something that might sound
> insulting; it is never my intention to be rude to anyone.
> I share my email with my dad; he was really P.O. about some guy wring
> obscenities to me. I mean, think about what would you feel if someone
> starts using that kind of language with your kids, eh!
>
> Hava a good Ho Ho Ho
>
> This class is part of a program I wanted to hand in at school, but as we
> all know
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> =3D=3D=3D GCC =3D=3D=3D
> namespace jme {
>
> #define  method    __PRETTY_FUNCTION__
> #define  file          __FILE__
> #define  line          __LINE__
> #define  function  __func__
>
> enum error_t{
>     //Generic error codes
>     msg,               //Default message
>     warning,           //Warning
>     fatal,             //Display fatal and exit
>     .....
> };
> class Exception{
> protected:
>      error_t error;
>     std::string File, Method;
>     size_t Line;
>
> public:
>     //Setters
>     void setException( jme::error_t,  e    // Error code
>                        const std::string&,  fn    // File name
>                        const std::string&,  m      // Method
>                        size_t l)                       // Line
>    {    error =3D e; File =3D fn; Method =3D m; Line =3D l;   }
>
>  };// Exception
> } // namespace
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> --- Someprogram.H -----
> namespace jme{
>     class SomepogramEx : virtual public jme::Exception{
>        public:
>           SomeprogramEx(error_t ec, const std::string& f,
>                          const std::string& m, size_t l);
>      };//End of SomeprogramEx
>     class Someprogram{
>              std::string* str_example;
>          public:
>               Someprogram(){
>                         try{str_example =3D  new std::string;}
>                         catch(std::bad_alloc& x){
>                               // This works!!!!
>                               throw jme::SomeprogramEx(msg, file,
> method, line);
>                                // This doesn't ?????
>                               throw jme::SomeprogramEx(jme::msg,
> jme::file, jme::method, jme::line);
>                         }
>                 }
>        }; //Someprogram
> } // namespace
>
> ce...@te... wrote:
>
> > 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__ =3D "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 =3D foo; ----> yuu =3D "__line__" (which makes no sense=
)
> > instead of "this is the line blah".
> >
> > Lars Hallberg wrote:
> >
> >> Carlos Garc=EDa 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 =3D foo::file;
> >>            size_t l =3D foo::line;
> >>
> >> Transforme to:
> >>
> >>            std::string f =3D foo::__func__;
> >>            size_t l =3D 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?
> >>>
> >>>
> >>
> >
> >
> >
> > -------------------------------------------------------
> > 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 admi=
n.
> > Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick
> > _______________________________________________
> > 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
>
>
> --
>
> 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=3D1278&alloc_id=3D3371&op=3Dclick
> _______________________________________________
> 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
>

Re: [Dev-C++] Demystifying namespace

[Maya <Esc...@ne...>]

Ok, see that there are a few misunderstandings here. I know that using 
the preprocessor '#define' means kind of "replace", so in my statement 
'#define  line      __LINE__' what I am saying is: the next time I use 
'line' what I really mean is '__LINE__', but in my rush to finish the 
program I started to treat 'line' as a variable, i.e. std::cout << 
jme::line << std::endl which of course is wrong, that is clear to me now.

I have handed in the program at school, and even though it works, I 
still have a lot of questions about  'namespace'. I know what you are 
thinking, ask the teachers! that's what my dad tells me too. Well I 
have, but the teachers in my high school are too preoccupied with the 
Christmas stuff to explain it in way that makes sense to ME and not only 
to THEM. I mean. So,  any help from you guys will be appreciated.

Please don't be rude if I ask questions that are very simple to you, and 
above all, don't take me wrong if I say something that might sound 
insulting; it is never my intention to be rude to anyone.
I share my email with my dad; he was really P.O. about some guy wring 
obscenities to me. I mean, think about what would you feel if someone 
starts using that kind of language with your kids, eh!

Hava a good Ho Ho Ho

This class is part of a program I wanted to hand in at school, but as we 
all know
=====================
=== GCC ===
namespace jme {

#define  method    __PRETTY_FUNCTION__
#define  file          __FILE__
#define  line          __LINE__
#define  function  __func__

enum error_t{
    //Generic error codes
    msg,               //Default message
    warning,           //Warning
    fatal,             //Display fatal and exit
    .....
};
class Exception{
protected:
     error_t error;
    std::string File, Method;
    size_t Line;

public:
    //Setters
    void setException( jme::error_t,  e    // Error code
                       const std::string&,  fn    // File name
                       const std::string&,  m      // Method
                       size_t l)                       // Line
   {    error = e; File = fn; Method = m; Line = l;   }
        
 };// Exception
} // namespace
=======================================
--- Someprogram.H -----
namespace jme{
    class SomepogramEx : virtual public jme::Exception{
       public:
          SomeprogramEx(error_t ec, const std::string& f,
                         const std::string& m, size_t l);
     };//End of SomeprogramEx
    class Someprogram{
             std::string* str_example;
         public:
              Someprogram(){
                        try{str_example =  new std::string;}
                        catch(std::bad_alloc& x){
                              // This works!!!!
                              throw jme::SomeprogramEx(msg, file, 
method, line);
                               // This doesn't ?????
                              throw jme::SomeprogramEx(jme::msg, 
jme::file, jme::method, jme::line);
                        }
                }
       }; //Someprogram
} // namespace
 
ce...@te... wrote:

> 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? 
>>>
>>>
>>
>
>
>
> -------------------------------------------------------
> 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


-- 

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!!

[Dev-C++] GetLastError, or the winapi's fraud.

[<ce...@te...>]

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.

Re: [Dev-C++] Demystifying namespace

[<ce...@te...>]

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?
>>>
>>>
>>>   
>>
>>
>>  
>>
>

Re: [Dev-C++] Demystifying namespace

[Maya <Esc...@ne...>]

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!!

Re: [Dev-C++] Demystifying namespace

[<ce...@te...>]

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? 
>>
>

[Dev-C++] C++ and mobile phone application programming.

[Napoleon A. <n_a...@ya...>]

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/

Re: [Dev-C++] Demystifying namespace

[<ce...@te...>]

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?
>>  
>>
>

Re: [Dev-C++] Demystifying namespace

[Maya <Esc...@ne...>]

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!!

RE: [Dev-C++] Demystifying namespace

[P.D. v. Z. <pd...@xs...>]

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

[Dev-C++] Demystifying namespace

[Maya <Esc...@ne...>]

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!!

Re: [Dev-C++] Low-level IO

[<ri...@te...>]

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
---------------------------------------------------