Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign

Ceniza's CodeCompletion Project

(1/5) > >>

Ceniza:
I've been thinking that maybe, just maybe, I should publish the code of my preprocessor. Questions are: where should I upload it (CB's svn respository, code.google.com, just a zip file somewhere, ...), and, most importantly, is it really going to be used?

I doubt it's going to be used right away in its current state. Chances are some modifications will be needed and some extra information saved during the process. Perhaps some more optimizations may be required, but it would be, at least, a starting point.

What's a real shame is that the document that explains its development is written only in Spanish. Well, you can always learn a new language, so it shouldn't be a problem either :wink:

JGM:

--- Quote from: Ceniza on February 07, 2009, 10:03:05 am ---What's a real shame is that the document that explains its development is written only in Spanish. Well, you can always learn a new language, so it shouldn't be a problem either :wink:

--- End quote ---

Well people that doesnt know spanish use google translate :D

joubertdj:

--- Quote from: Ceniza on February 07, 2009, 10:03:05 am ---I've been thinking that maybe, just maybe, I should publish the code of my preprocessor. Questions are: where should I upload it (CB's svn respository, code.google.com, just a zip file somewhere, ...), and, most importantly, is it really going to be used?

I doubt it's going to be used right away in its current state. Chances are some modifications will be needed and some extra information saved during the process. Perhaps some more optimizations may be required, but it would be, at least, a starting point.

What's a real shame is that the document that explains its development is written only in Spanish. Well, you can always learn a new language, so it shouldn't be a problem either :wink:

--- End quote ---

We need to start somewhere ... this is basically the only thing I currently want in C::B ... if you could post the code here, maybe we could all have a look? Hell if it does Allegro, correctly then I am satisfied it will work with everything!

ollydbg:
I'm also interested in improving the Code Completion. Especially, pre-process is necessary.
For example:
Now, these code can't be recognized as a function declaration.

--- Code: ---CVAPI(void*)  cvAlloc( size_t size );
--- End code ---
 
because CVAPI is a macro defined by

--- Code: ---  #ifndef CVAPI
    #define CVAPI(rettype) CV_EXTERN_C CV_EXPORTS rettype CV_CDECL
  #endif
--- End code ---
Also, there are macros nested.

So, I think pre-process is complicated.
But why not we borrow code from a general c compiler source code? :D

Ceniza:
With the information you provided, my preprocessor outputs:


--- Quote ---CV_EXTERN_C CV_EXPORTS void * CV_CDECL cvAlloc ( size_t size ) ;
--- End quote ---

I'll have to check the source code first, and try to isolate a few things. Maybe for this weekend I'll be doing that. I also need to find where I put the test for the optimized string type, and put that code along with it. The doxygen generated documentation may be worth uploading too, and the Spanish document for those who can read it.

Let's hope I don't forget...

Navigation

[0] Message Index

[#] Next page