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
 Technical Support
 VAX and C/C++ files with non-standard extensions
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

JerryEvans
New Member

3 Posts

Posted - Nov 02 2009 :  12:08:33 PM  Show Profile  Reply with Quote
I'm working on a project that has a Windows/C# GUI and a embedded Linux C/C++ server. As Win32 Codeblocks/Dev++ are not VAX hosts I find my productivity is hugely reduced. I can see how to trick VS into building the Linux source files with the GCC 68K cross-compiler, by creating a new filter/tool chain etc. Question is this: If I have a set of source files with .68k.c++ and .68k.h extensions (for example) how can I persuade VAX to parse+browse as usual?

BTW mightily impressed to find that VAX handles the entire Chromium project without any complaints. Makes making sense of the codebase 1000 times easier. Astounding product, all is needs is C++ enum refactoring!

Thx

Jerry

accord
Whole Tomato Software

United Kingdom
3287 Posts

Posted - Nov 02 2009 :  3:37:55 PM  Show Profile  Reply with Quote
This link will help you:

http://docs.wholetomato.com?W328

>Astounding product, all is needs is C++ enum refactoring!
You mean a new refactoring command? If you do, can you please explain your idea?
Go to Top of Page

JerryEvans
New Member

3 Posts

Posted - Nov 03 2009 :  07:35:46 AM  Show Profile  Reply with Quote
quote:


http://docs.wholetomato.com?W328




Thanks. I think that'll do it.

quote:

You mean a new refactoring command? If you do, can you please explain your idea?



Yes - since enumerations are generally seen as a good thing they tend to get used on a wide and frequent basis. What would be very useful is to be able to change an enumeration namespace and to combine enumeration from one space into another.

i.e

class control { enum settings { off, slow, full }; };

refactor so control::settings is moved out of the control class scope

enum settings { off, slow, full };

class control { };

control::settings::off -> settings::off

etc.
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18943 Posts

Posted - Nov 04 2009 :  3:32:14 PM  Show Profile  Reply with Quote
How often do you want to do something like this? My concern is that this is a special case for a more general operation "move X from scope A to scope B", which raises all sorts of complications.

Personally I use enum's a lot, but I have hardly ever wanted to move them around like 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  Reply to Topic
 Printer Friendly
Jump To:
© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000