Proc and Procedure

[Guest]

Well I noticed a few "shortcuts" when I first started Turing. Proc = Procedure, fcn = function. So I'm asking, when should one or the other be used, or does it matter? Like should proc be used when your like drawing something, or should procedure only be used when you make a formula that will be called on several occasions? Enlighten me.

[Cervantes]

They do the exact same thing. It's a matter of taste.

[codemage]

Pick your favourite one and stick with it - don't use them interchangeably.

[Guest]

Well I use both of them, like mostly proc I will use to change a major part of my program, and procedures will be called frequently in my program.

[NikG]

vahnx wrote:

Well I use both of them, like mostly proc I will use to change a major part of my program, and procedures will be called frequently in my program.

Your reason doesn't make much (if any) sense... The code is treated exactly the same whether you save proc or procedure.
Anyways, if for some reason it helps you... I guess keep it up.

[Guest]

I ment, I use 'proc' as the main procedure(s) in a program, such as towns, etc. and 'procedure' will be used to change small parts of the program. That's how I use them.

[Cervantes]

It's not entirely odd to use the two different syntaxes that do the exact same thing for different purposes. Let me give you a widespread example of this.

In Ruby, blocks are defined between do and end or between { and }. They are treated (almost) identically by the interpreter.
Some people use {} for everything, while others use do..end for everything. One convention (the one I use) uses {} for blocks on a single line, and uses do..end for multi-line blocks. Another convention (newer, gaining popularity) is to use {} for blocks that return a particular value (no side-effects) and do..end for things that modify state (have side effects).

Using two different syntaxes that do the same thing can be a good way of classifying what each section of your code is for.

[Guest]

What about if and elsif[b] versus [b]switch and case. Im not sure if switches and cases are in Turing, but you know what I mean, I think. Are those the same pretty much?

[Cervantes]

vahnx wrote:

What about if and elsif[b] versus [b]switch and case. Im not sure if switches and cases are in Turing, but you know what I mean, I think. Are those the same pretty much?

In Turing, "switch" and "case" are "case" and "label", respectively.
No, if's and switch/case/label are very different. For example, I can set up an if statement to check if x is greater than 46. Using a (Turing) case construct, this is impossible, because case constructs only compare using the = operator, not using > or any other operator.