You can see several differences above in the declaration of memory variables.
在上面的内存变量声明中可以看到几点差异。
Modules can be unloaded if needed which removes all the code and variables from memory.
如果需要的话，可以卸载模块来除去内存中所有的代码和变量。
This also helps to reduce memory usage, since the type information represents variables in native machine representation.
这还有助于减少内存使用量，因为类型信息以本机机器表示法表示变量。
Rather than sharing variables in memory, the mailbox effectively separates distinct processes from each other.
邮箱有效地将各个进程彼此分开，而不用共享内存中的变量。
It also leads me nicely to the last new features of the memory manager: environment variables.
它还精心地引导我使用内存管理器的最后几个新功能：环境变量。
Specifically, how an object stores its instance variables in memory.
特别是对象如何在内存中存储其实例变量。
Remember that error-checking only happens during marshalling -- this means that erroneous data can be floating around in these member variables while they are in memory, awaiting marshalling.
要知道错误检查只有在编组时进行，这意味着只要还在内存中，错误数据就可以自由地存在于这些成员变量之中等待编组。
Variables such as memory, intelligence, or mood are hard to define and even harder to measure.
很难定义，甚至更难测量一些可变因素，如记忆力、智力和情绪。
Note that you use your previously initialized variables along with a fourth parameter that indicates the GFP mask for memory initialization.
请注意使用了先前初始化的变量以及指示用于内存初始化的GFP屏蔽第四个参数。
The CLR JIT can only track a fixed number of variables for register allocation; once it has to track more than this, it begins to spill the contents of registers into memory.
CLRJIT只能跟踪固定数目的寄存器分配变量；一旦需要跟踪的数目超出这个数目，它就开始将寄存器的内容移到内存中。
After defining variables and checking to see if the video interface is available, a display surface is initialized that USES hardware video memory.
定义变量且检查视频接口是否可用之后，使用硬件视频内存的显示表面初始化。
Because the ELF objects are based at offset 0 (until relocation), the convenience variables include the relative offset into the temporary memory block.
因为ELF对象的偏移量是基于0的(除非重新分配)，所以这些方便变量将相对偏移量包含到临时内存块中。
You could consider these "thread-local" copies of variables to be similar to a cache, helping the thread avoid checking main memory each time it needs to access the variable's value.
您可以将变量的这些“线程局部”副本看作是与缓存类似，在每次线程需要访问变量的值时帮助它避免检查主存储器。
Using explicitly typed variables can improve performance and reduce memory consumption.
使用类型明确的变量可以提高性能表现和降低内存消耗。
Reads and writes of atomic variables have the same memory semantics as read and write access to volatile variables.
读取和写入原子变量与读取和写入对可变变量的访问具有相同的存取语义。
In other words, this means that the old memory model made promises only about the visibility of the variable being read or written, and no promises about the visibility of writes to other variables.
换句话说，这意味着老的内存模型只保证正在读或写的变量的可见性，不保证写入其他变量的可见性。
The cache is generally allowed to write variables back to main memory in a different order than they were written by the program.
通常允许缓存以与程序写入变量时所不相同的次序把变量存入主存。
Then, in the debug perspective, you can see the data graph in memory (under Variables), with its data objects (The Boss, Terrence Shorter, etc.), as shown in Figure 4.
然后，在调试窗口中就可以看到内存中的数据图（在Variables 下）和它的数据对象（Boss、Terrence Shorter等），如图 4 所示。
Now if you call a function, swap like increment or cube or swap, or in this case, foo, those variables are the parameters to that function, end up getting stored next in memory.
现在如果你调用一个函数，像increment或者cube或者，或者在这个例子里，foo，这些变量都是，函数的参数，在内存中存储。
Popular for Web development but not limited to it, the language has benefits like taking care of tasks like memory management and declaration of variables so developers do not have to, Goodger said.
Python在Web开发中广为流行但又不仅限于此，它的内存管理、变量声明等性能使开发者不必操心于此。
Atomic variables have memory semantics similar to that of volatile variables, but because they can also be modified atomically, they can be used as the basis for lock-free concurrent algorithms.
原子变量的内存语义与volatile变量类似，但是因为它们也可以被原子性地修改，所以可以把它们用作不使用锁的并发算法的基础。
Kernel variables limited to those pinned in memory.
内核变量仅限于内存中驻留的变量。
Since Perl doesn't have memory allocation issues, the biggest source of bugs for me has been the improper tracking of counter variables (wrong initialization, wrong increments, or wrong bounds).
由于Perl没有内存分配问题，所以对我来说缺陷的最主要来源就是追踪计数器变量的错误(错误的初始化，错误的增量，或者错误的边界)。
Every thread in an application requires memory to hold its stack (the area of memory used to hold local variables and maintain state when calling functions).
应用程序中的每个线程都需要内存来保存它的栈(用于在调用函数时保存本地变量和维持状态的内存区)。
We won't discuss specifics like how many CPUs or how much memory, as these issues depend on far too many variables to enumerate.
我们将不讨论像多少CPU或多大内存这样的具体细节，因为影响这些问题的因素太多了，以致难以胜数。
That allows you to examine and analyze relevant variables and memory contents in a debugger.
这样就允许您检查和分析相关的变量和调试器中内存的状态。
The contents of almost all the other views, including the source editor, Monitors, Registers, Modules, Variables and Memory views, will be updated based on the active debug session.
几乎所有其他视图的内容，包括源代码编辑器、监视器、注册表、模块、变量和内存视图，都会基于活动调试过程来得到更新。
Essentially, local variables (though not always the objects they point to) are free from both memory and time concerns.
实际上，本地变量(并非始终是它们指向的对象)并不影响内存和时间问题。
An area of memory that contains a last-in-first-out queue of storage for parameters, automatic variables, return addresses, and other information that must be maintained across function calls.
一个包含后进先出队列的内存区域，用来存储参数、自动变量、返回地址和其他一些必须在函数调用中进行维护的信息。
An area of memory that contains a last-in-first-out queue of storage for parameters, automatic variables, return addresses, and other information that must be maintained across function calls.
一个包含后进先出队列的内存区域，用来存储参数、自动变量、返回地址和其他一些必须在函数调用中进行维护的信息。
应用推荐