Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Obsolete PWMRANGE still defined as LITERAL1 in keywords.txt #8447

Merged
merged 1 commit into from
Jan 11, 2022
Merged

Obsolete PWMRANGE still defined as LITERAL1 in keywords.txt #8447

merged 1 commit into from
Jan 11, 2022

Conversation

Paraphraser
Copy link
Contributor

PWMRANGE was defined up until v2.7.4:

$ cd ~/Library/Arduino15/packages/esp8266/hardware/esp8266
$ grep -R "PWMRANGE" 2.7.4
2.7.4/keywords.txt:PWMRANGE	LITERAL1
2.7.4/tests/host/common/Arduino.h:#define PWMRANGE 1023
2.7.4/cores/esp8266/core_esp8266_wiring_pwm.cpp:static int32_t analogScale = PWMRANGE;
2.7.4/cores/esp8266/Arduino.h:#define PWMRANGE 1023

The define was removed in favour of the Arduino standard value of 255
but the keyword coloring was left behind:

$ cd ~/Library/Arduino15/packages/esp8266/hardware/esp8266
$ grep -R "PWMRANGE" 3.0.2
3.0.2/keywords.txt:PWMRANGE	LITERAL1

In the Arduino IDE, the coloring makes it look like PWMRANGE still
exists, when it doesn't, which is confusing.

Signed-off-by: Phill Kelley pmk.57t49@lgosys.com

PWMRANGE was defined up until v2.7.4:

```
$ cd ~/Library/Arduino15/packages/esp8266/hardware/esp8266
$ grep -R "PWMRANGE" 2.7.4
2.7.4/keywords.txt:PWMRANGE	LITERAL1
2.7.4/tests/host/common/Arduino.h:#define PWMRANGE 1023
2.7.4/cores/esp8266/core_esp8266_wiring_pwm.cpp:static int32_t analogScale = PWMRANGE;
2.7.4/cores/esp8266/Arduino.h:#define PWMRANGE 1023
```

The define was removed in favour of the Arduino standard value of 255
but the keyword coloring was left behind:

```
$ cd ~/Library/Arduino15/packages/esp8266/hardware/esp8266
$ grep -R "PWMRANGE" 3.0.2
3.0.2/keywords.txt:PWMRANGE	LITERAL1
```

In the Arduino IDE, the coloring makes it look like PWMRANGE still
exists, when it doesn't, which is confusing.

Signed-off-by: Phill Kelley <pmk.57t49@lgosys.com>
Copy link
Collaborator

@earlephilhower earlephilhower left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants