Re: afx_msg (VC++ 6->VS 2005)

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I agree with that. I think I used that feature for maybe 2 minutes then I
decided that I don't like it.

I must admit that back in DOS days I did alot of
main()
{
}

instead of
void main()
{
}

But what I am having problem with here is that I am trying to figure out how
this could have happened in the first place. There aren't too many message
handlers that return an int (Maybe 5 or 6 that I count), I want to know what
message it was attached to that it worked under 6.0 but now requires afx_msg
void XXXX.

AliR.

"Joseph M. Newcomer" <newcomer@xxxxxxxxxxxx> wrote in message
news:f1l203dbbvc8sj5j4cv3dfccto26n5i60g@xxxxxxxxxx
The assume-int-for-return-value was one of the greater mistakes in C. It
was done so that
programmers didn't have to keep typing 'int'. Silly reason. K&R C was a
bad language in
so many ways it is hard to believe we actually tolerated it for so many
years.
joe

On Tue, 20 Mar 2007 14:32:27 -0700, "Tom Serface"
<tom.nospam@xxxxxxxxxxxxx> wrote:

Hi Ali,

I got some of these messages for functions where it just had the afx_msg
tag
(which I think is just a blank define) and no actual type for a function.
In V6 it just assumed int for anything that wasn't typed, but 2005 changed
that behavior to displaying a message and not allowing "non-typed"
variables
or functions.

Tom

"AliR (VC++ MVP)" <AliR@xxxxxxxxxxxxx> wrote in message
news:kMVLh.8631$yW.1896@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Doesn't look like it's complaining about afx_msg, it looks like it's
complaining about the function not having a return type. afx_msg is
still
defined in VS 2005.

AliR.
Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm


.

Relevant Pages