<glowcoil>
pikajude: I am always playing executive function or depression
Sorella has quit [Ping timeout: 240 seconds]
Sorella has joined #elliottcable
alexgordon has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
Cheery has quit [Remote host closed the connection]
Cheery has joined #elliottcable
alexgordon has joined #elliottcable
fujisan has quit [Quit: Connection closed for inactivity]
<purr>
<jeannicolas> alexgordon styles his hair with a finite state machine ... why am I not surprised
<eligrey>
wut mobilexterm includes a mosh client
Sorella has quit [Quit: Connection closed for inactivity]
inimino has quit [Ping timeout: 272 seconds]
inimino has joined #elliottcable
Rurik has joined #elliottcable
alexgordon has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
Rurik has quit [Ping timeout: 240 seconds]
Rurik has joined #elliottcable
Rurik has quit [Ping timeout: 272 seconds]
Rurik has joined #elliottcable
Rurik has joined #elliottcable
fujisan has joined #elliottcable
<purr>
<locks> elliot is always up, he takes viagra by the bucketful
audy has quit [Ping timeout: 264 seconds]
nuck has joined #elliottcable
nuck is now known as Guest8906
audy has joined #elliottcable
eligrey has quit [Quit: Leaving]
Rurik has quit [Ping timeout: 276 seconds]
fujisan has quit [Quit: Connection closed for inactivity]
fujisan has joined #elliottcable
Sorella has joined #elliottcable
<purr>
<glowcoil> oh my fucking god you still think java is a really good sandwich alexgordon
gq has joined #elliottcable
Rurik has joined #elliottcable
ohhoe_ is now known as ohhoe
<purr>
<micahjohnston> DALEKSGORDON: thought you should know
<jaawerth>
lol daleks
<purr>
LOL
<pikajude>
glowcoil: did you end up getting to your therapy
<Rurik>
Can anyone here explain the stack and the heap to me?
<glowcoil>
pikajude: yeah! and also class and work
<glowcoil>
Rurik: yeah
<pikajude>
good job m8
<glowcoil>
Rurik: the stack is a section at the beginning of your program's memory. there's a pointer to keep track of the end of it. when you call a function, it needs space to allocate its arguments and local variables, so the stack pointer is moved forward to make just enough space for those. then when the function returns the stack pointer moves back again
<glowcoil>
pikajude: thanks, how have you been doing
<pikajude>
I'm all right, just trying a new medication
<glowcoil>
pikajude: oh! is it going ok
<pikajude>
I just took the first one so well find out today
<pikajude>
also finding out if I get a raise next week
<pikajude>
which will be helpful since I'm not ec levels of independently wealthy
<glowcoil>
Rurik: whereas the heap is just a big collection of chunks of memory, and your program can call malloc() or new or whatnot to grab a chunk that's big enough. so stuff that's on the heap sticks around either till you call free() (in a non-garbage-collected language) or until the garbage collector frees it
<glowcoil>
pikajude: good luck!
<glowcoil>
Rurik: is that what you are asking? hope I didn't explain too much/too little
<pikajude>
glowcoil: thanks man
<pikajude>
you too
<glowcoil>
: ]
<pikajude>
Rurik: btw the heap is called the heap because it's actually a heap (the data structure)
<pikajude>
at least i think it is
<glowcoil>
pikajude: it may be sometimes, but it can also be a plain old linked list
<pikajude>
alas i am slain
<glowcoil>
haha
<glowcoil>
i wrote malloc() in a class last semester
<pikajude>
Rurik: in many cases, you'll not want to use heap memory since allocating it is slower
<pikajude>
and certain low-memory environments don't even have dynamic allocation!
<pikajude>
also, kernels!
<ELLIOTTCABLE>
pikajude: what
<pikajude>
ELLIOTTCABLE: ?
<Rurik>
glowcoil, yep
<Rurik>
I am trying to understand Rust so that is why I was asking