- Welcome to Pelles C forum.
Pelles C forum
News:
Download Pelles C here: http://www.pellesc.se
Recent posts
#81
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
#82
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.
#83
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
#84
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.
#85
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/
#86
Feature requests / Re: Enhanced editor suggestion...
Last post by Vortex - March 22, 2026, 05:31:47 PMWhile that's an interesting idea, I guess it better to keep simple the project manager of Pelles C.
#87
Feature requests / Enhanced editor suggestion #3
Last post by PhilG57 - 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.
#88
Feature requests / Re: RichEdit 4.1
Last post by TimoVJL - March 22, 2026, 12:13:21 PMQuote from: Pelle on November 30, 2025, 10:03:50 PMApparently there are four versions of Rich Edit:Works in my tests in Windows 11 laptop.
Version 1.0, Riched32.dll, class "RICHEDIT"
Version 2.0, Riched20.dll, class "RichEdit20A"/"RichEdit20W"
Version 3.0, Riched20.dll, class "RichEdit20A"/"RichEdit20W"
Version 4.1, Msftedit.dll, class "RICHEDIT50W"
Not sure who came up with this, but surely strong medication must have been involved...
The next version of the dialog editor will have four RichEdit controls (1, 2, 3, and 5).
#89
Assembly discussions / Re: Saving the volatile regist...
Last post by Vortex - March 22, 2026, 11:04:33 AMAnother example :
Code Select
include SaveRegs.inc
SaveRegs MACRO
mov QWORD PTR [rbp],rcx
mov QWORD PTR [rbp+8],rdx
mov QWORD PTR [rbp+16],r8
mov QWORD PTR [rbp+24],r9
ENDM
.data
msg db 'Hello!',0
msg2 db 'rcx,rdx,r8 and r9 are saved.',0
title db 'MsgBox',0
title2 db 'Macro test',0
.code
start PROC PARMAREA=5*SIZEOF QWORD
; Pass rsp to the procedure main
invoke main,ADDR msg2,ADDR title2,10,20,rsp
invoke ExitProcess,0
start ENDP
main PROC uses rbp r:QWORD,s:QWORD,t:QWORD,u:QWORD,_rsp:QWORD PARMAREA=4*SIZEOF QWORD
mov rbp,_rsp
SaveRegs
_r TEXTEQU <QWORD PTR [rbp]>
_s TEXTEQU <QWORD PTR [rbp+8]>
_t TEXTEQU <QWORD PTR [rbp+16]>
_u TEXTEQU <QWORD PTR [rbp+24]>
invoke MessageBox,0,ADDR msg,ADDR title,0
; The first call to MessageBox destroys rcx,rdx,r8 and r9
invoke MessageBox,0,_r,_s,0
ret
main ENDP
END start
#90
Bug reports / Re: Creating resource with man...
Last post by John Z - March 21, 2026, 10:37:25 AMQuote from: PaoloC13 on March 20, 2026, 11:24:53 AMIntel Celeron N4020 CPU @ 1.10GHz - RAM 4,00 GB
Windows 11 Vers. 23H2
I am amazed that this works - Win 11 23H2 with such limited resources!
John Z