|
Didn't your compiler warn you about a 'possibly unintended empty statement' or something like that?
(Or have you disabled that error message?)
|
|
|
|
|
Huge legacy project 5+ million ROC - tons of warnings.
Advertise here – minimum three posts per day are guaranteed.
|
|
|
|
|
You make it sound like "Yeah, the compiler gave me a warning, but I didn't read the warning".
If that is the case: YAFIYGI
|
|
|
|
|
Sounds like You've never worked on a big project. A lot of warnings are generated from the environment, not necessarily a bad code. That's why now we have systems like SonarCloud/SonarSource. Also, as I said it wasn't my code. I happened to be the development manager in charge. If you start hunting urgent production bug with building the project and analyzing low-level warnings, this is bad news for your employers.
Advertise here – minimum three posts per day are guaranteed.
|
|
|
|
|
If you are "the development manager in charge", I am surprised that spending half a day, as you told, chasing this bug was your responsibility. But then again, I know nothing about your company.
If this really was your coworkers code, I guess he should have looked at the warning pertaining to his code. If you think that "This is a big system, so neither I as the development manager in charge, nor the developers responsible for a specific module, need to read the warnings - we'll rather complain in network forums about how nasty such bugs are", then I think you got what you deserved.
I have been working on big systems, and I have been responsible for the processing of warnings and errors, suppressing those that are considered 'noise', reporting the significant ones to the developer. I would never, ever, have classified 'Unexpected empty statement' as insignificant noise. I am not familiar with SonarCloud/SonarSource (I just checked the Wikipedia article; that is my first encounter with them). If this system is not capable of drawing your attention to unexpected empty statements, but let it drown in 'a lot of warning generated from the environment, not necessarily a bad code', then I would consider other tools.
I have been working with Coverity; it looks to me as if SonarSource is in the same business. With Coverity, you can indicate for almost any warning that 'This is noise - don't bother me with it'. But you are explicitly presented with every issue at least once, until you say 'Don't bother me with that issue any more'. You may also tell Coverity: "Never bother me with such silly details as unexpected empty statements - they're probably perfectly fine, good code!" In either case: You asked for it. You got it.
Your story does not suggest that SonarSource is a viable alternative to Coverity.
|
|
|
|
|
|
I found myself (in the old days) putting periods at the end of
COBOL comments... but that was OK.
|
|
|
|
|
Hi,
The company I work for has changed to using a secure pin over passwords as part of the Windows Hello routine.
I for one think PIN over Password is dodgy, no longer can I use B008IeS! as a password (I didn't but shipped something where I forgot to change it, whole other story!). View from the informed is this to make smart phone users happy (I am using a proper PC with a Proper Keyboard) or something else??
Glenn
|
|
|
|
|
Good news: just under where you enter the PIN there is an option to enter a password or a PIN.
|
|
|
|
|
Yes, but the change came some time ago.
|
|
|
|
|
Have they just changed the log on procedure at all or just give the password a new set of clothes?
|
|
|
|
|
It's just an extra option which makes it slightly easier to login. I'm sure I've been using it for more than a year.
|
|
|
|
|
"It's just an extra option which makes it slightly easier to hack. I'm sure I've been using it for more than a year."
FTFY.
</cynicmode>
|
|
|
|
|
Given that the PC never leaves the house, who is going to hack it?
|
|
|
|
|
|
|
I will not entertain agents of Satan.
|
|
|
|
|
Now you really pissed off the cats. They will be paying a visit…soon!
modified 13-Apr-23 19:39pm.
|
|
|
|
|
My son already has one that hates me.
|
|
|
|
|
Richard MacCutchan wrote: Given that the PC never leaves the house, who is going to hack it?
Clearly you've never been burgled.
|
|
|
|
|
|
Not at all.
But I think you might be a little more worried knowing a thief could take your PC back home and start trying to guess a 4-digit pin at a leisurely pace.
|
|
|
|
|
Well even if he did, there is nothing in there that he would find useful.
|
|
|
|
|
I see, not worried because you have nothing to hide.
Carry on your merry way, citizen!
|
|
|
|
|
If you insist on carrying the computer around the house to random places it does make it easier to walk off with it.
Now mine is locked to my desk. So they are going to need to do some sawing through metal to get to it. Does slow down the get in get out quick case.
|
|
|
|