Maarten Billemont wrote:
On 16 Apr 2012, at 11:43, Linda Walsh wrote:
But it won't work for files below the top level of the library directory.
if I have include system/errno.shh, Source is crippled to not look in PATH.
When there's a slash in the file, it stops searching PATH.
So the
On 16 Apr 2012, at 11:43, Linda Walsh wrote:
>
>
> But it won't work for files below the top level of the library directory.
>
> if I have include system/errno.shh, Source is crippled to not look in PATH.
When there's a slash in the file, it stops searching PATH.
So the reason you're not doi
Maarten Billemont wrote:
On 16 Apr 2012, at 09:54, Maarten Billemont wrote:
On 15 Apr 2012, at 22:52, Linda Walsh wrote:
But I want the syntax
include file.shh
to just 'work', i.e. first time, it would call my include file, which defines
the function...
I'm sorry, tell me again why you do
I have found one more problem:
I'm getting following:
bash -c 'printf "x%+fx\n" -0'
x+0.00x
where it should be:
x-0.00x
This is cause by:
/* round off to the precision */
#define ROUND(d, p) \
(d < 0.) ? \
d - pow_10(-(p)->precision) * 0.5 : \
d +
On 16 Apr 2012, at 09:54, Maarten Billemont wrote:
> On 15 Apr 2012, at 22:52, Linda Walsh wrote:
>>
>> But I want the syntax
>>
>> include file.shh
>>
>> to just 'work', i.e. first time, it would call my include file, which defines
>> the function...
>
> I'm sorry, tell me again why you don't
On 15 Apr 2012, at 22:52, Linda Walsh wrote:
>
> But I want the syntax
>
> include file.shh
>
> to just 'work', i.e. first time, it would call my include file, which defines
> the function...
I'm sorry, tell me again why you don't just write "source file.sh" instead of
having to invent your ow
