Cannot construct class definition - just inheritence - intermittent

[jhood]

I think that there is a problem when IDLDoc tries to construct a class definition for a class that just inherits. For example:

pro star_course_vs_time_receiver_request`__`define 
  struct = { star_course_vs_time_receiver_request, $ 
             inherits star_single_receiver_request } 
end

Produces the following error:

IDLDOC: cannot construct definition for class star_course_vs_time_receiver_request

This doesn't seem to happen all of the time, but I can't find a consistent thread to indicate when this problem occurs and when it doesn't.

[mgalloy]

Is the definition of star_single_receiver_request available? i.e., is star_single_receiver_request__define.pro in the !path? I got exactly the same error you mention when I hadn't created star_single_receiver_request__define.pro yet, but it works fine with star_single_receiver_request__define.pro in the same directory as star_course_vs_time_receiver_request__define.pro or somewhere else in my !path.

[jhood]

Yes all of the superclasses are in the path for the example. The code itself executes properly. Until a short while ago, all errors of this form (5 over the entire code base) were in depricated code, so I didn't pay much attention. In the last month, I got four new errors of this form, so I decided to try and solve it. It may be something silly that I am doing on my end, but I can't see what the problem would be.

Some of the code doesn't nicely auto-compile and we put includes (@filename) at the top of some applications to make sure that the right code is compiled in order. This is mainly because we will put several functions in the same file. It looks like you might require function calls, etc. to properly compile automatically in order for IDLDoc to understand them. This might be the root of the problem, though in this case the classes are in their own file and properly named to compile automatically. I will look to see if some other function call (i.e. one with a keyword that isn't already defined) could be causing a compile to fail. Would this cause the error?