General information
Category:
Coding, syntax & commands
>When I first tried to use them it was a major mess. I didn't 'get' how vfp used them and I was trying to have .h for .prg, .vcx, .scx, this class, that class, etc.. Arggh.
This is how I have been doing it--BUT I have only been using them while writing classes and COM components. So I simply have an include file for each class, and in inheritence situations, I put an #INCLUDE for the parent.h in child.h I handle client components as necessary. In general, if I want to use the Components constants, I put an #INCLUDE for its .h in the client component's .h
Finally, all of them #INCLUDE a standard.h that sits at the top of the project tree, and is available across all projects.
>Now, I just have a single .h file and #include all the rest in there. I haven't had any problems since then.
Where are you placing this? It would simplify things if I used a single .h for the project.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only