|
|
Java and C# are pretty popular and I would say they are definitely safe choices even in long term. A better questions is: what kind of stuff do you like working on. If you are programming just for money then a rarely used "exotic" language (cobol, haskell, erlang, ...) at the right place and the right time can bring pretty good money.
|
|
|
|
|
pasztorpisti,
Very interesting observation... money value erodes where masses go....
|
|
|
|
|
This is the real world. You are trading one of your most valuable resources with your employer: time
|
|
|
|
|
You should learn English first.
|
|
|
|
|
Having been laid off way too many times, I've gotten a good take on demand. The hottest thing right now is WebServices using C#.NET. Java is up there too, especially Android, but falling fast in that category. Alas, my favorite, C/C++ is not.
|
|
|
|
|
I would suggest that you learn one language, which you already are, from what you write. Then, it becomes a simpler matter to translate that knowledge into another language. What is most important, in my opinion, is the ability to solve a real-world problem using a programming language; rather than mastering the nitty-gritties of a programming language itself.
|
|
|
|
|
Hi,
I am using the 2 step process CWinThread constructer and CreateThread to Create a UI thread
and I am getting a Access Violation somewhere in CWinThread::CreateThread
From the debugger I can already see that the thread has been created as the thread id from
DEBUG->threads matches m_nThreadID
The address where the access violation occurs matches the pointer to my derived CWinThread pointer
threadptr[I}
threadptr[i] = NULL;
threadptr[i] = new SockCLeintThread(start_port);
if (threadptr[i] == NULL)
m_pMainWnd->MessageBox((LPCTSTR)"SockClientThreadFail",NULL,MB_ICONERROR);
threadptr[i]->CreateThread(CREATE_SUSPENDED,0,NULL);
|
|
|
|
|
I have no idea whether this is connected but you should not be casting an ASCII string to a LPCTSTR; the two may not be the same. Use the _T() macro to ensure your strings are generated to the correct mode for the project.
Use the best guess
|
|
|
|
|
fixed that up however that statement was never executed
I inserted this test
ASSERT(threadptr[i]->IsKindOf(RUNTIME_CLASS(SockCLeintThread));
|
|
|
|
|
Which means what?
Use the best guess
|
|
|
|
|
Richard
I don't know why I cleaned up my laptop and all of the sudden my code doesn't
work anyway a couple of points
After I create my CFramewnd and do a Showwindow it doesn't have a window handle its nulls
The Thread after creating the object
CWinThread->wm_pActiveWnd and CWinThread->m_pMainWnd are both NULL I populated via the debugger and CreateThread worked
|
|
|
|
|
Does your thread func start off by calling that AFX_MANAGE_STATE macro (or whatever it is called)? MFC threads need to do thkis else they screw up like this with all sorts of exceptions.
|
|
|
|
|
I populate both the
Main and active window of the thread
With my CFrameWnd * an that seemed to do the trick
Thanks
|
|
|
|
|
I believe AFX_MANAGE_STATE is only needed when exporting certain functions from a DLL which use MFC and load DLL resources.
|
|
|
|
|
I am sure I have had to use it in threads in MFC apps. Its been a while and of course it use could be required in many situations.
|
|
|
|
|
ForNow wrote: m_pMainWnd->MessageBox((LPCTSTR)"SockClientThreadFail",NULL,MB_ICONERROR);
Look at the underlined section. What are you hoping to achieve by the cast? If you're compiling for non-Unicode it does nothing and if it's a Unicode build it tells the compiler not to issue an error but to shut up and assume the ANSI string is a Unicode one, which it's clearly not. Best case scenario is a garbled string in the message box, worst case an access violation because of no double NULL terminator. This is the typical fate of the cast-happy: turning a compile-time error into a runtime one. Don't cast if you don't know what's going on or fumble around casting to suppress a compiler error.
You don't need any casts:
m_pMainWnd->MessageBox(_T("SockClientThreadFail"), NULL, MB_ICONERROR);
Steve
|
|
|
|
|
On which thread do you encounter the access violation? Can you post the piece of code that causes the crash? It would be nice to see the whole code of your worker thread and the codepieces from he main thread that are used in the communication with the worker (like thread creation, receiving messages from the worker).
As "UI thread" I usually name the thread that drives a gui framework, by default in MFC this is the main thread. In my opinion its better to use just one thread to handle the GUI (the main thread with MFC) because that is perfectly enough on every platform with any GUI framework despite the fact that on windows any threads are allowed to create their own set of windows but this is not a good practice. As I see your thread handles networking, how do you send/receive data? In case of multithreading a very nice strategy is minimizing the amount of shared data as much as possible usually by using message posting. Sometimes the amount of shared data can be reduced to zero along with the bugs. Post some code if possible and then we can give advices.
EDIT: Forgot to mention that in MFC there are two different kind of threads: UI threads that support message pumping for the UI and simple worker threads. There are two AfxBeginThread() functions and one of them creates a UI thread while the other creates a worker. You can simply go by creating a worker thread with a lightweight wrapper class around this worker AfxBeginThread() call. Deriving from CWinThread and using its CreateThread method is useful only if you want to reuse the same thread object to execute and exit many threads on it but reusing the same thread object twice is a bad design anyway because it introduces a lot of bugs. Its better to recreate thread objects. If you want to preserve state between thread executions then put the preservable state into a separate object and pass the same state object to every time you recreate the thread after the destruction of the previous thread. Often its better simply keep the thread running than terminating it and then starting another (but in my frameworks I always use pools and precreated threads, the frameworks hides the creation/destruction of threads and that is cool).
modified 17-Aug-13 11:06am.
|
|
|
|
|
I need a template function that takes a stream_type and a data type as template parameters in a function. The purpose for this template function is to either read or write data to a file (binary or text format). I define an stream_traits and its io traits specializations as following:
template <typename T>
struct iostream_traits
{
typedef T stream_type;
};
template<>
struct iostream_traits <std::ofstream>
{
typedef std::ofstream stream_type;
static const bool _bSaving = true;
static const bool _bLoading = false;
};
template<>
struct iostream_traits <std::ifstream>
{
typedef std::ifstream stream_type;
static const bool _bSaving = false;
static const bool _bLoading = true;
};
My template function for read or write is defined as:
template<typename STREAM_T, typename T>
void SerializeElement_IO(STREAM_T &ios, T &t, bool bBinary, char cDelimiter)
{
if (iostream_traits<STREAM_T>::_bSaving)
{
if (bBinary) ios.write(reinterpret_cast<char *>(&t), sizeof(t)); else
{
if (cDelimiter == ' ') ios << t << " "; else if (cDelimiter == '\n') ios << t << std::endl;
else ios << t;
}
}
else
{
if (bBinary) ios.read(reinterpret_cast<char *>(&t), sizeof(t));
else ios >> t;
}
}
However, if I make a call to this template function in a program:
int a = 10;
std::ofstream ofs("DataFile");
SerializeElement_IO(ofs, a, true, ' ');
I got compile errors as
error C2039: 'read' : is not a member of 'std::basic_ofstream<_Elem,_Traits>'
error C3767: '>>': candidate function(s) not accessible
I am sure I have included necessary headers for the program.
I just couldn't understand why the errors are related to read or << operator while an std::ofstream object is passed to the template function.
Is there any way to implement this using traits technique?
modified 3-Aug-13 18:09pm.
|
|
|
|
|
basic_ofstream is inherited from basic_ostream and is used for output.
read is for getting input and so is not implemented in basic_ostream.
On the other hand basic_ifstream which is inherited from basic_istream implements read and not write.
In your case, since the function template uses both read and write, you could use basic_fstream which inherits from basic_iostream which in turn inherits from both basic_istream and basic_ostream.
Or you would need to write 2 separate function templates, one for read and one for write.
|
|
|
|
|
How to find the shortest path between two nodes in a undigraph,but the constraints of this path isthat it should via several given intermediate nodes. This uidigraph is a sparse graph and may not a connected graph.
The weight of every edge in the graph is the same. The number of nodes in the graph is about several thousand.
Do you have some ideas about it? Looking forward to your reply!
|
|
|
|
|
Please do not post the same question in multiple forums.
Use the best guess
|
|
|
|
|
Alcohol is the answer.
When ever you are well pissed it is incredible how quickly you can find your way from the pub to your house wjile passing trough several important nodes such as 1, kebab shop, 2 all nigt shop, 3, bus shelter to relieve yourself.
|
|
|
|
|
Hi,
I have created an application in visualstudio 2008 and i used MFC Featurepack CRibbonBar for designing menu bar. Its working fine in my PC.
When i invoke that application in some other PC which doesnot have Visual studio, its not opening.
I pasted mfc90d.dll ,mfc90ud.dll,mfcm90d.dll,mfcm90ud.dll,Microsoft.VC90.MFC.manifest in that application path. When i open the application,its opening but i cannot find the Ribbon menubar.
Just the view window get enlarged and filled the screen.
I think im missing some Dlls related to MFC Feature Pack.
Please help me how to resolve this problem. I want to run this application in my Client PC.
Anu
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
