Viktor Szakáts wrote:
> 
> Maybe can be done to some extent, but I'm nearly sure 
> this can never be a fully generic process. With most libs 
> you need to understand the background logic which you can 
> rarely deduct from plain headers. If you're through that, 
> you need to map types, which even for the simpler cases 
> would require a complete C preprocessor and language 
> parser to work with all projects. You also need to know 
> what to parse and what to ignore, otherwise you will end 
> up struggling with rare exceptions, no one would ever 
> need anyway.
> 

Well described.
No parser can cater to all libraries.



> This horizon is so wide that I prefer to keep it 
> QT specific. I even hope someone can take it from this 
> stage (Pritpal I hope).
> 

I am looking at it, but right now casually, devided in hbIDE and hbQT.
Sure I will take over. Please keep up.

Yesterday I started generator3 to base Przemek code through 
.qth concept, but then immediately dropped because of time constraints.
Right now, probably, it is better for the project is to raise hbIDE to 
some level, keeping in view the immense user interest.

But surely I will take over.

-----
     enjoy hbIDEing...
        Pritpal Bedi 
http://hbide.vouch.info/
-- 
View this message in context: 
http://n2.nabble.com/SF-net-SVN-harbour-project-14330-trunk-harbour-tp4895981p4896538.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to