Kjell,
Am 25.08.2008 um 01:18 schrieb Kjell Godo:
So being without tools is better than being with tools because that
increases portability not to be dependent on anything. But I miss
the Squeak debugger. What debugger do you use for fonc? [...]
I think one cannot overemphasise that this
Michael FIG wrote:
Kjell Godo [EMAIL PROTECTED] writes:
So what you're saying is that the idc which is written in C
compiles C like code into machine code?
idc is written in Pepsi. You may be confused because the bootstrap
.o.c files are included in the SVN checkout, at least
Message -
From: Joshua Gargus
To: Fundamentals of New Computing
Sent: Sunday, August 24, 2008 5:02 PM
Subject: Re: [fonc] Coding Standards
Michael FIG wrote:
Kjell Godo [EMAIL PROTECTED] writes:
So what you're saying is that the idc which is written in C
compiles C like code
Hello Joshua,
Saturday, August 23, 2008, 9:42:38 AM, you wrote:
I think that (part of) the point is to be able to bootstrap with minimal
tool support, and thereafter to be self-supporting. The bootstrap
process is described better than I can in Section 6.1 of Accessible
Language-Based
So what you're saying is that the idc which is written in C
compiles C like code into machine code?
And then that machine code compiles Smalltalk like idst/Pepsi
into machine code? The idst/Pepsi compiles itself into machine
code. And this bootstrapping happens over and over again and
not just
Ah, space wars and brace wars rise again!
I'd like to propose that no standard be imposed...until a beautifier (text
filter) has been created to implement such a norm. After which, everyone
can peer at the code through their own rose-colored beautifiers.
;-)
Cheers,
--ken ritchie (atlanta)
PS,
On Jun 22, 2008, at 2:41 AM, John Leuner wrote:
What do you use a teletype for?
Backing up my sources to punched tape.
Cheers,
Ian
PS: if you're taking me seriously in this tread, it's time to stop.
___
fonc mailing list
fonc@vpri.org
Set your tabs stops every eight columns and the source will be
aligned properly.
I like the tabs in the source because I can move around indented
lines faster (and the file is a few bytes shorter). I also like
braces lined up like this
if (foo)
{
bar();
}
which would mean a tab
Now that Michael has set up repositories to which patches can be submitted, it
would be good for the project to have a few coding standards enforced for the
contributions.
I would like to see an all spaces, no tabs standard. The handful of files
in the current codebase which I looked at all
