Now that eMOS for AVR is in beta, time to polish off the crystal balls some more. I have a consultant looking at CANLIB for AVR already. I’d think that a robust, fast, small, full-feature TCP/IP stack is high on the list of things we should do. Problem there is there are 4 qualifiers there, and as they usually say, you can get 2 out of 3, or 3 out of 4. So what features would you want in a TCP/IP stack?
A compiler tie-in is that someone suggested that we provide some sort of API so that a program can take a web page HTML with embedded references to C variables, e.g.
…// html stuff …
…. @foo:bar …
where bar is a local variable in foo, and the API would expand the values at runtime. I am not sure what kind of variable reference we can allow yet, but you get the idea. Yay or nay?
Comments and suggestions always welcome. Contact me at richard at imagecraft.com