Currently the nesT typer does not understand const so writing "const correct" code is not possible in nesT. This particularly causes problems for declarations that are being shared between nesT and nesC. For example, consider the nesC module
Because the nesT typer ignores const it will allow values to be assigned to the buffer passed to process_buffer. The invoking nesC code won't expect this. Moreover when the specialized nesT module is compiled by the nesC compiler, type errors will be reported at that time.
Currently the nesT typer does not understand const so writing "const correct" code is not possible in nesT. This particularly causes problems for declarations that are being shared between nesT and nesC. For example, consider the nesC module
Suppose it is wired to the following nesT module
Because the nesT typer ignores const it will allow values to be assigned to the buffer passed to
process_buffer.
The invoking nesC code won't expect this. Moreover when the specialized nesT module is compiled by the nesC compiler, type errors will be reported at that time.