sliverorange coding conventions

Peter Rukavina

The fellows upstairs have their own coding conventions. Who knew? [[Steven Garrity]] ordered the [[Formosa]] Combo yesterday, a stark departure from his usual stuffed bun or sushi; I’m pretty sure this falls outside of the conventions.

Comments

Submitted by al o'neill on

Permalink

I like the compromise for the brace style, old and busted
name
{
thing
}
for classes and functioned,

new hotness

name {
thing
}

Submitted by Steven Garrity on

Permalink

As Isaac mentioned, the need for documented coding convention arose from our plans to release some of our software as open-source. If we’re to be get people submitting code, we want somewhere to be able to point people when we tell them it sucks.

Add new comment

Plain text

  • Allowed HTML tags: <b> <i> <em> <strong> <blockquote> <code> <ul> <ol> <li>
  • Lines and paragraphs break automatically.

About This Blog

Photo of Peter RukavinaI am . I am a writer, letterpress printer, and a curious person.

To learn more about me, read my /nowlook at my bio, listen to audio I’ve posted, read presentations and speeches I’ve written, or get in touch (peter@rukavina.net is the quickest way). 

You can subscribe to an RSS feed of posts, an RSS feed of comments, or a podcast RSS feed that just contains audio posts. You can also receive a daily digests of posts by email.

Search