Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About dcnjneer

  • Rank
  1. Thanks Dave. The simpler examples are definitely easier to grasp. I guess the lcd_driver.h file is an example of "long-winded" definitions.
  2. I seem to be having the most problems with macros, templates, and compiler directives, rather than simple C language. I was studying the file lcd_driver.h to understand how it works and came across these blocks of code that I assume are template definitions (the ellipis are mine): #define _LCD_FunctionMode LCD_FunctionMode <InterfaceType...RS,RW,E> #define _LCD_TEMPL template < unsigned char InterfaceType,\ . . . unsigned int CtrlPort, ...\ unsigned char RS, ...> and then several blocks of code that I assume are macros: _LCD_TEMPL inline void LCD_FunctionMode(void) {volatile bit rs@CtrlPort.RS = 0; } But I don't understand the exact relationship between the references. Do the <...> brackets define placeholders or list variables within a structure or a function? What does it mean when "_LCD_TEMPL" is placed before inline code definitions? It occurred several times, sometimes with no seeming relationship to the original _LCD_TEMPL definition. Any help or direction to resources will be appreciated, specifically as it applies to using BoostC. I have read the BoostC Compiler Manual several times, but it is by no means comprehensive. A LOT is left out for a beginner like me.
  3. I'd like to see the timer plugin modified so that I can see the instruction count and elapsed time as I step and not just when I click manual stop. This would be similar to what the timer in MPLAB does. It allows you to check critical timing as you go and identify problem sequences AS YOU GO without a dozen manual starts and stops.
  • Create New...