http://www.byond.com/forum/?post=1718300
this should be fixed while looking at the ref too

I honestly don't see this thread going very far, ideally something like a mediawiki gets setup as it is FAR more manageable that a forums thread of all things

Lummox JR wrote:

Hmm. 3 examples seems like it's probably enough, though. The tag and ref forms of locate() aren't given examples either, so this would probably be overkill.

http://docs.unity3d.com/ScriptReference/Physics.Raycast.html

He's right about the many examples. I didn't know how to do a lot of things until I was shown an example. Although, being presented with params should, in most cases, be enough. With Physics.Raycast() it wasn't. This can surely be applied to some of the procedures in DM. While I think it may be good to have many examples. I do think it'd be best to keep them at minimum for procedures that aren't that hard to understand. Who needs 6 examples on how to output to the world? Things like that.

Should read

Returns:
1 if A is zero, an empty string, or null; 0 otherwise.

Kaiochao wrote:

!A is also 1 if A is "".

"" is an empty string, so Ter's change reads correct.

How about throwing something into del() in the reference that makes it clear not to rely on calling it yourself so much? Won't do much good for the existing programmers, but might help future ones avoid that annoying little pitfall.

I like your last paragraph, so I used it verbatim but with the following additional sentence before the last one:

"Objects that have no references are deleted automatically without the need for a search."

The guide also mentions that you can assign atom.icon to an object (any atom), and it'll copy that icon's icon value.

Not mentioned in the ref under icon var (atom).

I propose a change to 5 articles, and the addition of two articles:

New article: to operator

to operator

See also:
  in operator
  switch proc
  for range proc
  vars

The to operator is not a true operator. It is only meant to be used in combination with certain special patterns as a shorthand for a range of values. See the above linked reference pages for how to use the 'to' operator in each specific instance.


New article: for range proc

for range proc

See also:
  break proc
  continue proc
  do proc
  for list proc
  for loop proc
  while proc

Format:
  for(Var in [Start] to [End] [step Inc]) Statement

Args:
  Var: a variable to sequentially contain each value in the range.
  Start: the first number in the range.
  End: the last number in the range.
  Inc: default 1 if not supplied. After running Statement, change Var by Inc

First set the Var to Start, then perform the Statement. Continue performing the statement until Var is out of the range determined by Start to End. Statement may be a code block or a single statement.

step Inc may be omitted. If the step clause is omitted and Start is less than End, step will default to 1. If step is omitted and Start is less than End, the loop will not operate even once. The loop can be exited early with a goto, break, or return instruction is used to escape the loop. The statement can be prematurely terminated and the loop will move on to the next step if a continue instruction is used.

Example:

var/i
for(i in 1 to 4)
    world << i

This outputs:

1
2
3
4

Example 2:

var/i
for(i in 4 to 1 step -1)
    world << i

This outputs:

4
3
2
1

Example 3:

var/i
for(i in 1 to 10 step 2)
    world << i

This outputs:

1
3
5
7
9

Article changes:

in operator:

In addition, a value can be used to test whether a numeric value is within a range using a combination of the in and the to operator

Example:

var/x = 5
world << (x in 1 to 10) //outputs 1
x = 12
world << (x in 1 to 10) //outputs 0

for list proc

*add a see also link to the new for range proc page

for loop proc

*add a see also link to the new for range proc page

for proc

*add a see also link to the new for range proc page

vars

+add the following section

Atom variables can be assigned a restricted range of values during prototype definition. These are called variable input parameters. This will affect the possible values that can be assigned to an instance using the map editor's instance editor using the as, in, and to keywords. Any parameter specifiers that can be used in verb arguments may also be used here.

Parameter Declaration Format:

mob
    var
        money as num
        strength in 1 to 20
        alignment in list("good","neutral","evil")
        backstory as text

Any instance values entered in the map editor's instance editor menu that do not fit within the parameter ranges will be refused. This is a useful way to allow mappers to have limited control over dynamic changes to your project without having to know anything about programming and without you having to define dozens of variations of the same object by hand.

The : operator example in the ref



Doesn't compile.