Posted: Thu Jul 03, 2008 11:46 am
has it got anything to do with rebotic hamsters?
you could argue that any low level programming language controls memory really...Ashley wrote:
Controls memory on a portable device such as but not limited to a mobile phone.
truely truely fascinating stuffWikipedia wrote:
Stacks in computing architectures are regions of memory where data is added or removed in a Last-In-First-Out manner.
In most modern computer systems, each thread has a reserved region of memory referred to as its stack. When a function executes, it may add some of its state data to the top of the stack; when the function exits it is responsible for removing that data from the stack. If a region of memory lies on the thread's stack, that memory is said to have been allocated on the stack.
So arguably I win the kitkat?dr ddd wrote:you could argue that any low level programming language controls memory really...Ashley wrote:
Controls memory on a portable device such as but not limited to a mobile phone.
so actually elbe - if you replace robotic with the word "stack" and hamster with the word "memory" - you win
truely truely fascinating stuffWikipedia wrote:
Stacks in computing architectures are regions of memory where data is added or removed in a Last-In-First-Out manner.
In most modern computer systems, each thread has a reserved region of memory referred to as its stack. When a function executes, it may add some of its state data to the top of the stack; when the function exits it is responsible for removing that data from the stack. If a region of memory lies on the thread's stack, that memory is said to have been allocated on the stack.
dr ddd wrote:you could argue that any low level programming language controls memory really...Ashley wrote:
Controls memory on a portable device such as but not limited to a mobile phone.
so actually elbe - if you replace robotic with the word "stack" and hamster with the word "memory" - you win
truely truely fascinating stuffWikipedia wrote:
Stacks in computing architectures are regions of memory where data is added or removed in a Last-In-First-Out manner.
In most modern computer systems, each thread has a reserved region of memory referred to as its stack. When a function executes, it may add some of its state data to the top of the stack; when the function exits it is responsible for removing that data from the stack. If a region of memory lies on the thread's stack, that memory is said to have been allocated on the stack.
I was firsteLBe wrote:back off ash the kitkat's mine
I am sure Will is pleased to hear that.Ashley wrote:Will I am sitting here going through a 79,000 line CSV file removing any anomalities.
Who is Will?eLBe wrote:I am sure Will is pleased to hear that.Ashley wrote:Will I am sitting here going through a 79,000 line CSV file removing any anomalities.
And how much of it are you going to eat you greedy fuck,badger wrote:i've got four different types of chocolate based snack in my desk drawer
I've got a stale gingerbread man and a bag of tangy cheese doritos.badger wrote:i've got four different types of chocolate based snack in my desk drawer
can of mackerel vonny von?!Von wrote:I'm so freakin bored. My job here is done.
Does the mackerel come in a sauce? A delicious, rich, tomato sauce? If so, I'll trade you the stale gingerbread man....dr ddd wrote:i have a tin of mackerel, a can of tomato soup, a box of lemon and ginger tea and a box of white tea
swap?
i also have tea, coffee, sugar, 3 types of crisps, cornflakes, porridge, 2 flavours of cupasoup, some lollipops and various canned drinks... and i just found what's left of a tube of fruit pastillesdr ddd wrote:i have a tin of mackerel, a can of tomato soup, a box of lemon and ginger tea and a box of white tea
swap?