linux-kernel - Re: Kernel Development & Objective-C

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071204175413.GD2310@csclub.uwaterloo.ca>
Date:	Tue, 4 Dec 2007 12:54:13 -0500
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	"J.A. Magall??n" <jamagallon@....com>
Cc:	Lo??c Greni?? <loic.grenie@...il.com>,
	Ben.Crowhurst@...llatravel.co.uk, linux-kernel@...r.kernel.org
Subject: Re: Kernel Development & Objective-C

On Sat, Dec 01, 2007 at 12:19:50AM +0100, J.A. Magall??n wrote:
> I think BeOS was C++ and OSX is C+ObjectiveC (and runs on an iPhone).
> Original MacOS (fron 6 to 9) was Pascal (and a mac SE was very near
> to embedded hardware :) ).
> 
> I do not advocate to rewrite Linux in C++, but don't say a kernel written
> in C++ can not be efficient.

Well I am pretty sure the micro kernel of OS X is in C, and certainly
the BSD layer is as well.  So the only ObjC part would be the nextstep
framework and other parts of the Mac GUI and other Mac APIs they
provide, which all at some point probably end up calling down into the C
stuff below.

> C++ (and for what I read on other answer, nor ObjectiveC) has no garbage
> collection. It does not anything you did not it to do. It just allows
> you to change this
> 
> 	struct buffer *x;
> 	x = kmalloc(...)
> 	x->sz = 128
> 	x->buff = kmalloc(...)
> 	...
> 	kfree(x->buff)
> 	kfree(x)
> 	
> to
> 	struct buffer *x;
> 	x = new buffer(128); (that does itself allocates x->buff,
>                               because _you_ programmed it,
>                               so you poor programmer don't forget)
>         ...
> 	delete x;            (that also was programmed to deallocate
>                               x->buff itself, sou you have one less
>                               memory leak to worry about)

But kmalloc is implemented by the kernel.  Who implements 'new'?

--
Len Sorensen
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/