Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Feature Requests
 Automatically generate correct #include
 New Topic  Topic Locked
 Printer Friendly
Author Previous Topic Topic Next Topic  

fmaddin
New Member

6 Posts

Posted - Aug 21 2004 :  4:44:54 PM  Show Profile

Alt-G is great to find what header a symbol is defined so you can know what header to include. If VA-X knows this info, it could automatically add the correct #include on request. I wouldn't care if it didn't get it right 100% of the time.

-frank

WannabeeDeveloper
Tomato Guru

Germany
775 Posts

Posted - Aug 22 2004 :  06:44:29 AM  Show Profile
Problem here is:
MAX_PATH is defined in windef.h

windef.h is included in windows.h

Same goes for several functions. How long will you wait for VAX finding the correct #include buried down in the various headers?

Go to Top of Page

Cezariusz
Tomato Guru

Poland
244 Posts

Posted - Aug 22 2004 :  08:56:52 AM  Show Profile
Stefan,
As Frank says "I wouldn't care if it didn't get it right 100% of the time". For example NetBeans in case of ambiguity presents a list of possible choices. It could work at least for simple cases, for example for classes declared in the current project.

Cezariusz Marek
https://midicat.net/
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18939 Posts

Posted - Aug 23 2004 :  3:07:53 PM  Show Profile
this has been asked before, and WT's comment was that if VAX inserts the wrong header, even occasionally, this is very bad!

however, offering a suggestion, or a list of possible headers sounds good to me so long as it is the user to says which header to include, rather than VAX, it shouldnt be a problem.

case=226

zen is the art of being at one with the two'ness
Go to Top of Page

Uniwares
Tomato Guru

Portugal
2321 Posts

Posted - Aug 24 2004 :  09:22:41 AM  Show Profile
Another problem will be where to insert this line. At the begining of the file? After a file comment header if it exists? After the sometimes used "#ifdef _THISFILEINCLUDEDALREADY_" line? After any already existing "#include"? What about dependencies in existing included files?
I think it might be the best to just put the line in the clipboard so the user can paste it where ever appropriate.
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18939 Posts

Posted - Aug 24 2004 :  4:46:09 PM  Show Profile
very good point, i have updated the case with this

zen is the art of being at one with the two'ness
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Topic Locked
 Printer Friendly
Jump To:
© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000