>If it's that long, it needs to be refactored. Log files are a different beast and can benefit from those types of lines.

I'm talking about a .prg which holds maybe a dozen classes, already nicely cut into manageable pieces. Navigation isn't hard via Document View - it's just when going to a certain class and going down its methods, a barrier in the form of a longish comment line is a nice clue to denote "you have reached the EndDefine, if you didn't notice". There may be a couple of similar situations where this would be justified, and that's just about it. I hate to see these anywhere between a Procedure and Endproc.

>>That style may make sense in places where you have a long prg where several classes, or several groups of related routines reside. A long comment like that may help to delineate them when scrolling - though Document View makes this mostly unnecessary. I do such long lines in log files (when logging into a textfile), to point out phases, when something started or ended. Helps eyeballing. For code, I agree with your doubts.