There was some mention that, during the history of Plan 9, developers
had difficulty maintaining two different languages on the system. I
wonder how much of that difficulty would still apply today. Although
the kernel could concievably be translated to a modern compiled
language, I doubt it
On Wed Feb 2 05:04:07 EST 2011, nyanhtoo...@gmail.com wrote:
Hi, Running plan 9 on virtual box 4.0.2, I've configured network
adaptaters as below.
Attached to NAT
Adapter type: PCnet-FAST 3(Am79C973)
check cable connected.
After booting plan 9, I typed ip/ipconfig, after waiting some
2011/2/2 erik quanstrom quans...@quanstro.net:
There was some mention that, during the history of Plan 9, developers
had difficulty maintaining two different languages on the system. I
wonder how much of that difficulty would still apply today. Although
the kernel could concievably be
On Wed, Feb 2, 2011 at 9:06 PM, erik quanstrom quans...@quanstro.net wrote:
On Wed Feb 2 05:04:07 EST 2011, nyanhtoo...@gmail.com wrote:
Hi, Running plan 9 on virtual box 4.0.2, I've configured network
adaptaters as below.
Attached to NAT
Adapter type: PCnet-FAST 3(Am79C973)
check cable
Just to address the unanswered Limbo questions:
The only Limbo compilers extant compile to a portable bytecode for the Dis
virtual machine. The only first-class Dis implementation is built into Inferno.
Dis can be either interpreted or just-in-time compiled. The historical claim
was a that the
On Tue, Feb 1, 2011 at 9:14 PM, smi...@zenzebra.mv.com wrote:
ron minnich rminn...@gmail.com writes:
I think you should set your sights higher than the macro approach you
propose. At least in my opinion it's a really ugly idea.
You might be surprised to hear that I agree. :) It's far
On Tue, Feb 1, 2011 at 11:35 PM, Nick LaForge nicklafo...@gmail.com wrote:
I hope it won't seem rude to suggest it, but the go-nuts list is the
optimum place for your specific concerns. The Go authors read it and
are very conscientious in responding to serious questions.
The Go authors did
On Wed, Feb 2, 2011 at 4:54 AM, erik quanstrom quans...@quanstro.netwrote:
There was some mention that, during the history of Plan 9, developers
had difficulty maintaining two different languages on the system. I
wonder how much of that difficulty would still apply today. Although
the
Even C has a runtime. Perhaps you should look more into how programming
languages are implemented :-). C++ has one too, especially in the wake of
exceptions and such.
really? what do you consider to be the c runtime?
i don't think that the asm goo that gets you to main
really counts as
Wait, isn't it the proof is in the *pudding*? YOU MEAN WE DON'T GET
FRENCH BENEFITS!?!
sadly, no. the work week is still 100hrs and we get -3 holidays/decade.
- erik
Where did your C compiler come from? Someone probably compiled it with a C
compiler. Bootstrapping is a fact of life as a new compiler can't just be
culled from /dev/random or willed into existence otherwise. It takes a plan
9 system to build plan 9 right? (This was not always true for
On Wed, Feb 02, 2011 at 09:47:01AM -0800, David Leimbach wrote:
Wait, isn't it the proof is in the *pudding*? YOU MEAN WE DON'T GET
FRENCH BENEFITS!?!
Please explain.
--
Thierry Laronde tlaronde +AT+ polynum +dot+ com
http://www.kergis.com/
Key fingerprint =
On Wed, 2011-02-02 at 12:50 -0500, erik quanstrom wrote:
Even C has a runtime. Perhaps you should look more into how programming
languages are implemented :-). C++ has one too, especially in the wake of
exceptions and such.
really? what do you consider to be the c runtime?
i don't
On Wed, Feb 2, 2011 at 9:50 AM, erik quanstrom quans...@quanstro.netwrote:
Even C has a runtime. Perhaps you should look more into how programming
languages are implemented :-). C++ has one too, especially in the wake
of
exceptions and such.
really? what do you consider to be the c
On Wed, Feb 2, 2011 at 10:07 AM, tlaro...@polynum.com wrote:
On Wed, Feb 02, 2011 at 09:47:01AM -0800, David Leimbach wrote:
Wait, isn't it the proof is in the *pudding*? YOU MEAN WE DON'T GET
FRENCH BENEFITS!?!
Please explain.
I was just pointing out something that happens a lot in
A runtime system is just a library whose entry points are language
keywords.[1] In go, dynamic allocation, threads, channels, etc. are
accessed via language features, so the libraries that implement those
things are considered part of the RTS. That's a terminological
difference only from
On Wed, Feb 2, 2011 at 10:03 AM, erik quanstrom quans...@labs.coraid.comwrote:
Where did your C compiler come from? Someone probably compiled it with a
C
compiler. Bootstrapping is a fact of life as a new compiler can't just
be
culled from /dev/random or willed into existence otherwise.
On Wed, Feb 2, 2011 at 10:21 AM, erik quanstrom quans...@quanstro.netwrote:
A runtime system is just a library whose entry points are language
keywords.[1] In go, dynamic allocation, threads, channels, etc. are
accessed via language features, so the libraries that implement those
things
Also, from this point of view, could pthreads be considered runtime for C?
no. then every library/os function ever bolted onto
c would be part of the c runtime. clearly this isn't
the case and pthreads are not specified in the c standard.
it might be part of /a/ runtime, but not the c
On Wednesday, February 2, 2011, erik quanstrom quans...@quanstro.net wrote:
Also, from this point of view, could pthreads be considered runtime for C?
no. then every library/os function ever bolted onto
c would be part of the c runtime. clearly this isn't
the case and pthreads are not
On Wed, Feb 02, 2011 at 10:26:34AM -0800, David Leimbach wrote:
On Wed, Feb 2, 2011 at 10:07 AM, tlaro...@polynum.com wrote:
On Wed, Feb 02, 2011 at 09:47:01AM -0800, David Leimbach wrote:
Wait, isn't it the proof is in the *pudding*? YOU MEAN WE DON'T GET
FRENCH BENEFITS!?!
Enjoy...
/$objtype/mkfile
CFLAGS=-FTVwp
binaries=app
headers=important.h
tarfile=app.tgz
srcfiles=${binaries:%=%.c} $headers mkfile
objfiles=${binaries:%=%.$O}
all:V: $binaries
app.$O: important.h
%.$O: %.c
$CC $CFLAGS $prereq
%: %.$O
$LD $LDFLAGS -o $target $prereq
Federico G. Benavento benave...@gmail.com writes:
I take it was trivial to find that overflow, come on the code is so simple
that you just see and get it the first time, which makes easier to find/fix
Oh, really? Simple to find? Trivial? If so, then why wasn't that
overflow found and fixed
On Wed, 2011-02-02 at 13:21 -0500, erik quanstrom wrote:
A runtime system is just a library whose entry points are language
keywords.[1] In go, dynamic allocation, threads, channels, etc. are
accessed via language features, so the libraries that implement those
things are considered part
On Wed, 02 Feb 2011 09:45:56 PST David Leimbach leim...@gmail.com wrote:
Well if I were funded and had an infinite amount of time I'd think LLVM for
Plan 9 would be excellent, as well as Go on LLVM :-).
llvm port would need c++.
$ size /usr/local/bin/clang
textdata bss dec
BCPL makes C look like a very high-level language and provides
absolutely no type checking or run-time support.
B. Stroustrup, The Design and Evolution of C++, 1994
C++ was designed to be used in a rather traditional compilation and
run-time environment, the C programming environment on the
I don't follow. Garbage collection certainly can be done in a library
(e.g., Boehm). GC is in my experience normally triggered by
* Allocation --- which is a function call in C
* Explicit call to the `garbage collect now' entry point in the
standard library. A
On Feb 2, 2011, at 1:31 PM, erik quanstrom wrote:
i think of it this way, the janitor doesn't insist that the factory shut
down so he can sweep. he waits for the factory to be idle, and then
sweeps.
Clearly I've been working on the wrong floors. That or all the janitors I know
are using
On Wed, 2011-02-02 at 14:31 -0500, erik quanstrom wrote:
I don't follow. Garbage collection certainly can be done in a library
(e.g., Boehm). GC is in my experience normally triggered by
* Allocation --- which is a function call in C
* Explicit call to the `garbage collect
start := now();
while (now() start + 2hours);
You don't expect GC to be able to trigger, right?
i sure do.
- erik
On Wed, 2011-02-02 at 15:11 -0500, erik quanstrom wrote:
start := now();
while (now() start + 2hours);
You don't expect GC to be able to trigger, right?
i sure do.
Ah. Interesting. Who's done that?
jcc
On Wed, Feb 2, 2011 at 11:15 AM, smi...@zenzebra.mv.com wrote:
bugs, iterators and the other crap you mentioned would had obfuscated
it.
The other crap I mentioned would have made that bug IMPOSSIBLE.
OK, let's do a test. You write your stuff with iterators and put it on
a machine with
$ size /usr/local/bin/clang
textdata bss dec hex filename
228428621023204 69200 2393526616d3922 /usr/local/bin/clang
impressive. certainly in the sense of `makes quite a dent if dropped'.
you'll hear people call [fringe benefits] French Benefits.
i did not expect that! i'd have guessed: `cheese'.
On Wed Feb 2 19:19:13 EST 2011, fors...@terzarima.net wrote:
$ size /usr/local/bin/clang
textdata bss dec hex filename
228428621023204 69200 2393526616d3922 /usr/local/bin/clang
impressive. certainly in the sense of `makes quite a dent if dropped'.
and
$ size /usr/local/bin/clang
textdata bss dec hex filename
228428621023204 69200 2393526616d3922 /usr/local/bin/clang
i suppose a more useful comment might be a question:
how does a C compiler get to be that big? what is all that code doing?
On Wed, Feb 2, 2011 at 4:52 PM, Charles Forsyth fors...@terzarima.net wrote:
i suppose a more useful comment might be a question:
how does a C compiler get to be that big? what is all that code doing?
iterators, string objects, and a full set of C macros that ensure
boundary conditions and
On Thu, 03 Feb 2011 00:52:35 GMT Charles Forsyth fors...@terzarima.net wrote:
$ size /usr/local/bin/clang
textdata bss dec hex filename
228428621023204 69200 2393526616d3922
/usr/local/bin/clang
i suppose a more useful comment might be a question:
On Wed, Feb 2, 2011 at 6:16 PM, Bakul Shah
bakul+pl...@bitblocks.combakul%2bpl...@bitblocks.com
wrote:
On Thu, 03 Feb 2011 00:52:35 GMT Charles Forsyth fors...@terzarima.net
wrote:
$ size /usr/local/bin/clang
textdata bss dec hex filename
228428621023204
ron minnich rminn...@gmail.com writes:
OK, let's do a test. You write your stuff with iterators and put it on
a machine with 256MB. I'll create a file with a file name that is
257MB long. What does your stuff do then?
The finished version will support strings backed by file storage and
should
Apologies if I've overlooked mention of this, but is there
an easy way to determine when a given 9atom .iso was generated?
How often are these updated?
-sl
The finished version will support strings backed by file storage and
I'm patiently waiting for strings backed by cloud storage.
On Thu, Feb 03, 2011 at 03:35:04AM +, smi...@zenzebra.mv.com wrote:
The finished version will support strings backed by file storage and
should actually be able to handle that. But that's still far in the
future, at this point. I haven't even finished coding the basic string
operations
On Thursday, February 03, 2011 04:35:04 am smi...@zenzebra.mv.com wrote:
ron minnich rminn...@gmail.com writes:
OK, let's do a test. You write your stuff with iterators and put it on
a machine with 256MB. I'll create a file with a file name that is
257MB long. What does your stuff do then?
44 matches
Mail list logo
