Coding practices are a source of a lot of arguments among programmers. Coding standards, to some degree, help us to put certain questions to bed and resolve stylistic debates. No coding standard makes everyone happy. (And even their existence is sure to make some unhappy.) What follows are the standards we put together on the Core team, which have become the general coding standard for all programming teams on new code development. We’ve tried to balance the need for creating a common, recognizable and readable code base with not unduly burdening the programmer with minor code formatting concerns.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
""" | |
pybble.py | |
Yup, you can run Python on your Pebble too! Go thank the good folks who | |
made Transcrypt, a dead-simple way to take your Python code and translate | |
it to *very* lean Javascript. In our case, instead of browser, we run it | |
on Pebble using their equally dead-simple Online IDE and Pebble.js library. | |
Here's a working example, it runs on a real Pebble Classic. |
Updated: Just use qutebrowser (and disable javascript). The web is done for.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/sh | |
# | |
# | |
# From: [email protected] ([email protected]) | |
# Subject: bournebasic | |
# Newsgroups: comp.sources.misc | |
# Date: 1987-08-18 18:54:12 PST | |
# | |
# Here's a useful BASIC interpreter written in Bourne shell. | |
# There's no manual but this demo shows the most salient features: |