ID:2306737
 
Resolved
BYOND Version:511
Operating System:Windows 8
Web Browser:Firefox 56.0
Applies to:DM Language
Status: Resolved

This issue has been resolved.
Descriptive Problem Summary:
Naming variable message causes compiler errors.

Since there's no mention of any inbuilt variable or proc of this name in the documentation i'm assuming this is a bug.

Numbered Steps to Reproduce Problem:

Code Snippet (if applicable) to Reproduce Problem:
/obj/test/proc/beep()
return

client/verb/test()
var/obj/test/message = new
message.beep()


Expected Results: Compiles.

Actual Results:
test.dm:9:error: message: output method has no effect here
test.dm:8:warning: message: variable defined but not used


Does the problem occur:
Every time? Or how often? Yes
In other games? Yes
In other user accounts? Yes
On other computers? Yes

When does the problem NOT occur?
Variable name is different than message.

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
Works same from 509 to 512.

Workarounds:
Change the name.

message() is a secret, undocumented proc. I suspect this is why it doesn't work as a variable name.
This is still open and I ran into it. Trying to create a message box so I'm surprised there isn't more hits here about this.
I'll have a look Monday and find out what's up.
In response to Lummox JR
Lummox JR wrote:
I'll have a look Monday and find out what's up.

Easy enough work around so low priority.
In response to PopLava
I just checked this and the code compiled just peachy in 513. I fixed a similar issue in 513.1490. Did you see this in 513 or was it 512?
In response to Lummox JR
Lummox JR wrote:
I just checked this and the code compiled just peachy in 513. I fixed a similar issue in 513.1490. Did you see this in 513 or was it 512?

512
Lummox JR resolved issue
In response to PopLava
Ah, then this has actually already been resolved.