for: faster, better readability against: memory isn't used optimally
No, the int variable uses less memory, and therefore it is preferable to use an int rather than a double where you can.A boolean variable uses even less memory, but obviously is useful only in limited circumstances.
Platform dependent. Many in unix, few in WinDos.
In 8086 microprocessor the total memory addressing capability is 1 mega bytes. For representing 1 mb there are minimum 4 hex digits are required i.e, 20 bits. but 8086 has fourteen 16-bit registers. That is there are no registers for representing 20 bit address. So,the total memory is divided into 16 logical segments and each segment capacity is 64 kb(kilo bytes). That is 16*64kb=1 mb.So,for representing 64 kb only 16 bit register is sufficient. In 8086 microprocessor the total memory addressing capability is 1 mega bytes. For representing 1 mb there are minimum 4 hex digits are required i.e, 20 bits. but 8086 has fourteen 16-bit registers. That is there are no registers for representing 20 bit address. So,the total memory is divided into 16 logical segments and each segment size is 64 kb(kilo bytes). That is 16*64kb=1 mb.So,for representing 64 kb only 16 bit register is sufficient.
When you call a function, the stack pointer is adjusted to cater for the function's arguments (if any), the caller's return address (mandatory), the function's local variables (if any) and the function's exception handlers (if any).
The differences are given below: 80286 1. Low data bus width (16 bit) 2. Returning from protected mode to real mode is hard and complicated. 3. Small RAM/Memory 80386 1. High data bus width (32 bit) 2. Easy for 80386 3. Big RAM / Memory (Real memory = 4GB and virtual memory= 64TB)
for: faster, better readability against: memory isn't used optimally
For: Using a single bit instead of an entire byte will conserve memory Against: Processors to have addresses for single bits. So up to 8 Booleans values can be combined into a single byte, which means bit-wise arithmetic to separate the separate values. Although this conserves memory, it takes more time (CPU time) to deal with.
It;s a powerful 3gig 4bit memory search engine FTW!
Odin
Boolean logic can be thought of as "0 and 1" logic, or "True or False" logic. Boolean math started out as "True or False" expressions. In computers, the bits stored in memory are interpreted as either a '0' or a '1' (binary numbers). Computer scientists (usually, though you can prove out the concept either way) map '0' = FALSE and '1' = 'TRUE', and thus the operations and decisions made in a computer can be expressed/evaluated as Boolean logic/math expressions.
No, the int variable uses less memory, and therefore it is preferable to use an int rather than a double where you can.A boolean variable uses even less memory, but obviously is useful only in limited circumstances.
The primitive data types that can normally be represented and processed by a CPU are an integer, real number, character, Boolean, and memory address
The Campaign of Memory
Data structures are classified as either linear or non linear, a data structure is said to be linear if its elements form a sequence, or, in other words, a linear list, there are two basic ways of representing such linear structures in memory, one way is to have the linear relationship between the elements represented by means of sequential memory locations, these linear structures are called arrays, the other way is to have the linear relationship between the elements represented by means of pointers or links, these linear structures are called linked lists.
Platform dependent. Many in unix, few in WinDos.
A bank schema system has columns and rows representing the system memory sockets. Independent sockets are shown in rows and banks of sockets are shown in columns. It is a way to diagram memory configurations.
No. Sorry. Maybe if you mode it.