|
Nishant Sivakumar wrote: For .NET, are you still using the 2003 MC++ syntax?
Still on 2003 MC++ syntax. The reason is that we are getting rid of .NET alltogether and it just doesn't make sense to upgrade it at this point. Maybe if MS finally releases mscfront, I take a day or two and upgrade it.
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
|
|
|
|
|
Nemanja Trifunovic wrote: The reason is that we are getting rid of .NET alltogether
Hmmmm, interesting. I haven't heard anyone else say that
Regards,
Nish
|
|
|
|
|
Nishant Sivakumar wrote: Hmmmm, interesting. I haven't heard anyone else say that
It simply did not work for us. .NET is a platform for data-centric business applications, but we are developing natural language processing software. It turned out that 90% of core work still needs to be done by native C++ code, and adding .NET on top of that makes little sense. Also, Linux has become a very important target platform, and Mono is too risky to rely on at this stage.
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
|
|
|
|
|
Ah ok. That makes sense.
Regards,
Nish
|
|
|
|
|
We have about 60 clients running our software on about 50,000 machines. At user group meetings, it has been made very clear to us that anything other than native code is completely unnaccetable to them. It isn't all that long since the last Windows v3.1 machine was removed from the list. We know there are still a lot of Win98 around, and I suspect (with some supporting evidence) that there are Win95 systems around, but not admitted to.
We asked, "What if you all ran XP?". Answers were the same, no CLI. A reasonable percentage said that they'd rather we produce a Linux solution than go down that route. Though I don't see that happening any time soon.
Rob in the West Riding
|
|
|
|
|
|
Michael P Butler wrote: My last remaining C++ product is maintenance only, and that is done using VC6.
We are not all independent consultants, Michael. Some of us can't just choose to do what we think is exciting!
Regards,
Nish
|
|
|
|
|
Nishant Sivakumar wrote: We are not all independent consultants, Michael. Some of us can't just choose to do what we think is exciting!
If I wanted exciting, I'd be still coding in C++. I miss the excitement of tracking down that missing delete
I choose the best tool to do the job. C#, just happens to be the best tool for writing my business apps.
If I was still doing major telephony work, I'd be using C++. (VS 2003 is the last version I used for my telephony apps, although I used to use VC6 to create the initial COM object because ATL was so much simpler in those days)
Michael
CP Blog [^] Development Blog [^]
|
|
|
|
|
Michael P Butler wrote: I miss the excitement of tracking down that missing delete
Oh man.. then you should witness the ACTION when you use an already deleted pointer, a.k.a dangling SOB. Everytime that happens, I put on the party hat and celebrate with my office mates.
|
|
|
|
|
Visual Studio 6 is still the best with Visual Assist and WndTabs
#define __ARMEN_H__
|
|
|
|
|
Compilation and standard compliance sucks. Try using the boost library and you are screwed.
well it works.. but it is dog slow.
and the STL ist pretty basic (means pretty bad) too.
Are the newer Visual Studio versions faster ?
[Mine uses jsut 256 MB of rams, altough I've got 1GB, so compilation time really sucks. And those freakin Internal Compiler errors when using boost library].
Well.. thanks for venting.
WndTabs rock.
All the label says is that this stuff contains chemicals "... known to the State of California to cause cancer in rats and low-income test subjects." Roger Wright http://www.codeproject.com/lounge.asp?select=965687&exp=5&fr=1#xx965687xx
-- modified at 5:04 Monday 30th January, 2006
|
|
|
|
|
I am also stuck for some projects using the good old Visual Studio 6.
And I also use boost a lot. But no problems there.
And for the STL thing: Use stlport (www.stlport.org[^])
|
|
|
|
|
Odd. I always had the problem with internal compiler errors, when using the tokenizer library, for example.
Rebuilding the project and the internal compiler errors went away (sometimes).
But then I used the project from codeproject (which was the basic version what became the tokenizer lib), and this works fine.
Well I know stlport, but FOR me the stl - library of VC6 is doing fine (altough I'd prefer a more complete version)
My biggest gripe is that I have got a new machine with 1 GB of ram and VC6 still didn't get really faster. (the more templates the worse).
And I wanted to know if the newer Visual studios are faster when compiling.
All the label says is that this stuff contains chemicals "... known to the State of California to cause cancer in rats and low-income test subjects." Roger Wright http://www.codeproject.com/lounge.asp?select=965687&exp=5&fr=1#xx965687xx
-- modified at 5:34 Monday 30th January, 2006
|
|
|
|
|
Boost is a real pain to get working but parts of it do work with vc6...
For STL. I have been using stlport for many years and it works great. Besides having a more complete stl the debug iterators really help debugging by throwing execptions when you do something wrong with an iterator. This feature alone has saved me many days debugging time...
John
|
|
|
|
|
Despite of VisualAssist (it really rocks!) the new 2005 IDE is the multitool you have to own.
Newer used 2002 oder 2003? The its definitivly the best choice. Better debugging support. Better what ever you want! So what is the valuable add vc6 owns?
Live is to short to be angered about lost chances!
|
|
|
|
|
VS6 IDE is lean and fast, but the compiler is way out of date.
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
|
|
|
|
|
Nemanja Trifunovic wrote: VS6 IDE is lean and fast, but the compiler is way out of date.
Yep, exactly!
Regards,
Nish
|
|
|
|
|
The IDE is fast until you load a large workspace (say about 80 projects). Then it really, really struggles - or crashes entirely.
Anna
Currently working mostly on: Visual Lint
Anna's Place | Tears and Laughter
"Be yourself - not what others think you should be"
- Marcia Graesch
"Anna's just a sexy-looking lesbian tart"
- A friend, trying to wind me up. It didn't work.
|
|
|
|
|
You are only thinking of the IDE. The VC++ 6 compiler sucks!!!
Regards,
Nish
|
|
|
|
|
Agreed there too. I can not believe that the highest processor supported in vc6 (without a processor pack which breaks many applications) is the Pentium Pro.
John
-- modified at 9:41 Monday 30th January, 2006
|
|
|
|
|
John M. Drescher wrote: I can not believe that the highest processor supported in vc6
What do you mean by "supported?" Are you saying that it is luck/coincidence that it works with P2, P3, and P4?
"The greatest good you can do for another is not just to share your riches but to reveal to him his own." - Benjamin Disraeli
|
|
|
|
|
There is no support or optimization for anything > than pentium pro. No mmx, sse ...
John
|
|
|
|
|
Ahh, that stuff. I can only guess that since VS6 came out around a year after the release of the Pentium 2, MMX support could not have been included without pushing a bunch of dates back, and since SSE did not come out until almost two years later with the Pentium 3, it could not have been included either. I imagine that Visual Studio Service Packs were not intended to include processor-specific instruction sets.
"The greatest good you can do for another is not just to share your riches but to reveal to him his own." - Benjamin Disraeli
|
|
|
|
|
That's NOT about the IDE. that's the fault of the compiler. Let's stay within context here.
------- sig starts
"I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
But we can leave it at that.
John
-- modified at 12:20 Friday 3rd February, 2006
|
|
|
|