C++ - "We don't use STL here"
-
Well, he is the boss, right? If he is ready to pay you for the extra hours you are going to spend because you can't use the Standard Library, it's all good and well. Your time is his money, right? ;)
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
Nemanja Trifunovic wrote: Well, he is the boss, right? If he is ready to pay you for the extra hours you are going to spend because you can't use the Standard Library, it's all good and well. Your time is his money, right? And if they just use containers from MFC or another library instead of STL bloatware?
-
That's what I was told by my boss in my last contract, when he was looking at some of my code that used it. His view was that he wouldn't touch it with a barge pole. Given that STL is a part of Standard C++ what do you guys think of such an attitude? Kevin
Kevin McFarlane wrote: Given that STL is a part of Standard C++ what do you guys think of such an attitude? May be, He doesn't like STL at all
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers, Alok Gupta
-
That's what I was told by my boss in my last contract, when he was looking at some of my code that used it. His view was that he wouldn't touch it with a barge pole. Given that STL is a part of Standard C++ what do you guys think of such an attitude? Kevin
Unfortunately, his attitude was probably formed from the poor support for the STL provided by Microsoft prior to VS.NET. We have a similar problem, in that our development up to now has used the MFC collection classes, and we really don't want to mix the two at this point.
Software Zen:
delete this; -
Kevin McFarlane wrote: what do you guys think of such an attitude? Ignore it and move on.
"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown
Pretty much what I did. Also, I only worked on that paticular project for two or three weeks. :) Kevin
-
Kevin McFarlane wrote: Given that STL is a part of Standard C++ what do you guys think of such an attitude? May be, He doesn't like STL at all
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers, Alok Gupta
He didn't. Kevin
-
Unfortunately, his attitude was probably formed from the poor support for the STL provided by Microsoft prior to VS.NET. We have a similar problem, in that our development up to now has used the MFC collection classes, and we really don't want to mix the two at this point.
Software Zen:
delete this;I found VC++ 6's STL support good enough for what I wanted to do. Maybe I'm an insufficiently advanced STL user? I view these things as tools. If the MFC collection classes do what you want then use them. But if there is functionality available in STL which is not in MFC we shouldn't be afraid to use it. Especially as STL is part of Standard C++. Kevin
-
That's what I was told by my boss in my last contract, when he was looking at some of my code that used it. His view was that he wouldn't touch it with a barge pole. Given that STL is a part of Standard C++ what do you guys think of such an attitude? Kevin
I don't want to seem judgemental but he's an idiot or a C programmer who doesn't want to learn. Elaine :rose: The tigress is here :-D
-
I found VC++ 6's STL support good enough for what I wanted to do. Maybe I'm an insufficiently advanced STL user? I view these things as tools. If the MFC collection classes do what you want then use them. But if there is functionality available in STL which is not in MFC we shouldn't be afraid to use it. Especially as STL is part of Standard C++. Kevin
Kevin McFarlane wrote: I found VC++ 6's STL support good enough for what I wanted to do. same here. i never understood all the complaints about VC6's STL. Cleek | Image Toolkits | Thumbnail maker
-
I don't want to seem judgemental but he's an idiot or a C programmer who doesn't want to learn. Elaine :rose: The tigress is here :-D
He was quite a clever guy. But he did seem to have a fondness, not so much for MFC, but for "C-style" C++. Lots of low-level methods, void*s and unnecessary dynamic allocations. But as his code generally seemed to work I guess his attitude is: if it ain't broke, don't fix it. Problem is it's not very friendly to the coder who has to understand his code. Kevin
-
Kevin McFarlane wrote: I found VC++ 6's STL support good enough for what I wanted to do. same here. i never understood all the complaints about VC6's STL. Cleek | Image Toolkits | Thumbnail maker
Chris Losinger wrote: same here. i never understood all the complaints about VC6's STL For single-threaded programs it was mostly fine (unless you were passing STL containers accross DLL boundaries). However, for multithreaded it was dangerously broken, unless you applied these fixes[^] (especially the one for xtree) Yep, I discovered it the hard way :)
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
-
Nemanja Trifunovic wrote: Well, he is the boss, right? If he is ready to pay you for the extra hours you are going to spend because you can't use the Standard Library, it's all good and well. Your time is his money, right? And if they just use containers from MFC or another library instead of STL bloatware?
CP Visitor wrote: And if they just use containers from MFC or another library STL is more than just "containers", although I agree that using MFC containers is much better than raw arrays. CP Visitor wrote: STL bloatware ;P Just take some time and learn it - it is really useful, especially when enriched with Boost libraries. Although, I admit I hate its name conventions :)
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
-
Chris Losinger wrote: same here. i never understood all the complaints about VC6's STL For single-threaded programs it was mostly fine (unless you were passing STL containers accross DLL boundaries). However, for multithreaded it was dangerously broken, unless you applied these fixes[^] (especially the one for xtree) Yep, I discovered it the hard way :)
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
hmm. i knew about the deque problem. didn't know about the others. Cleek | Image Toolkits | Thumbnail maker