For the SX chip (a 16C5x clone) and its SASM compiler, I have a macro that
only compiles code for a function if that function is used. And the first
time, it compiles the code, the next time that code is used, it just
compiles the call to it. Huge include file, only the required code is
included. I would guess something like that could be written for MPASM.

---
James.
 
 

> -----Original Message-----
> From: piclist-bounces@mit.edu 
> [mailto:piclist-bounces@mit.edu] On Behalf Of Jan-Erik Soderholm
> Sent: 2005 Feb 10, Thu 05:27
> To: piclist@mit.edu
> Subject: RE: [PIC] A/D Issues
> 
> John J. McDonough wrote :
> 
> > Well, not only that, but if you do the one subroutine per 
> file thing, 
> > when you stuff it all in a library the linker will merrily pull out 
> > only the stuff you need.
> 
> Right, but the major problem with *object* code libraries is 
> that you lose all assembly-time calculations and conditionals 
> and so on. Olin's environment, as an example, would be quite 
> hard to move to a object LIB based build environment.
> 
> What I'd realy liked to see, is *source* code libraries where 
> the assembler would search, extract and include source code 
> "snippets" out of plain text libraries on-the-fly. Not having 
> to have everything in one large INC file.
> 
> B.t.w, how many are realy using object LIB's a lot in their 
> PIC projects ?
> 
> Jan-Erik.
> 
> 
> 
> --
> http://www.piclist.com PIC/SX FAQ & list archive View/change 
> your membership options at 
> http://mailman.mit.edu/mailman/listinfo/piclist
> 


-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist