Справка по функциям - История изменений

Admin: /* Примечания */

2013-11-08T21:15:46Z

‎Примечания

Admin: /* Параметры */

2013-01-30T13:38:42Z

‎Параметры

Admin: /* Блок функций */

2013-01-28T20:47:22Z

‎Блок функций

Admin: /* Блок функции */

2013-01-28T20:46:40Z

‎Блок функции

Admin: /* Блок функции */

2013-01-17T15:41:05Z

‎Блок функции

Admin: /* Блок функции */

2013-01-17T15:38:51Z

‎Блок функции

Admin: /* Заголовок функции */

2013-01-17T15:26:01Z

‎Заголовок функции

Admin: /* Заголовок функции */

2013-01-17T15:15:53Z

‎Заголовок функции

Admin: /* Заголовок функции */

2013-01-17T15:15:43Z

‎Заголовок функции

Admin: /* Заголовок функции */

2013-01-17T15:14:52Z

‎Заголовок функции

@@ Строка 152: / Строка 152: @@
 </source>
-=== Примечания ===
+== Доступ к функциям из других скриптов ==
 * The nomenclature of Bethesda's functions' arguments is consistent, prefixing argument names such that their nature is easily determined. The naming convention is as follows, each prefix denoting the corresponding qualities:
@@ Строка 158: / Строка 212: @@
 : auiCount, for instance, is an unsigned integer argument while asFileName is a string argument. Note that 'p' and 'k', for Papyrus' purposes, are interchangeable and that Papyrus does not actually have pointers.
 [[Category:Скриптинг]]
 [[Category:Papyrus]]
 [[Category:Справка по языку Papyrus]]

@@ Строка 125: / Строка 125: @@
 === Параметры ===
   <параметры> ::= <параметр> (',' <параметр>)*
-  <параметр>  ::= [<identifier> '='] <выражение>
+  <параметр>  ::= [<идентификатор> '='] <выражение>
 The parameter list is a comma-separated list of expressions in the same order as the parameters are listed in the function definition. If a parameter is optional, it does not have to be passed (the default value is inserted by the compiler into the call location). You may specify parameters out of order by prefixing the expression with the identifier of the parameter (matching the name of the parameter in the definition) followed by an equals sign.

@@ Строка 71: / Строка 71: @@
 Параметры, это по сути [[Справка по переменным|переменные]], к которым функция имеет доступ для получения начальных значений, установленных пользователем.
-=== Блок функций ===
+=== Блок функции ===
   <блок функции> ::= <statement>*

@@ Строка 71: / Строка 71: @@
 Параметры, это по сути [[Справка по переменным|переменные]], к которым функция имеет доступ для получения начальных значений, установленных пользователем.
-=== Блок функции ===
+=== Блок функций ===
   <блок функции> ::= <statement>*

@@ Строка 74: / Строка 74: @@
   <блок функции> ::= <statement>*
-Блок функции содержит 0 или более [[Statement Reference|statements]]. Это выполняет основную работу функции.
+Блок функции содержит 0 или более [[Справка по инструкциям|инструкций]]. Здесь выполняется основная работа функции.
 === Примеры ===

@@ Строка 39: / Строка 39: @@
 All functions are actually resolved by the compiler to use the '''this/self''' pointer. If a script changes an integer variable '''someInt''' to 5, what it looks like to us is: '''someInt = 5'''. Internally, that variable is labeled with, and considered a component of, the object that calls it, which could be written as '''self.someInt = 5'''
-A simple example: imagine a function invoked on an object that takes a parameter that points to another object of the same class: '''car1.Ram(car2)''' (which should ram your car into another car). Obviously, the car cannot ram itself. By using the "Self" variable, we can ensure that car2 is not equal to Self and prevent damaging or unnecessary code from executing:
+Простой пример: представим себе функцию, вызываемую на объекте, который принимает параметр, указывающий на другой объект того же класса: '''car1.Ram(car2)''' (которая должна протаранить вашим автомобилем другой). Очевидно, что автомобиль не может сам себя протаранить. Используя переменную "Self", мы может быть уверены, что car2 не будет эквивалентна Self и предотвратим повреждения или выполнение ненужного кода:
 <br>
 <source lang="papyrus">
-;The function is called on one car like this.
+;Функция вызывается на одном автомобиле типа такого.
 Car1.Ram(car2)
-;Then we write the function:
+;Когда мы пишем функцию:
 function Ram(object someVehicle)
-;if someVehicle is the same as the car that the function was initially called on,
+;Если someVehicle это тот же автомобиль, на котором изначально вызывалась функция,
-;kill the function and do not proceed to ram it.
+;убиваем функцию, не позволяя автомобилю нанести себе самому повреждения.
   if(someVehicle == self)
      return
@@ Строка 57: / Строка 57: @@
 endFunction
 </source>
-<br>
+<br/>
 Another example is a script that is trying to release an object it no longer needs so that the reference no longer consumes memory. However due to the its complexities, the script may accidentally end up referencing the same object. A reference to an object that was expected to be released is called a dangling pointer, and it can cause crashes or other problems as the application progresses. By comparing newObject to Self (''if(newObject != Self)''), we can be sure that when the old object is released it will be properly replaced by newObject.

@@ Строка 33: / Строка 33: @@
 Here, let's pretend that you are trying to change an object crucial to your application and you want to release the old one because you're a good memory citizen who cares about his users and their limited memory resources. So, you want to first release the old object and then set the pointer to the new one, right? But what if a nasty scenario occurs where you replace the object with itself? You release the old object, set the pointer to the memory address of the "new" object (which is, actually, the old object), try to dereference it (a fancy word for "use it") and boom - a wild unicorn appears and destroys your application '''if you're lucky'''. Usually, the memory is just cleared to be overwritten, the system might not use it immediately, therefore, in some cases - your application could work and make your life miserable by reports of crashing. You made a dangling pointer which references an object that was released (by you, a moment ago). Do you, perhaps, see how you could solve this? Yes, exactly. If newObject is NOT equal to Self (newObject != Self), then release the object referenced by Self and change the Self pointer/variable to point to newObject (Self = newObject). And you've solved all of your life's troubles. Kittens are purring. Birds are singing. And gamers are cursing at the dragon that killed them because your game or mod is awesome.
 -->
 Переменная "self" является естественным следствием объектно-ориентированного программирования. Объектно-ориентированное программирование опирается на понятие абстрактного класса и экземпляра этого класса (экземпляр можно также назвать объектом.)

@@ Строка 25: / Строка 25: @@
 |-
 |style="border-style: solid; border-width: 0"|[[Image:InDepth.jpg|48px]]
-|style="border-style: solid; border-width: 0"|Если вам стало интересно что за такая переменная "Self", то можно сказать что она унаследована из объектно-ориентированного программирования, и наследуется, как и все остальные понятия класса и экземпляры класса, которые так же называются объектами. Типичным примером для объяснения связи класса(class)/экземпляра(instance) можно назвать различие между чертежом автомобиля и реальным автомобилем, который был сделан по этому чертежу. У вас может быть куча машин на базе одного чертежа. For anything useful, you can't know all the cars that are going to be created from your blueprint, поэтому вам нужен метод определения относительно того, какой автомобиль имеет некоторые функция, которые были вызваны/используются. To be direct, you can't turn on the radio of a blueprint, it's a piece of paper. But you can do it in a real car, made from the blueprint. One might tune in to a hard rock station. And another car could tune to a station that plays Rebecca Black's song "Friday" all day. Now, Replace the word "blueprint" with "class" and "car" with "instance/object" in your head. That difference is crucial, capture it. The way you find out which object is being possibly modified by a function is by silently pushing in an additional hidden parameter to a function which contains the memory address of the "victim" object, of the logical name "Self". In some languages, '''self''' is called '''this'''.
+|style="border-style: solid; border-width: 0"|<!--Если вам стало интересно что за такая переменная "Self", то можно сказать что она унаследована из объектно-ориентированного программирования, и наследуется, как и все остальные понятия класса и экземпляры класса, которые так же называются объектами. Типичным примером для объяснения связи класса(class)/экземпляра(instance) можно назвать различие между чертежом автомобиля и реальным автомобилем, который был сделан по этому чертежу. У вас может быть куча машин на базе одного чертежа. For anything useful, you can't know all the cars that are going to be created from your blueprint, поэтому вам нужен метод определения относительно того, какой автомобиль имеет некоторые функция, которые были вызваны/используются. To be direct, you can't turn on the radio of a blueprint, it's a piece of paper. But you can do it in a real car, made from the blueprint. One might tune in to a hard rock station. And another car could tune to a station that plays Rebecca Black's song "Friday" all day. Now, Replace the word "blueprint" with "class" and "car" with "instance/object" in your head. That difference is crucial, capture it. The way you find out which object is being possibly modified by a function is by silently pushing in an additional hidden parameter to a function which contains the memory address of the "victim" object, of the logical name "Self". In some languages, '''self''' is called '''this'''.
 On a serious note, one could ask: "'''Why should I ever want to use this "Self" variable when I can simply change any variable I want directly? I know they exist in the blueprint, therefore they are also in the instance. That's the whole point, is it not?'''" Sort of, young samurai. But not really, everything you do actually is resolved by the compiler to use the '''this/self''' pointer. If you change an integer member variable '''something''' to 5, what you do is: "'''something = 5;'''". What actually happens internally is "'''self->something = 5;'''". '''Self''' is your silent guardian, a watchful protector... A dark knight.
@@ Строка 31: / Строка 31: @@
 Here's just a simple taste from general programming which includes '''Self''''s explicit usage, imagine that you've got a function invoked on an object (sometimes called a '''non-static member function/method''' or perhaps an '''instance-level member function/method''') that takes a parameter that points to an object of the same class. And you want to make sure you're not being fed the very object the function has been invoked upon. That mouthful is referred to as "self-reference". With "Self", you can check whether pObject is equal to Self and prevent damaging or unnecessary code from executing. If you can't think of a useful application of this example, it comes in handy with dynamic memory management and functions called setters.
 Here, let's pretend that you are trying to change an object crucial to your application and you want to release the old one because you're a good memory citizen who cares about his users and their limited memory resources. So, you want to first release the old object and then set the pointer to the new one, right? But what if a nasty scenario occurs where you replace the object with itself? You release the old object, set the pointer to the memory address of the "new" object (which is, actually, the old object), try to dereference it (a fancy word for "use it") and boom - a wild unicorn appears and destroys your application '''if you're lucky'''. Usually, the memory is just cleared to be overwritten, the system might not use it immediately, therefore, in some cases - your application could work and make your life miserable by reports of crashing. You made a dangling pointer which references an object that was released (by you, a moment ago). Do you, perhaps, see how you could solve this? Yes, exactly. If newObject is NOT equal to Self (newObject != Self), then release the object referenced by Self and change the Self pointer/variable to point to newObject (Self = newObject). And you've solved all of your life's troubles. Kittens are purring. Birds are singing. And gamers are cursing at the dragon that killed them because your game or mod is awesome.

@@ Строка 39: / Строка 39: @@
-The "self" variable is a natural consequence of object oriented programming. Object oriented programming relies on the concept of an abstract ''class'' and an ''instance'' of that class (An instance may also be called an ''object''.)
+Связь между классом и экземпляром похожа на разницу между чертежом автомобиля и реальным автомобилем, который сделан по этому чертежу. Всего лишь один чертеж может являться базой для множества автомобилей. Чертеж - это и есть абстракция. Вы не можете взаимодействовать с ним. Например, вы не можете включить радио автомобиля на чертеже. Это кусок бумаги, не более. Для того, чтобы включить радио, вам нужно взаимодействовать с реальным автомобилем. Чертеж - это класс, а автомобиль - это объект. The way you find out which object is being acted upon by a function is to refer to the self. Например, ''self.TurnOn(theRadio)'' включит радио у автомобиля, который вызвал функцию, и при этом, только у одного этого автомобиля.
-−
-The relationship between a class and an instance is similar to the difference between a blueprint of a car and the actual car that is made from that blueprint. A single blueprint may be the basis for many cars. The blueprint is an abstraction. You cannot interact act with it. For example, you can't turn on the radio of the car in the blueprint. It's a piece of paper. In order to turn on the radio, you need to interact with the actual car. The blueprint is the class, and the car is the object. The way you find out which object is being acted upon by a function is to refer to the self. For example, ''self.TurnOn(theRadio)'' will turn on the radio of the car that calls that function, and only that one car.
 All functions are actually resolved by the compiler to use the '''this/self''' pointer. If a script changes an integer variable '''someInt''' to 5, what it looks like to us is: '''someInt = 5'''. Internally, that variable is labeled with, and considered a component of, the object that calls it, which could be written as '''self.someInt = 5'''