# P5.js bug report (semicolons)

**URL:** https://discourse.processing.org/t/p5-js-bug-report-semicolons/22542
**Category:** p5.js
**Created:** [July 10, 2020, 7:53pm UTC](https://discourse.processing.org/t/p5-js-bug-report-semicolons/22542 "2020-07-10T19:53:52Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![DavidMatuszek](https://avatars.discourse-cdn.com/v4/letter/d/d2c977/32.png) [@DavidMatuszek](https://discourse.processing.org/u/DavidMatuszek)
#### Post date: [July 10, 2020, 7:53pm UTC](https://discourse.processing.org/t/p5-js-bug-report-semicolons/22542/1 "2020-07-10T19:53:52Z")

</div>

JavaScript does not require semicolons at the end of lines. For the most part, p5.js does not require semicolons at the end of lines.

Nevertheless, it appears that lines not ending in semicolons are being counted as errors “under the hood.” Given a sufficiently long program, p5.js will report “Too many errors,” and provide a display with “Missing semicolon” on each previous line. The limit appears to be around 100 semicolon-free lines.

It is easy to adjust exactly where this error occurs by adding or deleting semicolons.

Mac OS Mohave, 10.14.6  
Processing 3.5.4

 ![too many errors](https://canada1.discourse-cdn.com/flex036/uploads/processingfoundation1/original/2X/3/36111b7fabdd608ac82476f00f13f580fdb8a92b.png)

---

<div class="post-metadata">

### Author: ![ARNAV\_A\_GUPTA](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/arnav_a_gupta/32/9660_2.png) [@ARNAV\_A\_GUPTA](https://discourse.processing.org/u/ARNAV_A_GUPTA)
#### Post date: [July 11, 2020, 12:25pm UTC](https://discourse.processing.org/t/p5-js-bug-report-semicolons/22542/2 "2020-07-11T12:25:00Z")

</div>

> [@DavidMatuszek](#):
>
> JavaScript does not require semicolons at the end of lines. For the most part, p5.js does not require semicolons at the end of lines.

who said that?? Javascript require semicolons at the end…

---

<div class="post-metadata">

### Author: ![ARNAV\_A\_GUPTA](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/arnav_a_gupta/32/9660_2.png) [@ARNAV\_A\_GUPTA](https://discourse.processing.org/u/ARNAV_A_GUPTA)
#### Post date: [July 11, 2020, 12:38pm UTC](https://discourse.processing.org/t/p5-js-bug-report-semicolons/22542/3 "2020-07-11T12:38:34Z")

</div>

anyways, welcome to the processing community… 🙂🙂🙂🙂

---

<div class="post-metadata">

### Author: ![DavidMatuszek](https://avatars.discourse-cdn.com/v4/letter/d/d2c977/32.png) [@DavidMatuszek](https://discourse.processing.org/u/DavidMatuszek)
#### Post date: [July 11, 2020, 3:03pm UTC](https://discourse.processing.org/t/p5-js-bug-report-semicolons/22542/4 "2020-07-11T15:03:40Z")

</div>

Actually, JavaScript automatically inserts semicolons, so the programmer does not have to. I generally do in JS, but not in p5.js.

I wondered if I would get the same error with a JavaScript program longer than 100 lines, in which case it would be a JavaScript problem, rather than a p5.js problem. So I took an existing 850 line JS program and removed all the semicolons from it. It continues to work without errors.

Thanks for the welcome. Processing is great!

---

<div class="post-metadata">

### Author: ![ARNAV\_A\_GUPTA](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/arnav_a_gupta/32/9660_2.png) [@ARNAV\_A\_GUPTA](https://discourse.processing.org/u/ARNAV_A_GUPTA)
#### Post date: [July 16, 2020, 6:24am UTC](https://discourse.processing.org/t/p5-js-bug-report-semicolons/22542/5 "2020-07-16T06:24:03Z")

</div>

YUP; IT’S GREATEST FOR A GREAT. I’ve not used any js as such, only p5 and from that I thought, it was compulsory

---

<div class="post-metadata">

### Author: ![Pr0tonX](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/pr0tonx/32/2590_2.png) [@Pr0tonX](https://discourse.processing.org/u/Pr0tonX)
#### Post date: [July 16, 2020, 7:48pm UTC](https://discourse.processing.org/t/p5-js-bug-report-semicolons/22542/6 "2020-07-16T19:48:04Z")

</div>

It seems to be an error from the Processing editor so. The warn should not be repeted to avoid it : semicolons are as you said not compulsory in js, but remains a good practice !
