Re: [jamboost] Re: Re: Re: Re: PCH support

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-09-10 13:09:14

On Thursday 09 September 2004 03:59 pm, Thorsten Ottosen wrote:
> | But can't we just use full path in --create_pch and --use_pch options?
>
> sure.

Ok.

> | > begin 666 std.zip
> | > M4$L#!!0````(`+),*3'>?/QE-P$``"@$```'`!4`<W1D+FAP<%54"0`#/PA
> | > M03\(0$%5> 0`]0,!`FW2O6X",0P'\/V>`ND>@*5BJCI4';J!!#LRB<.YS<?A
> |
> | Looks like your mailer likes uuecode ;-) Ok, I figured out that by saving
> | an email, editing it a bit, and running uudecode command line tool I
> | still can get the file.
>
> hm...not sure what comes into play. what is the problem with
> uuencode/uudecode?

The only problem is that ordinary attachment can be opened with a single 
click, and uuencoded require saving file, editing it, and running a separate 
tool. Just less convenient.

- Volodya