Pelles C forum

Pelles C => Feature requests => Topic started by: PhilG57 on February 15, 2026, 02:16:00 PM

Title: Enhanced editor suggestion #2
Post by: PhilG57 on February 15, 2026, 02:16:00 PM
A user selectable (on or off) editor feature to display the status of variables.  Ideally the feature would show whether a variable is local, global, static, described in this file or another file, etc. 

This capability would make it easier locating variables in large multi-file projects and might even help to reduce the number of variables described or defined.  I do love your editor's 'find in files' feature though. 
Title: Re: Enhanced editor suggestion #2
Post by: TimoVJL on February 15, 2026, 02:40:49 PM
Quote from: PhilG57 on February 15, 2026, 02:16:00 PMThis capability would make it easier locating variables in large multi-file projects and might even help to reduce the number of variables described or defined.  I do love your editor's 'find in files' feature though. 
Perhaps a new Add-In for collect some info from an object files ?
Just do it yourself ?

EDIT: also tag-files contains useful info ?
Title: Re: Enhanced editor suggestion #2
Post by: PhilG57 on February 16, 2026, 02:21:59 PM
I have no idea how to do that. Besides, I thought Pelle was looking for something to do.
Title: Re: Enhanced editor suggestion #2
Post by: TimoVJL on February 16, 2026, 04:46:06 PM
https://forum.pellesc.de/index.php?msg=41529 (https://forum.pellesc.de/index.php?msg=41529)

Modify this for a your purposes.
Use pope.exe to examine obj-files for symbols.
Title: Re: Enhanced editor suggestion #2
Post by: PhilG57 on February 20, 2026, 06:41:23 PM
Thanks, but I don't think this is it.  I'm hoping for a capability that, while in the editor, I can know if a particular compiler symbol is defined or not.  A symbol like "_WIN32" or "__32BIT__" or more likely some user symbol defined in the code itself and evaluated (by the preprocessor??) with #ifdef and #ifndef statements.  With this capability I could, while in the editor, know and see which path through the source code the preprocessor and compiler is taking.

I didn't actually look at your suggestion seeing as it referenced .obj (already compiled) files so if I am missing the boat here, please LMK.  Thanks.