|
Sorry, no.
The compiler fault: 'getMyVar2' : this-pointer cannot be converted from 'const class MyClass' to 'class MyClass &'
If I write:
bool MyClass::operator < (const MyClass& crefCl) { return (::strcmp(m_myVar2, crefCl.m_myVar2) < 0);}
the same fault
|
|
|
|
|
|
Thank you! Yes I am a newbie! Therefor I ask. Why do you make it so difficult to me? It is your Intention?
It is so easy to post a simple code instead to make a secret from that.
I find out the easy way myself bei Codeguru, only short way:
http://www.codeguru.com/forum/showthread.php?t=366063[^]
|
|
|
|
|
nne-vitamin wrote: Why do you make it so difficult to me?
2 things :
- because it is not difficult if you know the basics of C++ (which is apprently not the case)
- the example on codeguru is exactly what i suggested you, but unfortunately, you didn't apply it correctly. it's not my fault buddy. learning C++ was only a good advice, now, the balls are in your area ; you do what you want...
TOXCCT >>> GEII power
[toxcct][VisualCalc 2.20][VisualCalc 3.0]
|
|
|
|
|
FYI:
Most C++ experts recommend that you make operator<() a non-member function.
And that you create a operator<=() as a member function.
That paticular example in CodeGuru is not a good one, and it may be a little out date.
Top ten member of C++ Expert Exchange.
http://www.experts-exchange.com/Cplusplus
|
|
|
|
|
// We use this object so that list::sort() can sort in a different
// order.Normally greater<> is used. We override it here to switch to
// less.
class less_str : public greater<string> {
public:
bool operator()(const string& _X, const string& _Y) const
{
return _X <= _Y;
}
};
I have directly use the list.sort(less_str());
In this processing, I have trace into ...
but it always get into greater<string> operator (), why it don't get into less_str operator()?
|
|
|
|
|
|
If you use VC++ 6.0 it's probably a bug in VC++ 6.0. See MSDN
|
|
|
|
|
Dear Members,
I need to color a button using ATL, WTL or WIN 32 API..
I can easily do it using MFC but because of the Application requirement
I have to do it by using the above mentioned technologies only.
Kindly help me out by sending tips and useful codes.
Regards,
Mayank Srivastava
|
|
|
|
|
srimayank11_codeproject wrote: I need to color a button using ATL, WTL or WIN 32 API..I can easily do it using MFC but because of the Application requirementI have to do it by using the above mentioned technologies only.
Here's a good start with WTL:
class CColorButton : public CWindowImpl<CColorButton, CButton> {
public:
DECLARE_WND_SUPERCLASS(_T("CColorButton"), _T("BUTTON"))
BEGIN_MSG_MAP(CColorButton)
MSG_OCM_DRAWITEM(OnDrawItem)
END_MSG_MAP()
public:
void OnDrawItem(UINT uCode, LPDRAWITEMSTRUCT pdis) {
}
};
Please note that you will have to make your button BS_OWNERDRAW (window style flag). This unfortunately makes the button unable to work properly as a default button. If you need this functionality, I can provide that code as well. I just wanted to make this code as simple and easy to understand as possible, as it illustrates how to draw the button yourself easily. Also, please do not forget to add REFLECT_NOTIFICATIONS() in your parents message handler. If you don't, your button will not be drawn.. at all! 
--
Pictures[^] from my Japan trip.
|
|
|
|
|
As many of you probably know, Visual Studio 2005 contains a nasty std::iostream bug that causes a memory leak. If, like me, you use streams such as stringstream/wstringstream, fstream, etc. you will be affected. The fix is to rebuild the MSVCRT80.DLL, which is a major undertaking and, IMHO, not worth the pain.
Hence I thought I'd investigate STLPort. I have heard good things about this library, and it would allow me to work around the iostream bug, as I wouldn't be using the MS implementation.
However, I also use Boost, and there doesn't seem to be a config for VS 2005 _and_ STLPort! Sob. Has anyone here made the three work together?
The Rob Blog
Google Talk: robert.caldecott
|
|
|
|
|
Robert Edward Caldecott wrote: The fix is to rebuild the MSVCRT80.DLL, which is a major undertaking and, IMHO, not worth the pain.
It's also a pain because you'd have to put the DLL next to your binary. You never know which app will overwrite that file. So in essence, it'd be like using a static library, but with a bigger startup overhead! 
Robert Edward Caldecott wrote: However, I also use Boost, and there doesn't seem to be a config for VS 2005 _and_ STLPort! Sob. Has anyone here made the three work together?
I don't see how boost comes into the picture..? IIRC, STLPort is supposed to be a drop in replacement for the regular STL library that ships with Visual Studio. As for the missing config for VS 2k5, have you tried using the 2k3 config? It might work straight out of the box...
--
Pictures[^] from my Japan trip.
|
|
|
|
|
Jörgen Sigvardsson wrote: I don't see how boost comes into the picture..?
Boost has different jam configs when building for VC + STLPort, so I think it must be relevanr somehow...
The Rob Blog
Google Talk: robert.caldecott
|
|
|
|
|
Jörgen Sigvardsson wrote: It's also a pain because you'd have to put the DLL next to your binary. You never know which app will overwrite that file.
What do you mean by this?
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
|
|
|
|
|
If you rebuild the crt dll, and install it in say Windows\System32, it could be overwritten by another program. Overwritten with the "original" crt dll which has the memory leaks.
If you put the dll alongside the binary, the chances of another application overwriting it is virtually zero.
--
Pictures[^] from my Japan trip.
|
|
|
|
|
Jörgen Sigvardsson wrote: If you rebuild the crt dll, and install it in say Windows\System32,
Shudder. Never even cross my mind to install anything in System32, but you are right - many people actually do that
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
|
|
|
|
|
Uh huh. I've stopped doing that as well. It used to be "correct practice" once I believe, but it's just asking for headaches. I do DLLs only these days, but I put them side by side with the executable. It won't be much better than .libs from an optimization point of view (shared code, etc). But it is easier from a maintainence point of view, as I only have to patch affected DLLs, and not the entire app.
Another great benefit with DLLs is that it's very easy to debug code on site, as it's just a matter of replacing the DLLs which contains TRACE messages, and/or similar debugging I/O.
I like DLLs. Does it show?
--
Pictures[^] from my Japan trip.
|
|
|
|
|
Jörgen Sigvardsson wrote: I like DLLs
Me too. Although it wouldn't hurt if we got some standard C++ module/component system on top of them. The .NET component system is one of the rare things where .NET is really a better development environment than C++. I know there is COM, but a) it is bloated and b) it is not portable.
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
|
|
|
|
|
I'd ask on the Boost Users mailing list - that's probably more likely to get a useful (or at least definitive) reply...
|
|
|
|
|
Robert Edward Caldecott wrote: The fix is to rebuild the MSVCRT80.DLL, which is a major undertaking and, IMHO, not worth the pain.
Apparently, there is another "unofficial" way: Look at the third reply from the bottom of this page:[^]
Steps:
1) Open up istream in \Program Files\Microsoft Visual Studio 8\VC\Include
2) Before line 29, insert the following code
explicit __CLR_OR_THIS_CALL basic_istream(_Mysb *_Strbuf, bool _Isstd, bool _Noinit)
: _Chcount(0)
{ // construct from stream buffer pointer
if (!_Noinit)
_Myios::init(_Strbuf, _Isstd);
}
3) In the same file (istream), look for the following line:
: basic_istream<_Elem, _Traits>(_Strbuf, false),
and change it to:
: basic_istream<_Elem, _Traits>(_Strbuf, false, true),
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
|
|
|
|
|
Much appreciated Nemanja.
The Rob Blog
Google Talk: robert.caldecott
|
|
|
|
|
Hi all,
Does aNy body know how we can pass strucutres ( types in VB ) as parameters of function defined in COM DLL interface ?
For e.g. I have one interface called IDatabase and i want to add method like
"HRESULT SetData([in]USER userData)".
In this case the DLL is compiled successfully, but when it is used in the Visual Basic, it gives error
"user defined object can not be passed by value". The DLL should be used in both VB and VC++ client applicaitons.
Karnav Zaveri
|
|
|
|
|
It's not a simple task to pass structures in COM/DCOM.
1. A structure must be of the type VT_RECORD.
2. All the structure's fields must be of an automation-compatible type.
3. The structure must be described in a TLB.
4. The structure must have a GUID (assigned in the IDL file).
5. A special structure-oriented interface IRecordInfo must be used to manipulate structures (IRecordInfo::RecordCreate(), IRecordInfo::RecordDestroy(), etc.).
|
|
|
|
|
Anyone use this product? If so, did you update it for VC7+? If so...I need to talk to you! 
ed
~"Watch your thoughts; they become your words. Watch your words they become your actions.
Watch your actions; they become your habits. Watch your habits; they become your character.
Watch your character; it becomes your destiny."
-Frank Outlaw.
|
|
|
|
|
Dear all,
I am new to ATL COM programming and the question may be silly, but pls help.
In the COM, I have defined one Simple Object Add with the inferface IAdd. Then in the client program I try to get the COM interface using following:
CComPtr<iadd> pAdd;
HRESULT hr = pAdd.CoCreateInstance(CLSID_Add);
here got problem, the following ASSERT failed;
ASSERT(hr==S_OK);
Then I define the connection Container pointer,
IConnectionPointContainer * pCPC;
hr = pAdd->QueryInterface(IID_IConnectionPointContainer, (void **) &pCPC;
Then I got the assertion failure again and it is atlbase.h line 758 assertion failed.
The program is quite simple, but I just don't know where is the problem. Please help!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
