FixInsight 2017.04 is finally there! :)
FixInsight 2017.04 is finally there! :)
What's new:
New rule: O805 Inline marked routine comes after its call in the same unit
New rule: O804 Method parameter is declared but never used
Delphi 10.2 Tokyo support
Improved : Code parser
Fixed false positives in some cases
http://www.tmssoftware.com/site/fixinsight.asp
What's new:
New rule: O805 Inline marked routine comes after its call in the same unit
New rule: O804 Method parameter is declared but never used
Delphi 10.2 Tokyo support
Improved : Code parser
Fixed false positives in some cases
http://www.tmssoftware.com/site/fixinsight.asp
How about this issue? tmssoftware.com - TMS Software I reported it a while ago, both to forum and support, it makes it unusable if parser fails
ReplyDelete/sub
ReplyDeleteCan't login on TMS site :( Login and code correct, no error message at login - but not login...
ReplyDeleteI have same issue on TMS site, but if you download and install trial version it should use your existing license
ReplyDeletePlease try to clear the cache and try again. We have recently fixed a related issue but clearing cache is needed.
ReplyDeleteEugene Kotlyarov this should be fixed in the latest build. Please download and reinstall the latest version again.
ReplyDeleteRoman Yankovsky thank you it works now!
ReplyDeleteJust tried to download but it sent me old version 2016.09
ReplyDeleteStill no path exclusions feature? I'd really like to buy FixInsight, however I won't be til it has this feature
ReplyDeleteRussell Peters Richard Baroniunas I can't reproduce this.. I've asked TMS to double check.
ReplyDeleteIn "Latest available release" - 2017.04 (Wednesday, April 19, 2017), all ok. But in download section - only sep-2016 version too :(
ReplyDeleteДенис Мартьянов Should have said earlier, my problem was that I logged in with the old password instead of the new one.
ReplyDeleteDownloads should be fixed now
ReplyDeleteRoman Yankovsky
ReplyDeleteWe have some issues with latest FixInsight. First of all it revealed tons of proper issues, those should be fixed now.
Problems are following ignoring the cases we are OK with.
O804 is very picky of the placement. Would be cool and way better syntactically if that ignore could also be after procedure/function line (Before var/cost/nested methods.) Also defining actually what is OK and What is not, would be very cool. Like:
function Foo(const ACompanyId, AUserId : Integer; const AName:; string;): Ingeger;
//FI:O804('AUserId ', 'AName')
So ACompanyId would always be needed, but other two in some situations would be totally OK to not to be used.
Biggest problem is ignoring the O803
O803 ignoring does not work always. We have at least 100 constants ignored because they are in common unit, but not all projects use it. and ifdeffing them out would be too much work. If we ignore them they still get complained about. But not systematically (I think, I have no proof that will this actually be so)
(Asked this from TMS support but have not heard from them so I'll try from here.)
Tommi Prami replied in email
ReplyDeleteThanks for reply, hope we can get HotFix soon :)
ReplyDeleteRoman Yankovsky Any idea on update schedule?
ReplyDelete