- Welcome to Pelles C forum.
Pelles C forum
News:
Download Pelles C here: http://www.pellesc.se
Recent posts
#11
Projects developed with Pelles C / JJs Road Rage: The Musical
Last post by rweidner - March 24, 2026, 01:36:22 AMhttps://github.com/xecronix/JJsRoadRage/blob/main/README.md
JJ's Road Rage: The Musical
JJ's Road Rage: The Musical is a small C + raylib arcade driving game built with Pelles C on Windows.
The current build is a one-level, endless-road score attack game with:
What kind of game is this?
You drive on an endless scrolling road, dodge traffic, shoot red enemy cars, avoid hitting civilians, grab power-ups, and chase a higher score.
If you like arcade games, you'll like this game for sure.
JJ's Road Rage: The Musical
JJ's Road Rage: The Musical is a small C + raylib arcade driving game built with Pelles C on Windows.
The current build is a one-level, endless-road score attack game with:
- keyboard controls
- a start screen
- a pause screen
- a high score screen
- an in-dash stereo in fullscreen mode
- 6 music tracks
- 2 power-ups
- local high score saving
What kind of game is this?
You drive on an endless scrolling road, dodge traffic, shoot red enemy cars, avoid hitting civilians, grab power-ups, and chase a higher score.
If you like arcade games, you'll like this game for sure.
#12
Bug reports / TEXTEQU statement freezing Poa...
Last post by Vortex - March 23, 2026, 09:03:13 PMHi Pelle,
This code portion below is freezing Poasm Version 14.00.00 :
MessageBoxA TEXTEQU <MessageBoxA> is not meaningful but this should not lock the assembler.
This code portion below is freezing Poasm Version 14.00.00 :
Code Select
.386
.model flat,stdcall
option casemap:none
ExitProcess PROTO :DWORD
MessageBoxA TEXTEQU <MessageBoxA>
.code
start:
invoke MessageBoxA,0,0,0,0
invoke ExitProcess,0
END start
MessageBoxA TEXTEQU <MessageBoxA> is not meaningful but this should not lock the assembler.
#13
Assembly discussions / Re: Verifying the support of t...
Last post by Vortex - March 23, 2026, 07:51:56 PMAttached is the 64-bit GUI example.
#14
Feature requests / Re: RichEdit 4.1
Last post by John Z - March 23, 2026, 01:13:21 PMThanks Timo!
I've not had a chance to test, still bogged down getting powershell script working to build programs in my BBBBuilder.dll add-in.
John Z
I've not had a chance to test, still bogged down getting powershell script working to build programs in my BBBBuilder.dll add-in.
John Z
#15
Feature requests / Re: Enhanced editor suggestion
Last post by John Z - March 23, 2026, 01:11:06 PMEclipse IDE installation requirements are huge, yet it was a very popular IDE. No Java on my systems 
.
Now superseded by IntelliJ IDEA I understand.
Eclipse IDE has features to use its IDE with PelleC build programs if one really wanted that IDE.
John Z
.Now superseded by IntelliJ IDEA I understand.
Eclipse IDE has features to use its IDE with PelleC build programs if one really wanted that IDE.
John Z
#16
Feature requests / Re: Enhanced editor suggestion...
Last post by John Z - March 23, 2026, 12:51:44 PMQuote from: PhilG57 on March 22, 2026, 04:21:39 PMIt would be nice, if when working on a "workspace" with multiple "projects", various options of the project (compiler level, flags, libraries, link options for libraries, etc.), could be inherited from the workspace. Those project options inherited from the workspace would all be the same for each individual project, while projects needing unique options would specify those in the project's .ppj or whatever file. Thanks.
Not that familiar with the 'workspace' use but I created one with two projects. The workspace file contains none of the project options (from either project) so I can't see how anything would inherit something not existing. Seems this concept it would totally change the way projects themselves and workspaces work.
Alternatively it might be possible to have an Add-In that can select a project mode from one project and replicate it into a different project. This would work similarly to the new Copy Mode feature, except copy from another project rather than copy from an existing mode within the current project.
John Z
#17
Feature requests / Re: Enhanced editor suggestion
Last post by Michele - March 23, 2026, 12:38:47 PMThis is behavior of ECLIPSE IDE, it is a really useful feature! I like it very much.
Nevertheless it requires a grammar checking engine very powerful or the result could even be counterproductive.
And I imagine the POIDE isn't so strong.
Nevertheless it requires a grammar checking engine very powerful or the result could even be counterproductive.
And I imagine the POIDE isn't so strong.
#18
Feature requests / Re: Enhanced editor suggestion
Last post by John Z - March 23, 2026, 12:25:20 PMHi PhilG57,
I don't see this as a good fit with a text editor. You'd have the editor constantly checking every key stroke to see if it was a #DEFINE xxxxx, #DEFINE a 1, #DEFINE macro, or an #undef yyyyy and so on then checking every file, or a list of #ifdef and others, to see if the define/undef was used somewhere then highlighting the use path, which might not be that simple with nested cases (as you mentioned). It would need to not just check C source but all headers and all project ppj configs. It would really bog down the editor with unrelated editing task. Imagine constantly checking 45 source files plus headers...
Even if the editor were to build a list as text is entered of where checks are done like #ifdefs it would need to check the list constantly every time a #... was typed, and not just then as a previously #DEFINE xxxx might be changed at any edit time or somewhere else. Then too if it old existing source code then no one is typing everything so some initialization would need to be done to develop the initial list.
So an Add-IN that can be called ad-hoc to process all the source files and headers seems more reasonable, even though it would be snapshot in time, it could be run as needed.
Add-ins can be written by the user community so you have a path to do it. The editor is only updated by Pelle the developer. I don't think he will will be interested, but just imo.
John Z
I don't see this as a good fit with a text editor. You'd have the editor constantly checking every key stroke to see if it was a #DEFINE xxxxx, #DEFINE a 1, #DEFINE macro, or an #undef yyyyy and so on then checking every file, or a list of #ifdef and others, to see if the define/undef was used somewhere then highlighting the use path, which might not be that simple with nested cases (as you mentioned). It would need to not just check C source but all headers and all project ppj configs. It would really bog down the editor with unrelated editing task. Imagine constantly checking 45 source files plus headers...
Even if the editor were to build a list as text is entered of where checks are done like #ifdefs it would need to check the list constantly every time a #... was typed, and not just then as a previously #DEFINE xxxx might be changed at any edit time or somewhere else. Then too if it old existing source code then no one is typing everything so some initialization would need to be done to develop the initial list.
So an Add-IN that can be called ad-hoc to process all the source files and headers seems more reasonable, even though it would be snapshot in time, it could be run as needed.
Add-ins can be written by the user community so you have a path to do it. The editor is only updated by Pelle the developer. I don't think he will will be interested, but just imo.
John Z
#19
Feature requests / Re: Enhanced editor suggestion...
Last post by TimoVJL - March 22, 2026, 10:41:00 PMMight be possible with Add-In.
Hopefully someone understand a you ideas for it.
Hopefully someone understand a you ideas for it.
#20
Projects developed with Pelles C / Re: Some of my programs were d...
Last post by alderman2 - March 22, 2026, 09:29:39 PMJag har utvecklat ett nytt program:
https://exmag.se/matrosim-ett-program-som-simulerar-reflexfri-matning/
https://exmag.se/matrosim-ett-program-som-simulerar-reflexfri-matning/