Hi Gedare,
thanks for your analysis and comments!
> On 22 Oct 2020, at 17:22, Gedare Bloom wrote:
>
> For standalone tools it is really your choice. We would prefer
> adoption of an easily maintained style consistent with some kind of
> sane default.
Given that Promela is based on C with the
Hi Joel,
> On 22 Oct 2020, at 17:13, Joel Sherrill wrote:
>
> Please not the first. Looks like a documentation bug to me.
Phew! I was hoping for that response.
>
> Please feel free to submit a patch and ticket for this.
Sure - thing - so now I will have to look at the how-tos for these ...
On 23/10/20 3:13 am, Joel Sherrill wrote:
> On Thu, Oct 22, 2020 at 6:07 AM Andrew Butterfield
> mailto:andrew.butterfi...@scss.tcd.ie>>
> wrote:
>
> Dear all,
>
> In the RTEMS Software Engineering manual, Sec 6.3.2.1
>
> https://docs.rtems.org/branches/master/eng/coding-80cols.html
Hi Andrew,
On Thu, Oct 22, 2020 at 5:07 AM Andrew Butterfield
wrote:
>
> Dear all,
>
> In the RTEMS Software Engineering manual, Sec 6.3.2.1
> https://docs.rtems.org/branches/master/eng/coding-80cols.html#breaking-long-lines
> it recommends excessively long comments be broken as follows:
>
> /* f
On Thu, Oct 22, 2020 at 6:07 AM Andrew Butterfield <
andrew.butterfi...@scss.tcd.ie> wrote:
> Dear all,
>
> In the RTEMS Software Engineering manual, Sec 6.3.2.1
>
> https://docs.rtems.org/branches/master/eng/coding-80cols.html#breaking-long-lines
> it recommends excessively long comments be broke
Dear all,
In the RTEMS Software Engineering manual, Sec 6.3.2.1
https://docs.rtems.org/branches/master/eng/coding-80cols.html#breaking-long-lines
it recommends excessively long comments be broken as follows:
/* first line
* second line
* third, and in this case last line */
In Sec 6.3.5.2
http
