bad argument definition can someone help

ID:633293
 
Apr 6 2012, 4:52 am
(See the best response by DarkCampainger.)
Code:
Area
    var/area
        gringotts_exit
        diagonally_exit1

    Entered(0)

    0 << name (THe proplem here)
    return ..()
    Diagonally
    Gringotts
        gringotts_exit = .Diagonally


Problem description:

having trouble with 0 << name part
can some one help
Apr 6 2012, 5:54 am (Edited on Apr 6 2012, 6:00 am)
Why is O << name there? It should be tabbed over. And so should the next line. And why is ..() after a return?
Apr 6 2012, 6:17 am
In response to Lugia319
Lugia319 wrote:
And why is ..() after a return?

Because.
mob/Login()
    src << "Hello"
    ..()
    src << "world."

Would output:

Hello
world.

However...
mob/Login()
    src << "Hello"
    return ..()
    src << "world."

Would only output:

Hello

That's why. He doesn't particularly have a reason to do it here, but he doesn't have a reason not to either.
Apr 6 2012, 10:08 am
Doesn't seem practical for the purpose of reading to me, but I suppose we all have our tastes.
Apr 6 2012, 12:17 pm
Best response
You're using a 0 (ZERO) instead of an O (Oh?). You indentation is also a bit off.

The gringotts_exit and diagonally_exit1 variables should probably also be defined under their types, and not under the /area base type. Either that, or you could create a generic exit variable and have them all share it.
Apr 6 2012, 12:21 pm
In response to Albro1
It's more useful when you're actually overriding a process that has a default return value (ie Move() or Enter()).

. = ..() has a similar effect, but doesn't force the process to return immediately.