Re: Proposed feature: #include inline

I don't like #include in general, but I can't see anything wrong with 
this addition to it.

Anyone else got a good suggestion for an alternate name that makes it very 
clear that this happens at compile time?

Tavis

On Tue, 14 Jul 2009, R. Tyler Ballance wrote:

> I'm not going to write up a CHEP for this just yet, but I came across a
> usecase for `#include inline` version `#include raw` today.
>
> When watching a production server run through a particular template I
> realized that we were using `#include raw` far too much, resulting in a
> large amount of open(2) and read(2) calls (to be expected, duh).
>
> What we *really* want to do however, is an `#include inline` which would
> be processed and the contents of the included file inlined at *compile
> time* instead of raw's inclusion at run time.
>
> Thoughts?
>
> Tavis, if you've no enormous objections, I think this would be a
> reasonable addition.
>
>
> Cheers
>
> -R. Tyler Ballance
> Slide, Inc.
>

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge