This shows you the differences between two versions of the page.
|
start [2010/02/03 10:17] wikiops |
start [2010/02/03 10:18] (current) wikiops |
||
|---|---|---|---|
| Line 12: | Line 12: | ||
| </code> | </code> | ||
| It's easy to extend Bitlash by naming a sequence of commands as a [[macros:overview|Macro]], which is like a new word in the Bitlash language. A Bitlash application is a set of such macros, and since they are stored in the EEPROM, Bitlash can start up your application automatically at boot time for standalone operation. | It's easy to extend Bitlash by naming a sequence of commands as a [[macros:overview|Macro]], which is like a new word in the Bitlash language. A Bitlash application is a set of such macros, and since they are stored in the EEPROM, Bitlash can start up your application automatically at boot time for standalone operation. | ||
| - | + | ||
| - | It's also easy to integrate your C code with Bitlash as a [[userfunctions|User Function]] where performance is an issue. | + | In cases where you need native C code to get closer to the hardware, perhaps for speed or to interface with a custom peripheral, |
| + | it's also easy to integrate your C code with Bitlash as a [[userfunctions|User Function]]. | ||
| Read on for more about Bitlash. | Read on for more about Bitlash. | ||