In response to Lummox JR
I usually put debug messages all over my code when I get a runtime. I output the procedure name, all arguments to the procedure, and at which half of the procedure it failed.

I can tell where it failed because it will spit a runtime before the first or final debug message is located is outputted. Sometimes it takes a while to find the bug, but I usually do.

It's really simple and easy, not to mention a great way to deal with runtimes on BYOND. I've never used it on any other language, so I don't know how useful it would be, but I bet it would be just as effective.
In response to CaptFalcon33035
It's called printf() debugging (when done in C, at least), and yes it's pretty effective. It's a lot more time-consuming than using a proper debugger facility though. (i.e. one that allows you to step through a program, automatically pause on errors, and investigate the current state of the system [variable values and so forth] at any time while execution is paused.)

Speaking of which, how about a proper debugger for BYOND, Lummox? ;-)
In response to Lummox JR
Lummox JR wrote:
Wait, it's extraneous, but not to the point of irrelevance? So it's only mostly extraneous,

(Hedgemistress is not among them, FYI)

Yes, I know. Perhaps we haven't "met" before, but I've read a few of her posts before.

I have a reputation of being "a little slow"... so, let me just test my understandin of your thinking here

No problem. I went slightly in-depth for you, tell me if you understand it now.

"They don't have sarcasm on Betelgeuse, and Ford Prefect often failed to notice it unless he was concentrating."

Yes, true. You've kind of failed to notice my reply there was also sarcastic, I'm afraid.

This turned out to be a lot easier than I thought to implement. As of BYOND 4.0, type mismatch and undefined operation errors will show their arguments, to clarify how the error occurred.

Ah, nice. As kinda implied before, too bad its only in 4.0 though. Mind telling 'right around' what corner is it, lol? Looks like some corner in the distant reaches of space.
In response to Kaioken
Kaioken wrote:
I have a reputation of being "a little slow"... so, let me just test my understandin of your thinking here

No problem. I went slightly in-depth for you, tell me if you understand it now.

"They don't have sarcasm on Betelgeuse, and Ford Prefect often failed to notice it unless he was concentrating."

Yes, true. You've kind of failed to notice my reply there was also sarcastic, I'm afraid.

Sarcasm is difficult to get across in a text environment, but it looks like you didn't manage to convey it at all. It came off as condescension, perhaps because a lot of your other posts have had the same tone.

Lummox JR
In response to Hedgemistress
'Dammit Tom, I'm a programmer, not a doctor!'
In response to Lummox JR
Lummox JR wrote:
Nope. BYOND has no such facility for strict-typing a list. It'd require radical redesign of the language.

Until you realize that this would turn out much easier than previously thought, and you come to be a miracle worker. ;P

Hiead
In response to Hiead
Hiead wrote:
Lummox JR wrote:
Nope. BYOND has no such facility for strict-typing a list. It'd require radical redesign of the language.

Until you realize that this would turn out much easier than previously thought, and you come to be a miracle worker. ;P

Eh, changing an error message was gonna be laborious at worst. What PirateHead is asking for would change the very nature of the language. He's trying to get strict-typing features into a loosely-typed language, which is simply impossible.

Lummox JR
In response to Lummox JR
He's trying to get strict-typing features into a loosely-typed language, which is simply impossible.

Impossible... or the winning combination for a zany, Perfect Strangers meets The Odd Couple sitcom?
Page: 1 2