oview(x,ref) still returning ref at null loc

ID:2273994
 
Jul 25 2017, 9:48 pm
Resolved
Calling oview() from a null location included the reference object.
BYOND Version:511
Operating System:Windows 7 Ultimate 64-bit
Web Browser:Chrome 59.0.3071.115
Applies to:Dream Daemon
Status: Resolved (512.1386)
This issue has been resolved.
Descriptive Problem Summary:

client
    verb
        test()
            mob.loc = null
            if(mob in oview(1,mob))
                src << "This shouldn't show."
            mob.loc = locate(1,1,1)
            if(!(mob in oview(1,mob)))
                src << "This should show."


This was reported fixed in 511.1377, but to my knowledge it was never fixed.
Jul 26 2017, 8:47 am
Huh. I distinctly remember looking into that and fixing it, but I'll give it another look.
Sep 5 2017, 1:32 pm
Apologies for the delay in getting back to this. I took a look and the results I'm getting are indeed correct.
Sep 5 2017, 1:38 pm
...Correct as in the bug report is accurate, or correct as in the bug report is inaccurate?
Sep 5 2017, 9:26 pm
Urgh, my bad. I had a massive brainfart earlier and somehow just didn't at all process the semantics of "this shouldn't show". It was that kind of day.

I can confirm there's a bug here. I'll look into it further.
Sep 6 2017, 12:13 pm
Found the problem. This actually relates to a fix that was done for view() when the loc was null, but it didn't take the exclusion of oview() into account.
Sep 25 2017, 11:23 am
Lummox JR resolved issue with message:
Calling oview() from a null location included the reference object.