}KWEX^[_Xgß=
¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤
.EEEEE.EEEEEEEP èºÌi}æEE.EEEEE.EEEEE.
¢
This email address is no longer valid.
Original Message:
X-YahooFilteredBulk: 213.221.3.178
Authentication-Results: mta119.mail.dcn.yahoo.com
from=gnu.org; domainkeys=neutral (no sig)
X-Originating-IP: [213.221.3.178]
Return-Path:
Received: from 213.221.3.178 (EHLO yah
When compiling bash with GCC there are a number of alarming-looking
warnings, and several of them could be avoided by minor changes to the
code. For example:
bashline.c:2976: warning: suggest parentheses around assignment used
as truth value
for (passc = 0; c = string[i]; i++)
This could more
Hi,
In bash-3.0, bashline.c gives this warning during compilation:
bashline.c:1418: warning: control may reach end of non-void function
'bash_directory_expansion' being inlined
Since that function is only used once, and in that instance the return
value is not examined---and since there are no r
> When compiling bash with GCC there are a number of alarming-looking
> warnings, and several of them could be avoided by minor changes to the
> code. For example:
>
> bashline.c:2976: warning: suggest parentheses around assignment used
> as truth value
>
> for (passc = 0; c = string[i]; i++)
Hey,
I was wondering if it's possible to make the build-in 'read' command
not always stop at ascii 0.
I've got a file "foo" with "asdf\0qwer\n" in it and when I do:
read x < foo
then
echo ${#x}
always returns 4 instead of 9 or 10 because it stopped after "asdf" at
the null char
I've played
On Tue, Mar 08, 2005 at 03:26:37PM -0600, Davy Durham wrote:
> Hey,
> I was wondering if it's possible to make the build-in 'read' command
> not always stop at ascii 0.
>
> I've got a file "foo" with "asdf\0qwer\n" in it and when I do:
> read x < foo
> then
> echo ${#x}
> always returns 4 in
Davy Durham <[EMAIL PROTECTED]> wrote:
> I was wondering if it's possible to make the build-in 'read' command
> not always stop at ascii 0.
Shell variable values are null-terminated; they can't hold internal
nulls. Even if bash were changed, it's still not possible to pass
such values as argume
Hi,
On Tue, 08 Mar 2005 16:31:15 +0100, Chet Ramey wrote:
...
> > for (passc = 0; c = string[i]; i++)
> >
> > This could more readably be written:
> >
> > for (passc = 0; (c = string[i]) != '\0'; i++)
...
> No, the former is my preferred style. The latter is less readable and
> reduces clar
(BNote: JP stands for Japanese.
(B
(BALERT!!
(BThis e-mail contained one or more virus-infected files and have been rejected.
(B(JP:$B%3%s%T%e!<%?%&%#%k%9$rH/8+$7$^$7$?$N$G!"%a!<%k$NAw?.$rCf;_$7$^$7$?!#(J)
(B
(BThe following attachments were infected:
(B(JP:[EMAIL PROTECTED]<$N$H$*$j!#(
10 matches
Mail list logo
