Language Hype

It's an unknown fact that most GNU utils written in C never free up the memory they allocate, which usually results in memory leaks.

You may wonder, why? It's because C lacks RAII.

Same goes for D; although D does have RAII, its Garbage Collector creates memory leaks by allocating and never freeing ridicolously large memory chunks.

This code allocates 41,688 bytes, and never frees it:

import tango.io.Stdout;

void main(char[][] args)
{
    Stdout("Hello World!").newline();
}

Imagine the memory chunk allocated by the GC for a ``bigger'' application.

Yet D & C folks claim to be better than C++...

An unknown fact, is it? Well how do you know it then, mister smartypants?

>>1
tango
Please, use D2.
You may wonder, why?
Because GNU utils is made of crap.
because C lacks RAII.
It's so hard to put an object_destroy(); at the end of the scope.
Yet D & C folks claim to be better than C++...
Because they are.


Also, LISP.

This code allocates [seemingly absurd chunk of memory]
I wonder why...
import
Oh right.

Imagine the memory chunk allocated by the GC for a ``bigger'' application.
Why the faggot qu--oh I see, ``bigger'', eh? ;) As in, no more than about 40KB bigger? I forget how GC works.

It's all better than Java...what kind of faggot codes a game in Java? RUNS LIKE SHIT

>>2
Valgrind.

>>3
It's so hard to put an object_destroy(); at the end of the scope.
You obviously don't understand RAII.

>>4
Why the faggot qu--oh I see, ``bigger'', eh? ;) As in, no more than about 40KB bigger? I forget how GC works.
Because there is no such thing as 'big, noteworthy D application'... well, except the DMD compiler itself. Yes, D is a sad clownlanguage like that.

RAII
(define malloc
  ; get malloc through ffi
  (lambda (size)
    (display "malloc'ed ")
    (display size)
    (display " bytes")
    (newline)
    (lambda ()
      size)))

(define free
  ; get free through ffi
  (lambda (ptr)
    (display "freed ")
    (display (ptr))
    (display " bytes")
    (newline)))
   

(define-syntax with-malloc
  (syntax-rules ()
    ((with-malloc ((ptr args ...) ...) b ...)
     (let ((ptr (malloc args ...)) ...)
       b ...
       (begin
         (free ptr) ...)))))

> (with-malloc ((p 256)
              (t 64)
              (r 65536))
   ; play with the pointers
   (+ (p) (t) (r)))
malloc'ed 256 bytes
malloc'ed 64 bytes
malloc'ed 65536 bytes
freed 256 bytes
freed 64 bytes
freed 65536 bytes
>

LOL WATCH ME I'M SO SEPPLES

What's with all this "[u]because[/i] C lacks RAII" business?

I think >>1 is even more confused than >>3 is.

>>8
I sense a lack of [i][u][o]BBCODE M[sup]A[sup]STER_Y[/o][/u][/i]

>>9
ah fuck.

Object Oriented is a Sexual Preference

>>11
PREFER MY ANUS! but be gentle, please.

>>10
Irony!

>>9-10
laughingirls.jpg