変数について - 版の履歴

2016年8月4日 (木) 22:49にMacchkyによる

2016-08-04T22:49:31Z

2016年8月4日 (木) 21:32にMacchkyによる

2016-08-04T21:32:32Z

Macchky: ページの作成:「Category:ARMA3Category:SQF A '''variable''' is a "storage container" or "named placeholder" for data. You can read and modify the data once this container is cre...」

2016-08-04T20:58:27Z

ページの作成:「Category:ARMA3 Category:SQF A '''variable''' is a "storage container" or "named placeholder" for data. You can read and modify the data once this container is cre...」

新規ページ

[[Category:ARMA3]][[Category:SQF]]

A '''variable''' is a "storage container" or "named placeholder" for data. You can read and modify the data once this container is created.

== Requirements ==

The following links guide to the basics to understand this article:

* [[ArmA: Introduction to Scripting]]
* [[Identifier]]

== Initialization ==

The first thing you have to do is to find a name for your variable. This name is called [[identifier]]. Read the article [[Identifier]] for more information.

Once you know a name, you have to tell the game engine that you are going to use this identifier. This is called '''initialization'''. Then you may do anything with this variable.

Don't worry: This sounds more dramatic than it is. You can initialize any variable by assigning a value to it.

myVariable = 0;

Querying undefined (or uninitialized) variables returns [[nil]] (undefined value). When converted to [[String|Strings]] with [[str]], they will always return [[scalar bool array string 0xe0ffffef]] (in [[Armed Assault]]) or [[scalar bool array string 0xfcffffef]] (in [[Operation Flashpoint]]).

myString = str(undefinedVar);

myString => "scalar bool array string 0xe0ffffef"

Thus you can't really apply any [[Operators|operations]] on variables before they are initialized with a start value.

== Deletion ==

Once created, variables will take up space in your computer memory. This is not drastic for small variables, but if you use a big number of very large variables, you should undefine any variables that are not needed anymore. This can be done with the command [[nil]].

hugeVariable = nil;

This effectively destroys a variable as if it had never existed.

== Namespace ==

Variables are only visible in certain areas (namespaces) of the game. This prevents name conflicts between different variables in different [[Script (File)|scripts]].

There are three namespaces:

; local
: A variable is only visible in the [[Script (File)|script]] in which it was defined.

; global
: A variable is visible on the whole computer where it is defined.

; public
: A variable is broadcasted over the network and visible on all computers connected to the network.

=== Local Variables ===

Local variables are only visible in a specific [[Script (File)|script]]. The whole code in this script has access to the variable, that includes also [[Function|functions]] called within the script.

The [[identifier]] of variables local to a [[Script (File)|script]] always has to start with an underscore.

_myLocalVariable = 0;

In functions you should additionally mark variables as local using the command [[private]]. Otherwise you may modify local variables of the calling script that are visible in the function.

private "_myLocalVariable";
_myLocalVariable = 0;

You may also pass more [[Identifier|identifiers]] to the private command using an [[Array]].

private ["_myLocalVariable1", "_myLocalVariable2", ...];

=== Global Variables ===

Global variables are visible on the whole computer where they are defined. Names given to units in the [[Mission Editor]] are also global variables pointing to those units, which may not be redefined or modified.

[[Identifier]]s of global variables ''must not'' start with underscore. Otherwise there are the same rules as for all [[Identifier|identifiers]].

myGlobalVariable = 0;

=== Public Variables ===

Public variables are global variables that are visible on all computers in the network. You can never have true public variables, but you can emulate their behaviour.

The value of a global variable gets broadcasted over the network using [[publicVariable]]. After the call of this command the variable will have the same value on all [[Client|clients]]. Once you modify the variable though you have to broadcast it manually ''again'' with [[publicVariable]].

== Scope ==
If a local variable is initialized within a [[Control Structures]] (i.e. [[if]], [[for]], [[switch]], [[while]]) its scope will stay ''within'' this structure (i.e. outside of the structure it will still be seen as undefined). This does not apply to global or public variables.
<code>if (alive player) then {_living=true}; hint format["%1",_living];</code>
Returns "scalar bool array string 0xe0ffffef", since the local variable was not initialized ''before'' being used within a control structure.

<code>_dead=true; if (alive player) then {_dead=false}; hint format["%1",_dead];
</code>
Returns "false", since the variable was initialized before the if...then.<br>
To initialize local variables, so that they are available throughout the whole script (including any control structures), either initialize it via the [[private]] command (e.g. ''private ["_varname"];''), or by assigning a default value to it (e.g. ''varname=0;'').

== Data Types ==

Variables may store certain values. The kind of the value specifies the ''type'' of the variable. Different [[Operators|operators]] and [[:Category:Scripting Commands|commands]] require variables to be of different types.

Read the article [[Data Types]] for more information about variable types.

== Multiplayer Considerations ==

Storing vars and functions into global vars without securing them with compileFinal is a very bad practice in MP.
Basically, if you have a script installed on a server in mission file that uses functions stored in unprotected variables then hackers can overwrite that function attached to a global variable and make it execute code for everyone and do a lot of nasty stuff. So please put all of the code for each function in a SEPARATE file and initialize them like this:
<code>myGlobalVarFunction = compileFinal preprocessFileLineNumbers "Dir\where\function\is\fnc_globalVarFunction.sqf";</code>
That way, the function can be called and spawned without it being subject to hackers that attempt to overwrite the global variable "myGlobalVarFunction".

Everyone happy :)

== See also ==

* [[Data Types]], [[Magic Variables]]

[[Category: Scripting_Topics]]

@@ 9行目: / 9行目: @@
 * [https://community.bistudio.com/wiki/ArmA:_Introduction_to_Scripting ArmA: Introduction to Scripting]
-* [[識別子]]
+* [[演算子について]]
 == 初期化 ==
@@ 29行目: / 29行目: @@
 このように変数は初期化しないと、どんな [[演算子|操作]] も出来ません。
-== Deletion ==
+== 削除 ==
-Once created, variables will take up space in your computer memory. This is not drastic for small variables, but if you use a big number of very large variables, you should undefine any variables that are not needed anymore. This can be done with the command [[nil]].
+変数が作られると、あなたのPCのメモリを食います。小さい変数なら気にすることでもないですが、大量に大きな変数を使う際は必要なくなった変数を解放すべきです。これは [[nil]] コマンドを代入することで出来ます。
   hugeVariable = nil;
-This effectively destroys a variable as if it had never existed.
+== 名前空間 ==
-== Namespace ==
+変数はゲーム内の特定のエリア（名前空間）でしか見えません。これは別の [[Script (File)|scripts]] 間での名前の衝突を防ぎます。
-Variables are only visible in certain areas (namespaces) of the game. This prevents name conflicts between different variables in different [[Script (File)|scripts]].
+ARMA3には3つの名前空間が有ります
-There are three namespaces:
+; local　ローカル
-; local
+; global　グローバル
-: A variable is only visible in the [[Script (File)|script]] in which it was defined.
+: 定義されたコンピュータ内全体で見える。
-; global
+; public　パブリック
-: A variable is visible on the whole computer where it is defined.
+: ネットワークに接続された全てのコンピュータで見える。
-; public
+=== ローカル変数 ===
-=== Local Variables ===
+ローカル変数は特定の [[Script (File)|script]] 内だけで見える。そのスクリプト内のすべてのコードから変数にアクセスでき、スクリプト内から呼ばれた [[関数について|関数]] も含まれる。
-Local variables are only visible in a specific [[Script (File)|script]]. The whole code in this script has access to the variable, that includes also [[Function|functions]] called within the script.
+[[Script (File)|script]] に対してローカルな変数の [[識別子]] は常にアンダースコアからはじめなければいけません。
   _myLocalVariable = 0;
-In functions you should additionally mark variables as local using the command [[private]]. Otherwise you may modify local variables of the calling script that are visible in the function.
+関数の中では加えて [[private]] コマンドを使って変数をローカルに指定すべきです。さもないとその関数を呼んだスクリプト内のローカル変数を改変してしまうでしょう。
   private "_myLocalVariable";
   _myLocalVariable = 0;
-You may also pass more [[Identifier|identifiers]] to the private command using an [[Array]].
+[[配列]] を使って2個以上の [[識別子]] を private コマンドに入力できます。
   private ["_myLocalVariable1", "_myLocalVariable2", ...];
-=== Global Variables ===
+=== グローバル変数 ===
-Global variables are visible on the whole computer where they are defined. Names given to units in the [[Mission Editor]] are also global variables pointing to those units, which may not be redefined or modified.
+グローバル変数は定義されたコンピュータ内全体から見える変数です。ミッションエディタ内でユニットに与えた名前もまたそのユニットを示すグローバル変数となり、再定義・改変してはいけないものです。
-[[Identifier]]s of global variables ''must not'' start with underscore. Otherwise there are the same rules as for all [[Identifier|identifiers]].
+グローバル変数の [[識別子]] はアンダースコアからはじめては ''いけません''。
   myGlobalVariable = 0;
-=== Public Variables ===
+=== パブリック変数 ===
-Public variables are global variables that are visible on all computers in the network. You can never have true public variables, but you can emulate their behaviour.
+[[publicVariable]] コマンドを使うことでグローバル変数をネットワーク上に伝えることが出来ます。このコマンドを使われると変数は全ての [[クライアント]] で同じ値となります。変数を再度改変した場合は''もう一度''手動で [[publicVariable]] を使って全てのクライアントに伝えなければいけません。
-The value of a global variable gets broadcasted over the network using [[publicVariable]]. After the call of this command the variable will have the same value on all [[Client|clients]]. Once you modify the variable though you have to broadcast it manually ''again'' with [[publicVariable]].
+== スコープ ==
 <code>if (alive player) then {_living=true}; hint format["%1",_living];</code>
 Returns "scalar bool array string 0xe0ffffef", since the local variable was not initialized ''before'' being used within a control structure.
-<code>_dead=true; if (alive player) then {_dead=false}; hint format["%1",_dead];
+<code>_dead=true; if (alive player) then {_dead=false}; hint format["%1",_dead];</code>
 </code>
 Returns "false", since the variable was initialized before the if...then.<br>
 To initialize local variables, so that they are available throughout the whole script (including any control structures), either initialize it via the [[private]] command (e.g. ''private ["_varname"];''), or by assigning a default value to it (e.g. ''varname=0;'').
-== Data Types ==
+== データ型 ==
-Variables may store certain values. The kind of the value specifies the ''type'' of the variable. Different [[Operators|operators]] and [[:Category:Scripting Commands|commands]] require variables to be of different types.
+変数は特定の値を格納し、値の種類によって変数の '''型''' が決まります。[[演算子について|演算子]]やコマンドによって異なる型の変数が必要となります。
-Read the article [[Data Types]] for more information about variable types.
+詳しくは [[データ型について|データ型]] 記事参照。
-== Multiplayer Considerations ==
+== マルチプレイヤーでの留意事項 ==
 Storing vars and functions into global vars without securing them with compileFinal is a very bad practice in MP.
@@ 110行目: / 110行目: @@
 == See also ==
-* [[Data Types]], [[Magic Variables]]
+* [[データ型について|データ型]], [[Magic Variables]]
 [[Category: Scripting_Topics]]

@@ 1行目: / 1行目: @@
 [[Category:ARMA3]][[Category:SQF]]
-A '''variable''' is a "storage container" or "named placeholder" for data. You can read and modify the data once this container is created.
+'''変数''' はデータのための箱である。一度作った変数は参照したり、改変することが出来る。
-== Requirements ==
+== 前提知識 ==
-The following links guide to the basics to understand this article:
+下記のリンクはこの記事を理解するのに必要な基礎を紹介しています。
-* [[ArmA: Introduction to Scripting]]
+* [https://community.bistudio.com/wiki/ArmA:_Introduction_to_Scripting ArmA: Introduction to Scripting]
-* [[Identifier]]
+* [[識別子]]
-== Initialization ==
+== 初期化 ==
-The first thing you have to do is to find a name for your variable. This name is called [[identifier]]. Read the article [[Identifier]] for more information.
+まずはじめにあなたがしなければいけないことは、変数の名前を決めることです。この名前は [[識別子]] と言います。
-Once you know a name, you have to tell the game engine that you are going to use this identifier. This is called '''initialization'''. Then you may do anything with this variable.
+名前を決めたら、ゲームエンジンにこの識別子を使うことを知らせなければなりません。これを '''初期化''' と言います。そしたら今変数に対して何でもできるようになります。
-Don't worry: This sounds more dramatic than it is. You can initialize any variable by assigning a value to it.
+心配しないで: 大袈裟に聞こえるかもしれませんが、初期化は変数に値を割り当てるだけで出来ます。
   myVariable = 0;
-Querying undefined (or uninitialized) variables returns [[nil]] (undefined value). When converted to [[String|Strings]] with [[str]], they will always return [[scalar bool array string 0xe0ffffef]] (in [[Armed Assault]]) or [[scalar bool array string 0xfcffffef]] (in [[Operation Flashpoint]]).
+未定義もしくは初期化されていない変数にアクセスしようとすると [[nil]] を返します (未定義値)。[[str]] コマンドで 未定義な変数を [[文字列|文字列]] に変換しようとすると常に [[scalar bool array string 0xe0ffffef]] (in [[Armed Assault]]) or [[scalar bool array string 0xfcffffef]] (in [[Operation Flashpoint]]) を返します。
   myString = str(undefinedVar);
@@ 26行目: / 27行目: @@
   myString => "scalar bool array string 0xe0ffffef"
-Thus you can't really apply any [[Operators|operations]] on variables before they are initialized with a start value.
+このように変数は初期化しないと、どんな [[演算子|操作]] も出来ません。
 == Deletion ==