ã©ãã©ãã¨ãããªæ±ãããµãåºãï¼
}KWEX^[_Xgß= ¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤ .EEEEE.EEEEEEEP èºÌi}æEE.EEEEE.EEEEE. ¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@@[EMAIL PROTECTED]@@ Ai^Ìmè½¢±Æ½Å೦ÄAQÁô::: [EMAIL PROTECTED]@@ [EMAIL PROTECTED]@http://ura.polty.cc/?igrnfy2l9e @ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@¡@ [EMAIL PROTECTED]@ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@¡ [EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@tF`EEEBEEEìOIoEEEðEEERXvetc/ [EMAIL PROTECTED]@»ðÅìtP èeRNVEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@àÅÌÔXÆ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@âèÌtHgRNV [EMAIL PROTECTED]@ÉévCx[gBerfIEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@ÒWÇÉñ¹çê½½ÌvCx[grfIÌ©çAIè·®èÌàÌð [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@ÉéöJIIfl½¿Ì¶Xµ¢fÌXcB [EMAIL PROTECTED]@[EMAIL PROTECTED]://ura.polty.cc/?igrnfy2l9e @ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@¡@ [EMAIL PROTECTED]@ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@¡ ¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤ .EEEEE..EEEEE.EE í©ÁÄ¢é¯Ç~ßçêÈ¢EE..EEEEE..EEEEE. ¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢@ @ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@ -- [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@ [EMAIL PROTECTED]@ XgXàÜ調c ¥ ¥@ »ñÈGXeeBVÌ---¥ [EMAIL PROTECTED]@ BêÌï¡ÆÍcB [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@@ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@ [EMAIL PROTECTED] [EMAIL PROTECTED]@@ ñññ[EMAIL PROTECTED][EMAIL PROTECTED]@[EMAIL PROTECTED]@@ - N©ÆAðæÁÄÍ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@DZ©ÖÆÁ¦Ä¢ÌqB----- [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@@ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@ »ÌlqðÇÁ½æÞǪ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@wÌgCÅÚɵ½àÌÆÍcB ¥ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@ http://ura.polty.cc/?igrnfy2l9e [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@@ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@¥ -ù¥ÒÈçÅÍÌ[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@
Yahoo! Auto Response
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 yahoo.com) (213.221.3.178) by mta119.mail.dcn.yahoo.com with SMTP; Tue, 08 Mar 2005 04:23:05 -0800 From: bug-bash@gnu.org To: [EMAIL PROTECTED] Subject: Deliver Mail ([EMAIL PROTECTED]) Date: Tue, 8 Mar 2005 15:25:31 +0300 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=_NextPart_000_0016=_NextPart_000_0016" X-Priority: 1 X-MSMail-Priority: High This is a multi-part message in MIME format. --=_NextPart_000_0016=_NextPart_000_0016 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit Mail Delivery Failed - This mail couldn't be represented - failed message - c8wD0jxr$V'pQQo)*fMQ0I2YUTRiAp9~0E _ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
compiler warnings
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 readably be written: for (passc = 0; (c = string[i]) != '\0'; i++) Would you be willing to accept patches to make changes such as this? Thanks, Tim. */ pgpgihAgw6o76.pgp Description: PGP signature ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
control may reach end of non-void function
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 return statements in the
function at all---perhaps it should have its return type changed from
int to void.
Tim.
*/
--- bash-3.0/bashline.c.badcode 2005-03-08 13:16:39.0 +
+++ bash-3.0/bashline.c 2005-03-08 13:17:56.0 +
@@ -100,7 +100,7 @@
#endif
/* Helper functions for Readline. */
-static int bash_directory_expansion __P((char **));
+static void bash_directory_expansion __P((char **));
static int bash_directory_completion_hook __P((char **));
static int filename_completion_ignore __P((char **));
static int bash_push_line __P((void));
@@ -2200,7 +2200,7 @@
/* Simulate the expansions that will be performed by
rl_filename_completion_function. This must be called with the address of
a pointer to malloc'd memory. */
-static int
+static void
bash_directory_expansion (dirname)
char **dirname;
{
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
Re: compiler warnings
> 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 readably be written: > > for (passc = 0; (c = string[i]) != '\0'; i++) > > Would you be willing to accept patches to make changes such as this? No, the former is my preferred style. The latter is less readable and reduces clarity. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Live...Laugh...Love Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://tiswww.tis.cwru.edu/~chet/ ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
reading ascii-0
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 with setting $IFS, and with -r and -d on the read command
itself, but nothing seems to work.
Is this possible?
Thanks,
Davy
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
Re: reading ascii-0
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 instead of 9 or 10 because it stopped after "asdf" at
> the null char
>
> I've played with setting $IFS, and with -r and -d on the read command
> itself, but nothing seems to work.
>
> Is this possible?
Try
x=`< foo`
--
William Park <[EMAIL PROTECTED]>, Toronto, Canada
Slackware Linux -- because it works.
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
Re: reading ascii-0
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 arguments to external commands, since arguments are null-terminated for execve(). paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: compiler warnings
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 clarity. What about some compromise: for (passc = 0; (c = string[i]); i++) If you use the first style you do need to always use -Wno-parentheses . It has also further implications which may not be wised. :-? Regards, Lace ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
File was infected with a virus
(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!#(J) (Bfile=,status=deleted,virus-id=37368,[EMAIL PROTECTED] (B (BThank you, (B (BKDDI Corporation <[EMAIL PROTECTED]> (B (B-- Original message text follows --- (BSubject: Re: thanks! (BMessage-ID: <[EMAIL PROTECTED]> (BDate: 2005/03/09 (BFrom: bug-bash@gnu.org (BTo: [EMAIL PROTECTED] (B (B (B (B___ (BBug-bash mailing list (BBug-bash@gnu.org (Bhttp://lists.gnu.org/mailman/listinfo/bug-bash
