On 3/24/10 9:13 PM, Joerg Sonnenberger wrote:
The point is that you don't really get that. Consider mutexes currently
hold by a different thread in the original program. May I strongly
advise you to first identify exactly where Ruby is failing and based on
that let us decide how it can be
On Thu, Mar 25, 2010 at 09:09:32AM +, David Holland wrote:
On Thu, Mar 25, 2010 at 12:46:10PM +0900, Masao Uebayashi wrote:
% grep ':.*,' sys/conf/files | wc -l
86
And? I don't understand your point. There are a lot more than 86
entities in sys/conf/files.
There are many
On Thu, Mar 25, 2010 at 06:22:17PM +0900, Masao Uebayashi wrote:
% grep ':.*,' sys/conf/files | wc -l
86
And? I don't understand your point. There are a lot more than 86
entities in sys/conf/files.
There are many instances where modules have multiple dependencies.
jeanyves.mig...@free.fr said:
There should be some way to serialize/deserialize prop/plistref
objects within the kernel, but I never found a solution. I suppose
you will have to dig deeper than I did :/
I think it should be avoided at all costs. With proplists, you give up type
safety
and
On Thu, 25 Mar 2010, Matthias Drochner wrote:
jeanyves.mig...@free.fr said:
There should be some way to serialize/deserialize prop/plistref
objects within the kernel, but I never found a solution. I suppose
you will have to dig deeper than I did :/
I think it should be avoided at all
On Fri, Mar 26, 2010 at 12:41 PM, matthew green m...@eterna.com.au wrote:
On Fri, Mar 26, 2010 at 6:49 AM, David Holland dholland-t...@netbsd.org
wrote:
On Thu, Mar 25, 2010 at 06:22:17PM +0900, Masao Uebayashi wrote:
% grep ':.*,' sys/conf/files | wc -l
86
To manage dependency nicely.
When a module A dpend on B, you write define A: B, where B has to be
already define'ed in the current syntax. We're managing such
ordering by hand in sys/conf/files. By splitting files use
include, we don't need to manage such a mess by hand.
