v0.4.22 solc compile failing - not predictable behavior

Question

Error:

 Warning: Defining constructors as functions with the same name as the contract is deprecated. Use "constructor(...) { ... }" instead.
  function CappedCrowdsale(uint256 _cap) public {
  ^ (Relevant source part starts here and spans across multiple lines).
 not valid for functions.oc tag @dev
Compilation failed. See above.

I got this same exact error when my token contract was not using the new constructor() convention.

What is odd, is after I switch the token contract to the new convention, the compiler was happy. The next day it did the same thing, broke and complained about my crowdsale contract not using the new convention. (weird it didn't complain about this the day before) This was last week. I resolved the issue by switching to constructor().

Now I did a git pull on my laptop to continue work today, and now it's not happy with the constructor call made to the inherited contract, CappedCrowdsale.

function CappedCrowdsale(uint256 _cap) public { ^ (Relevant source part 
starts here and spans across multiple lines).
    not valid for functions.oc tag @dev

Googling has not turned up anything helpful. And troubleshooting on my own has not turned up any positive outcomes. I'm not 100% sure the constructor convention causing this error as it's only deprecated. But perhaps something related around that?

not valid for functions.oc tag @dev Compilation failed. See above. - leaves me clueless

Edit: I've restarted my computer and now compile doesn't give any warning about the constructor convention. Only the 1 liner error above. Last week this occurred on my desktop. Today is on my laptop.

Edit x2: Narrow down the issue to the laptop. Same code base is working without issue on my desktop. Perhaps something needs updated/reinstalled? Will update when I figure it out. The warnings are separate, nonrelated, to the compile failure.

Answer 1

@dev & @title tags need trailing characters. As stated by Ismael

Breaks: @dev

Works: @dev constructor

The odd thing I haven't figured out, yet, is the difference between both my machines. Both being Windows 10. My laptop is the that throws the error. My desktop does not.