[fonc] Coding Standards

2008-06-20 Thread Karl Robillard
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

Re: [fonc] Coding Standards

2008-06-20 Thread Steve Folta
On Fri, Jun 20, 2008 at 12:30 PM, Karl Robillard <[EMAIL PROTECTED]> wrote: > I would like to see an "all spaces, no tabs" standard. And I would like to see an "all tabs, no spaces" standard. Maintain your own fork if you must, but don't try to impose spacist wrongheadedness on those of us who kn

Re: [fonc] Coding Standards

2008-06-20 Thread Michael FIG
Hi, Karl Robillard <[EMAIL PROTECTED]> writes: > 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 think the only standard is "keep the same spirit of what is alre

Re: [fonc] Coding Standards

2008-06-20 Thread Karl Robillard
On Friday 20 June 2008 01:30:25 pm Steve Folta wrote: > As you note, the current codebase is neither spacist (it has tabs) nor > tabbist (it only looks right at a particular tab-width setting) in > style. Although I'm a hardcore tabbist, I think we should all just > put up with it as it is. I don

Re: [fonc] Coding Standards

2008-06-21 Thread Joshua Gargus
On Jun 20, 2008, at 8:25 PM, Karl Robillard wrote: On Friday 20 June 2008 01:30:25 pm Steve Folta wrote: As you note, the current codebase is neither spacist (it has tabs) nor tabbist (it only looks right at a particular tab-width setting) in style. Although I'm a hardcore tabbist, I think w

Re: [fonc] Coding Standards

2008-06-21 Thread Ian Piumarta
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

Re: [fonc] Coding Standards

2008-06-22 Thread John Leuner
What do you use a teletype for? John On Sat, 2008-06-21 at 11:45 -0700, Ian Piumarta wrote: > 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 sh

Re: [fonc] Coding Standards

2008-06-22 Thread Bert Freudenberg
Am 22.06.2008 um 11:41 schrieb John Leuner: What do you use a teletype for? John http://en.wikipedia.org/wiki/Teletype SCNR, - Bert - On Sat, 2008-06-21 at 11:45 -0700, Ian Piumarta wrote: Set your tabs stops every eight columns and the source will be aligned properly. I like the tabs

Re: [fonc] Coding Standards

2008-06-22 Thread Ken Ritchie
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)

Re: [fonc] Coding Standards

2008-06-22 Thread Ian Piumarta
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 http://vpri

Re: [fonc] Coding Standards

2008-08-23 Thread Kjell Godo
Wouldn't this whole thing be better written in Smalltalk than in gcc? gcc is more portable? Couldn't Smalltalk output assembler that gcc could then compile? I saw an assembler written in Smalltalk once. Hope I still have it. It was very simple and clean looking. I am writting a compiler for a l

Re: [fonc] Coding Standards

2008-08-23 Thread Joshua Gargus
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 Environments of Recursive Theories", available on the VPRI website. C is d

Re: [fonc] Coding Standards

2008-08-23 Thread Derek Kuliński
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 E

Re: [fonc] Coding Standards

2008-08-23 Thread Kjell Godo
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 on

Re: [fonc] Coding Standards

2008-08-23 Thread Michael FIG
"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 until idc targets Coke instead

Re: [fonc] Coding Standards

2008-08-24 Thread Derek Kuliński
Hello Kjell, Saturday, August 23, 2008, 7:07:02 PM, you wrote: > 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

Re: [fonc] Coding Standards

2008-08-24 Thread Joshua Gargus
Derek Kuliński wrote: > 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

Re: [fonc] Coding Standards

2008-08-24 Thread Joshua Gargus
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 checkou

Re: [fonc] Coding Standards

2008-08-24 Thread 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? So: If you had done it in Smalltalk instead of gcc: Once you get fonc to compile on Squeak then you tell i

Re: [fonc] Coding Standards

2008-08-24 Thread Alejandro F. Reimondo
onclusion at low cost or fast, it has been +30years from the first sustainable system in computer media. cheers, Ale. - Original Message - From: Joshua Gargus To: Fundamentals of New Computing Sent: Sunday, August 24, 2008 5:02 PM Subject: Re: [fonc] Coding Standards Mich

Re: [fonc] Coding Standards

2008-08-24 Thread Michael Haupt
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

Re: [fonc] Coding Standards: Editor settings?

2008-06-20 Thread Kurt Stephens
Perhaps a loadable set of vim and emacs (and other) settings should be added to the repository? We should not do any thing different from what Ian has been doing, otherwise the merge to upstream will be a nightmare. Kurt Steve Folta wrote: > On Fri, Jun 20, 2008 at 12:30 PM, Karl Robillard > <[E

Re: [fonc] Coding Standards: Editor settings?

2008-06-20 Thread Michael FIG
Hi, Kurt Stephens <[EMAIL PROTECTED]> writes: > Perhaps a loadable set of vim and emacs (and other) settings should be added > to the repository? I'm pretty sure Ian is using something like the following (or a derivative) for his Emacs smalltalk-mode: http://piumarta.com/pepsi/old/pepsi-0.1/etc

Re: [fonc] Coding Standards: Editor settings?

2008-06-21 Thread Karl Robillard
Kurt Stephens <[EMAIL PROTECTED]> writes: > We should not do any thing different from what Ian has been doing, otherwise > the merge to upstream will be a nightmare. Folks, judging from a few randomly selected files, the current code seems to be a total hodge-podge of tabs and spaces. There is