[Tdg] Code commit

Graham Wakefield wakefield at mat.ucsb.edu
Sat Mar 3 09:32:14 PST 2007


Since the users will need to include the headers when the link the  
libraries, I think we should keep the number of .h files to a  
minimum.  So various subclasses of memory pools etc. can all be  
declared in a single mmemory_pool.h file.  Perhaps even we might want  
to merge all core headers into a single header for the library  
include, at a later point... if the user wants to statically link,  
then having a complex folder structure with a ton of .h files in the / 
usr/local/include/ isn't very friendly.

But I agree, there seems to be more folder structure than really  
necessary right now.  Simplifying it also simplifies the search path  
settings for VS, since it can't do recursive search. Alex: the IDE  
doesn't abstract away the concept of file BTW, but it does abstract  
away folder structure if you want.

On Mar 3, 2007, at 8:55 AM, Alex Norman wrote:

>
> Well, like I said, I think it is a good idea to have platform  
> dependent code
> separated, but having all the cpp files [per "project" (ie core,  
> audio)] that
> are platform independent in one folder simply makes life easier.   
> Maybe it'll
> also help us keep our code size smaller?  I think, for now, it  
> makes things
> easier, if it becomes a problem later, we can change.  But systems  
> should NOT be
> that large, and the core shouldn't either, we should make sure of  
> that, so there
> won't be that many files to deal with and most people here use some  
> IDE that
> abstracts away the concept of "file" anyways right?  So it doesn't  
> really matter
> to you folks once you get the shit in your IDE.
>
> I agree that nothing is perfect the first time but I can see what  
> is wrong with
> what we have RIGHT NOW and I think we should fix it before we move  
> on.  If that
> in turn causes problems down the line we can fix them then but  
> right now the
> current setup causes problems as I see it.  I understand that  
> you've invested a
> lot of time in the the VS project, but that is no reason to stick  
> with a setup
> that is too compilcated and actually "incorrect" as I see it when  
> we can easily
> change that.  We should change it now before we become too invested  
> in it.  at
> the very least I think we need each system to have its own top  
> level folder and
> to reduce some of the folder redundancy.
>
> -Alex
>
>>
>> rama
>> _______________________________________________
>> Tdg mailing list
>> Tdg at mat.ucsb.edu
>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg
> _______________________________________________
> Tdg mailing list
> Tdg at mat.ucsb.edu
> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg




More information about the Tdg mailing list