The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
1. The lounge is for the CodeProject community to discuss things of interest to the community, and as a place for the whole community to participate. It is, first and foremost, a respectful meeting and discussion area for those wishing to discuss the life of a Software developer.
The #1 rule is: Be respectful of others, of the site, and of the community as a whole.
2. Technical discussions are welcome, but if you need specific programming question answered please use Quick Answers[^], or to discussion your programming problem in depth use the programming forums[^]. We encourage technical discussion, but this is a general discussion forum, not a programming Q&A forum. Posts will be moved or deleted if they fit better elsewhere.
4. No politics (including enviro-politics[^]), no sex, no religion. This is a community for software development. There are plenty of other sites that are far more appropriate for these discussions. Or if you must, use the Back Room[^] - but enter at your own risk.
5. Nothing Not Safe For Work, nothing you would not want your wife/husband, your girlfriend/boyfriend, your mother or your kid sister seeing on your screen. For those discussions where you wish to be a little more frank, use the Soapbox[^]
6. Any personal attacks, any spam, any advertising, any trolling, or any abuse of the rules will result in your account being removed.
7. Not everyone's first language is English. Be understanding.
Please respect the community and respect each other. We are of many cultures so remember that. Don't assume others understand you are joking, don't belittle anyone for taking offense or being thin skinned.
We are a community for software developers. Leave the egos at the door.
Hi there we want to debug GASChedule. But it not starting on visual studio 2015. we got some errors. This errors are: "Error C2338 <hash_map> is deprecated and will be REMOVED. Please use <unordered_map>. You can define _SILENCE_STDEXT_HASH_DEPRECATION_WARNINGS to acknowledge that you have received this warning. GenetikAlgoritma c:\program files (x86)\microsoft visual studio 14.0\vc\include\hash_map 17"
"Error C2664 'BOOL CFont::CreateFontW(int,int,int,int,int,BYTE,BYTE,BYTE,BYTE,BYTE,BYTE,BYTE,BYTE,LPCTSTR)': cannot convert argument 14 from 'const char ' to 'LPCTSTR' GenetikAlgoritma c:\users\özge\documents\visual studio 2015\projects\genetikalgoritma\genetikalgoritma\childview.cpp 115"
"Error C2664 'void ATL::CStringT<wchar_t,StrTraitMFC_DLL<wchar_t,ATL::ChTraitsCRT<wchar_t>>>::Format(UINT,...)': cannot convert argument 1 from 'const char ' to 'const wchar_t *' GenetikAlgoritma c:\users\özge\documents\visual studio 2015\projects\genetikalgoritma\genetikalgoritma\childview.cpp 163"
Well I'm not surprised you are having problem working with software you can't even read the hihlighted text at the top of the page, read it now and you may understand why you are not going to get a positive response from to this question in this forum.
Try Visual Studio Discussion Boards[^]. You probably won't get much of a response there because these issues look lik very specific problem with GASchedule. Try telling us a little more like what is GASchedule for a start.
Never underestimate the power of human stupidity
Looks like you have some code written for a previous version of C++ (C++0x) and now you want to compile it with more modern C++ (C++11 or C++17). Try the C++ forums.
#SupportHeForShe Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
Please to place mental litter generated while reading off-topic posts in appropriate waste container.
«There is a spectrum, from "clearly desirable behaviour," to "possibly dodgy behavior that still makes some sense," to "clearly undesirable behavior." We try to make the latter into warnings or, better, errors. But stuff that is in the middle category you don’t want to restrict unless there is a clear way to work around it.» Eric Lippert, May 14, 2008
He posted in the wrong forum for sure but that's rude and in violation of rule #1 and #6 of this very forum. He obviously has an issue. To post this 10 hours after the initial post and 9 hours after he re-posted in the appropriate section after being told to is uncouth.
I had a C++/CLI project I had to migrate from VS2013 to VS2015 that wouldn't compile in VS2015. I had to manually edit the .csproj file because of nuances between the two versions. I'm not saying it's not his fault but to assume that incurs the assumption you've never run into the same situation.
I think the issue has more to do with the character encoding used. He's attempting to assign an 8-bit encoding to a 16-bit value (char to wchar_t). Any non-character-encoding expert has probably run into the same problem before - I know I have. The base Windows types don't have very descriptive names so often I have to look up what they mean. Personally, I've never dealt with an LPCTSTR before only LPCSTR and LPTSTR.
It's a problem if you don't even understand the basic premise of why that encoding is different. I've said it in the past - programming is an infinitely complex topic in which no one, and I mean NO ONE, has a full grasp. Lifetimes of work can be encapsulated in a single topic.
Just cast them and all will be well.
That's an easy statement to say when you're familiar with the topic being discussed. That's an entirely different monster when you have no character encoding experience or experience with Windows types. You even mention the fact that wchar_t is a header definition for an unsigned short in your response. How many average coders do you really expect to have read the header file for wchar.h or its equivalent? wchar_t isn't even universally accepted and the char32_t standard was implemented in 2011 to deal with that issue.
Assuming the basic types are fundamentally correct, else it would have crashed anyway, all it needs is a cast. And it meerely takes a minute or two to read up the types if you are in doubt. Posting a question to a forum is lazy, and NOT the behaviour of an engineer.
Off-by-one errors, as the simplest form of error in possibly computing history, would like to have a word with you. Sometimes being blind to your own code or simply being ignorant of the context of your code is a fatal mistake. It is in this time of need that developers turn to their peers. Not to be berated but to be educated.
Being too lazy to do your own research IS an indication of a bad engineer.
It is only when you have researched and boiled a problem down to a single, distinct question, that you seek the help of senior engineers. If I hadn't done that in my early days I would have got a roasting, and rightfully so!
Okay, one part for my supercharger project came in the mail yesterday. Not quite a flood, but, exciting nonetheless.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 - You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 - When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
Ignore me, I'm commiserating - Canada Post won't even put something as small as a CD in my mailbox and makes me drive a few miles to go pick up packages that would clearly fit in it (and that's my first world problem of the day)...
Okay, so I'm working with a team that's (relatively) young and like to do things "the right way". This means Agile (naturally!), unit tests written up front, acceptance tests (Gherkin) too..
The problem is that very little gets delivered. In the last two week sprint, 160 points were promised but only 40 delivered. Same in the previous sprint. There's a bit of worry as they're working on a mission critical project that needs to be delivered in a couple of months.
Personally, I think they're missing one major point mentioned in the Agile manifesto, in that..
We are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
We're ending up with the situation that writing tests and refactoring is taking the bulk of the time. Things are being (IMO) over-tested and (also IMO) and there's an over-reliance on unit/acceptance testing to pick up all defects - real bugs are being missed and picked up at the point of actual system testing (or even worse, demo).
On top of that, we've got developers going in changing working code simply because they think it should be done differently (in their opinion, better). And, if there's a complex way to write simple code you can bet this team will find it..
Has anyone else run into this? What was done to get the team focused on the important deliverables? I would like to understand how we can get away from delivering tests but very little product every two weeks..
Ah, I see you have the machine that goes ping. This is my favorite. You see we lease it back from the company we sold it to and that way it comes under the monthly current budget and not the capital account.
Agile - an MBA's idea of how programming should be done.
It's too bad it has descended into that. I often talk about he _heart_ of Agile as it is defined by one of the two original "creators" of the Agile methodology in the following book: Scrum: The Art of Doing Twice the Work in Half the Time[^] It's really a great read and if you were to read it I believe you'd find, as I did, that Agile is a set of processes pulled together into a methodology that explains how real work is done.
But, alas, it is described in so many places so poorly.
No, not just because Agile says so. I'm saying that code without a purpose isn't valuable to a company or a project. Developers often get stuck on code, but if the code isn't useful or usable the product suffers. Often, it is because developers are focused on other things like some beautiful algorithm. I like software that works and that is really the true goal of a real Agile project. Even this process that the OP has described isn't actually Agile, because they are missing a prime ingredient: product owner / visionary. Alas.