Proper Code Format for Script Combiner

[mikembm]

For those of you releasing codes please follow these guidelines so those who use my script combiner can also use your code with it.

The full procedure/function line
The var statement if necessary, followed by the variables
The begin statement followed by the main code
The end; statement

For the built-in functions that have a return statement, only include a return statement if you are changing it's value in your script.

The only comments that will not get stripped out are single line comments using '//' in the begin section of a procedure
Lastly, comment type syntax cannot be used in strings. (myString := '//hello') Comments count as: //comment, (* comment *), and { comment }

[deguix]

Well... where's it btw? No links here.

(Shouldn't this go to the "How to properly combine scripts" topic in the Scripting Discussions and Help forum?)

[EnEsCe]

Yup doesn't belong in this forum. I think hes trying to get a sticky... but no.



LOOKING FOR THE WORD SUPERNATURAL COMB ? WELL ITS GONE! ALL YOUR HINT ARE BELONG TO ME!

[chrisgbk]

For functions that have a return statement in the template, do not include that as part of your code.

This is asking too much; those lines are needed, and not everyone is going to use the script combiner. Either fix the script combiner, or add a note so people can manually fix scripts as needed.

Remember, some scripts may modify the return value; leaving it out in that case will not result in the desired behaviour.

Unless there is a good reason not to, I'm going to end up merging this with the other thread; tools of the community should not dictate formatting of others work without good reason, of which working around problems with a tool is not one of those reasons.

[spkka]

agreed, i really like the idea but it should work for all scripts... Mine bugged when i tried combining something so i didn´t

fix the code a lot of new scripters will like the combiner i think..
cheers spkka

[FliesLikeABrick]

This information really should have been posted in the script combiner thread, not a separate one.

[mikembm]

For functions that have a return statement in the template, do not include that as part of your code.

This is asking too much; those lines are needed, and not everyone is going to use the script combiner. Either fix the script combiner, or add a note so people can manually fix scripts as needed.

Remember, some scripts may modify the return value; leaving it out in that case will not result in the desired behaviour.

Unless there is a good reason not to, I'm going to end up merging this with the other thread; tools of the community should not dictate formatting of others work without good reason, of which working around problems with a tool is not one of those reasons.

No you misunderstood. When you download the server and get the default code all the functions have a return line in them like Result := State or whatever. And I have seen some people include those in their script. But if you do that it will just double up on that line. You can of cource include wahtever return statements you want. I'm just saying dont include the ones that are already there to begin with.

[chrisgbk]

For functions that have a return statement in the template, do not include that as part of your code.

This is asking too much; those lines are needed, and not everyone is going to use the script combiner. Either fix the script combiner, or add a note so people can manually fix scripts as needed.

Remember, some scripts may modify the return value; leaving it out in that case will not result in the desired behaviour.

Unless there is a good reason not to, I'm going to end up merging this with the other thread; tools of the community should not dictate formatting of others work without good reason, of which working around problems with a tool is not one of those reasons.

No you misunderstood. When you download the server and get the default code all the functions have a return line in them like Result := State or whatever. And I have seen some people include those in their script. But if you do that it will just double up on that line. You can of cource include wahtever return statements you want. I'm just saying dont include the ones that are already there to begin with.

The point still stands, that someone who does it manually would then be left in the dark. The entire working script should always be included, not segments that work if you use a certain tool to combine them.