C programmers think memory management is too important to be left to the computer. Lisp programmers think memory management is too important to be left to the user.
ACTUALLY IM AN EXPERT C PROGRAMMER, MY OTHER MALLOC IS A FREE() HAX MY ANUS
Name:
Anonymous2010-02-14 18:33
Step 1: Look at your packaged goods. Find the Japanese kanji character for paper: 紙. This means that it is considered burnable garbage and should be put in the appropriate bin lined with an opaque, burnable garbage bag.
Step 2: All food waste is considered burnable garbage, the food itself, not the package it is in, unless the wrapper is labeled "paper" or "burnable".
Step 3: Find the Japanese katakana characters for plastic: プラ that is encircled with a squarish arrow. This indicates that the item should be disposed with plastic, non-burnable garbage. These garbage bags are clear, meaning see-through, not opaque like the burnable garbage bags.
Step 4: Plastic bottles, like soda bottles, or water bottles, are separated from all other types of garbage. Aluminum or tin cans, soda cans are also included in this category of "pets, bin, can" garbage. The plastic labels on the bottles should be removed and put into "plastic" garbage bins, and the plastic bottle caps are put into "other non-burnable" garbage bags.
Step 5: Disposing electronic equipment like televisions, computers, hot pots, mattresses, bookshelves, furniture, bicycles, carpets, large items that cannot fit into a 40 liter garbage bag need to be picked up by special appointment with the city, which usually costs extra money. Some areas have a free "big garbage" day in which these large items can be disposed of without charge.
Name:
!iN.MY.aRMs2010-02-14 18:33
retardes, use perl
Name:
!iN.MY.aRMs2010-02-14 18:34
from all languages for retardes, perl the best
Name:
Anonymous2010-02-14 18:46
MY OTHER MALLOC IS A FREE
Name:
Anonymous2010-02-14 19:36
>>7
THAT WILL BE ESPECIALLY EASY, SINCE YOU MANAGE YOUR ANUS MANUALLY
Name:
Anonymous2010-02-14 21:56
Java users let the computer handle memory management. They don't have trust issues.
Name:
!iN.MY.aRMs2010-02-14 21:59
>>13
Java woking like chit
first java eat all memory
then do "garbage collecting" and halt for 5 minutes
Name:
Anonymous2010-02-14 21:59
I don't manage memory I just let it leak, I can always buy more anyway. EXTREME C PROGRAMMING
>>14
Uhm. Shouldn't you learn english before you get to programming languages?
Name:
Anonymous2010-02-15 3:11
>>14
Some people even manage to leak memory with a garbage collector.
Name:
Anonymous2010-02-15 3:22
>>15
I do this but for a different reason. I don't leak if it will cause the program to crash, but it is a waste of cpu time to free resources. it is better to let them leak. when the process is done, then the os will free them anyways, so i just hold onto em until im dont with my program to make it faster.
>>18
How hard it is to identify a troll/idiot, especially if he's using a tripcode?
Name:
Anonymous2010-02-15 3:40
I have a global hash table; malloc(a) stores a in that table and returns a unchanged; free(a) removes a from hash table. This way, even with garbage-collected language I can use manual memory allocation; garbage collector won't touch anything until I free it (and I malloc and free everything).
Oh yeah I don't use free, its for pussies
are you too chicken to leave garbage collecting to the OS?
Name:
Anonymous2010-02-15 9:58
>>28
I would NEVER leave GC to the OS! I always use free, sometimes twice to ensure the memory has actually been freed.
Name:
Anonymous2010-02-15 11:43
FREE MY ANUS
Name:
Anonymous2010-02-15 12:31
If you're not confident enough to let the computer do something on its own, you're in the wrong field - you should have gone into computer engineering.
>>33
After a tip I got off some Unix page, I now name all my files in the fashion of small letters to my Grandma.
My dead Grandma. Are you reading my letters, Grandma? ;_;
>>20,21
Actually this is only partially a troll. With modern operating systems it's faster to just leak all reachable memory on app exit and let the operating system reclaim your pages, instead of invoking free() on every little chunk of memory and having the allocator do a shitload of useless work.
This is also why tools like Valgrind don't throw a bunch of warnings for reachable leaked memory on app exit. It's normal to just leak everything.
Of course you should not accumulate leaks; any temporary memory that doesn't need to survive the lifetime of the app should be free()d. Valgrind throws a warning if you leak something you no longer have a reference to; this is memory you should free().
Name:
Anonymous2010-02-16 1:56
>>37
This is so stupid; dealloc is not a destructor, since you can't be sure if it will be called, which means you can't place things you want done in it when object is destroyed. Which leaves you with one thing - things you don't care about but somehow still have to do like deallocating memory or freeing resources, things that are done automatically by the language in sane world.
Name:
Anonymous2010-02-16 2:29
>>38
Um, yeah. -dealloc is not a destructor; it is *ONLY* for releasing referenced memory. If you have resources you need to close/flush/whatever, you add your own method to do that, and call it at the appropriate time.
Note that most modern garbage-collected languages don't actually have destructors. In fact I'm not sure Objective-C on desktop even calls -dealloc in GC mode. Some of them have special GC hooks, like Java's finalize(), but they are inefficient and unreliable and generally shouldn't be used. (This does not apply to Python however, since its implementation of GC is totally fucked.)