Nabble - clisp-devel

clisp-cvs Digest, Vol 44, Issue 9

2009-12-17T04:04:45Z

Re: clisp: cvs --> hg

2009-12-16T23:39:56Z

2009/12/16 Sam Steingold <sds@...>:
> Sam Steingold wrote:
>> I would like to convert the clisp cvs repository to hg (mercurial).
>> Any objections?
>
> One more argument for hg: "hg bisect"

There's also git bisect and svn-bisect.

I'm using svn and git mainly.
hg and darcs works for me, but I'm not pretty familiar with it.
git is hard to learn, hg is easier.

I have to use git for perl now, but I prefer svn for all other
projects because it's easier, centralized and I can work over a proxy.
man 5 hgrc => http_proxy, so no problem for me.

git is the future though.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

Re: clisp: cvs --> hg

2009-12-16T11:21:02Z

Sam Steingold wrote:
> I would like to convert the clisp cvs repository to hg (mercurial).
> Any objections?

One more argument for hg: "hg bisect"

bisect [-gbsr] [-c CMD] [REV]

This command helps to find changesets which introduce problems.
To use, mark the earliest changeset you know exhibits the prob-
lem as bad, then mark the latest changeset which is free from
the problem as good. Bisect will update your working directory
to a revision for testing (unless the -U/--noupdate option is
specified). Once you have performed tests, mark the working
directory as good or bad, and bisect will either update to
another candidate changeset or announce that it has found the
bad revision.

As a shortcut, you can also use the revision argument to mark a
revision as good or bad without checking it out first.

If you supply a command, it will be used for automatic bisec-
tion. Its exit status will be used to mark revisions as good or
bad: status 0 means good, 125 means to skip the revision, 127
(command not found) will abort the bisection, and any other
non-zero exit status means the revision is bad.

options:

-r, --reset
reset bisect state

-g, --good
mark changeset good

-b, --bad
mark changeset bad

-s, --skip
skip testing changeset

-c, --command
use command to check changeset state

-U, --noupdate
do not update to target

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

clisp-cvs Digest, Vol 44, Issue 8

2009-12-15T04:04:51Z

[ clisp-Bugs-2913228 ] wrong version of libsigsegv?

2009-12-14T06:51:37Z

Bugs item #2913228, was opened at 2009-12-12 06:26
Message generated for change (Comment added) made by sds
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2913228&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: build problems
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: titanium (titanium_geek)
>Assigned to: Sam Steingold (sds)
Summary: wrong version of libsigsegv?

Initial Comment:
I downloaded CLISP 2.48 from sourceforge.net on the 12th of December 2009, and attempted to compile it on my Intel Core2duo macbook (OS X 10.5.8). I Have XCode installed.

The ./configure file gave me the wrong version of libsigsegv, I think.
libsigsegv: no, consider installing GNU libsigsegv

Please install libsigsegv like this:
mkdir tools; cd tools; prefix=`pwd`/i386-apple-darwin9.8.0
wget http://ftp.gnu.org/pub/gnu/libsigsegv/libsigsegv-2.6.tar.gz
tar xfz libsigsegv-2.6.tar.gz
cd libsigsegv-2.6
./configure --prefix=${prefix} && make && make check && make install
cd ../..
rm -f src/config.cache
./configure --with-libsigsegv-prefix=${prefix}

As you can see libsigsegv is 2.6, however when I followed instructions and emailed Bruno this line: libsigsegv: i386-apple-darwin9.8.0 | yes | yes | 2.6
he responded that libsigsegv is now at version 2.8 so perhaps this needs to be updated.

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2009-12-14 09:51

Message:
thank you for your bug report.
the bug has been fixed in the CVS tree.
you can either wait for the next release (recommended)
or check out the current CVS tree (see http://clisp.cons.org)
and build CLISP from the sources (be advised that between
releases the CVS tree is very unstable and may not even build
on your platform).

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2913228&group_id=1355

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

[ clisp-Bugs-2913228 ] wrong version of libsigsegv?

2009-12-12T03:31:49Z

Bugs item #2913228, was opened at 2009-12-12 22:26
Message generated for change (Settings changed) made by titanium_geek
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2913228&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: build problems
Status: Open
Resolution: None
>Priority: 5
Private: No
Submitted By: titanium (titanium_geek)
Assigned to: Nobody/Anonymous (nobody)
Summary: wrong version of libsigsegv?

Initial Comment:
I downloaded CLISP 2.48 from sourceforge.net on the 12th of December 2009, and attempted to compile it on my Intel Core2duo macbook (OS X 10.5.8). I Have XCode installed.

The ./configure file gave me the wrong version of libsigsegv, I think.
libsigsegv: no, consider installing GNU libsigsegv

Please install libsigsegv like this:
mkdir tools; cd tools; prefix=`pwd`/i386-apple-darwin9.8.0
wget http://ftp.gnu.org/pub/gnu/libsigsegv/libsigsegv-2.6.tar.gz
tar xfz libsigsegv-2.6.tar.gz
cd libsigsegv-2.6
./configure --prefix=${prefix} && make && make check && make install
cd ../..
rm -f src/config.cache
./configure --with-libsigsegv-prefix=${prefix}

As you can see libsigsegv is 2.6, however when I followed instructions and emailed Bruno this line: libsigsegv: i386-apple-darwin9.8.0 | yes | yes | 2.6
he responded that libsigsegv is now at version 2.8 so perhaps this needs to be updated.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2913228&group_id=1355

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

[ clisp-Bugs-2913228 ] wrong version of libsigsegv?

2009-12-12T03:31:23Z

Bugs item #2913228, was opened at 2009-12-12 22:26
Message generated for change (Settings changed) made by titanium_geek
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2913228&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
>Group: build problems
Status: Open
Resolution: None
>Priority: 4
Private: No
Submitted By: titanium (titanium_geek)
Assigned to: Nobody/Anonymous (nobody)
Summary: wrong version of libsigsegv?

Initial Comment:
I downloaded CLISP 2.48 from sourceforge.net on the 12th of December 2009, and attempted to compile it on my Intel Core2duo macbook (OS X 10.5.8). I Have XCode installed.

The ./configure file gave me the wrong version of libsigsegv, I think.
libsigsegv: no, consider installing GNU libsigsegv

Please install libsigsegv like this:
mkdir tools; cd tools; prefix=`pwd`/i386-apple-darwin9.8.0
wget http://ftp.gnu.org/pub/gnu/libsigsegv/libsigsegv-2.6.tar.gz
tar xfz libsigsegv-2.6.tar.gz
cd libsigsegv-2.6
./configure --prefix=${prefix} && make && make check && make install
cd ../..
rm -f src/config.cache
./configure --with-libsigsegv-prefix=${prefix}

As you can see libsigsegv is 2.6, however when I followed instructions and emailed Bruno this line: libsigsegv: i386-apple-darwin9.8.0 | yes | yes | 2.6
he responded that libsigsegv is now at version 2.8 so perhaps this needs to be updated.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2913228&group_id=1355

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

[ clisp-Bugs-2913228 ] wrong version of libsigsegv?

2009-12-12T03:26:23Z

Bugs item #2913228, was opened at 2009-12-12 22:26
Message generated for change (Tracker Item Submitted) made by titanium_geek
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2913228&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: titanium (titanium_geek)
Assigned to: Nobody/Anonymous (nobody)
Summary: wrong version of libsigsegv?

Initial Comment:
I downloaded CLISP 2.48 from sourceforge.net on the 12th of December 2009, and attempted to compile it on my Intel Core2duo macbook (OS X 10.5.8). I Have XCode installed.

The ./configure file gave me the wrong version of libsigsegv, I think.
libsigsegv: no, consider installing GNU libsigsegv

Please install libsigsegv like this:
mkdir tools; cd tools; prefix=`pwd`/i386-apple-darwin9.8.0
wget http://ftp.gnu.org/pub/gnu/libsigsegv/libsigsegv-2.6.tar.gz
tar xfz libsigsegv-2.6.tar.gz
cd libsigsegv-2.6
./configure --prefix=${prefix} && make && make check && make install
cd ../..
rm -f src/config.cache
./configure --with-libsigsegv-prefix=${prefix}

As you can see libsigsegv is 2.6, however when I followed instructions and emailed Bruno this line: libsigsegv: i386-apple-darwin9.8.0 | yes | yes | 2.6
he responded that libsigsegv is now at version 2.8 so perhaps this needs to be updated.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2913228&group_id=1355

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

clisp-cvs Digest, Vol 44, Issue 7

2009-12-11T04:04:33Z

Send clisp-cvs mailing list submissions to
clisp-cvs@...

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/clisp-cvs
or, via email, send a message with subject or body 'help' to
clisp-cvs-request@...

You can reach the person managing the list at
clisp-cvs-owner@...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of clisp-cvs digest..."

CLISP CVS commits for today

Today's Topics:

1. clisp/modules/rawsock configure.in,1.33,1.34
rawsock.c,1.129,1.130 (Sam Steingold)
2. clisp/src ChangeLog,1.7218,1.7219 (Sam Steingold)
3. clisp/src ChangeLog, 1.7219, 1.7220 compiler.lisp, 1.354,
1.355 defs1.lisp, 1.75, 1.76 (Sam Steingold)
4. clisp/doc impbody.xml,1.582,1.583 impent.xml,1.362,1.363
(Sam Steingold)

----------------------------------------------------------------------

Message: 1
Date: Thu, 10 Dec 2009 14:58:39 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock configure.in,1.33,1.34
rawsock.c,1.129,1.130
To: clisp-cvs@...
Message-ID: <E1NIkTX-0000Zh-0q@...>

Update of /cvsroot/clisp/clisp/modules/rawsock
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv2184/modules/rawsock

Modified Files:
configure.in rawsock.c
Log Message:
* modules/rawsock/rawsock.c: include <linux/netlink.h> when present
(check_socket_protocol): add NETLINK_*
* modules/rawsock/configure.in: check for <linux/netlink.h>

Index: rawsock.c
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/rawsock.c,v
retrieving revision 1.129
retrieving revision 1.130
diff -u -d -r1.129 -r1.130
--- rawsock.c 3 Dec 2009 21:03:58 -0000 1.129
+++ rawsock.c 10 Dec 2009 14:58:36 -0000 1.130
@@ -38,6 +38,9 @@
#if defined(HAVE_LINUX_IF_PACKET_H)
# include <linux/if_packet.h>
#endif
+#if defined(HAVE_LINUX_NETLINK_H)
+# include <linux/netlink.h>
+#endif
#if defined(HAVE_NET_IF_H)
# include <net/if.h>
#endif
@@ -635,6 +638,12 @@
IPPROTO-ICMPV6 IPPROTO-DSTOPTS IPPROTO-NONE \
IPPROTO-RSVP IPPROTO-GRE IPPROTO-PIM IPPROTO-COMP \
NSPROTO-IPX NSPROTO-SPX NSPROTO-SPXII \
+ NETLINK_ROUTE NETLINK_USERSOCK NETLINK_FIREWALL NETLINK_INET_DIAG \
+ NETLINK_NFLOG NETLINK_XFRM NETLINK_SELINUX NETLINK_ISCSI \
+ NETLINK_AUDIT NETLINK_FIB_LOOKUP NETLINK_CONNECTOR \
+ NETLINK_NETFILTER NETLINK_IP6_FW NETLINK_DNRTMSG \
+ NETLINK_KOBJECT_UEVENT NETLINK_GENERIC NETLINK_SCSITRANSPORT \
+ NETLINK_ECRYPTFS \
ETH-P-LOOP ETH-P-PUP ETH-P-PUPAT ETH-P-IP ETH-P-X25 ETH-P-ARP \
ETH-P-BPQ ETH-P-IEEEPUP ETH-P-IEEEPUPAT ETH-P-DEC ETH-P-DNA-DL \
ETH-P-DNA-RC ETH-P-DNA-RT ETH-P-LAT ETH-P-DIAG ETH-P-CUST \

Index: configure.in
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/configure.in,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -d -r1.33 -r1.34
--- configure.in 2 Sep 2009 23:17:12 -0000 1.33
+++ configure.in 10 Dec 2009 14:58:36 -0000 1.34
@@ -13,6 +13,7 @@
BOLD_MSG([Rawsock (Headers)])
CL_TCPCONN
AC_CHECK_HEADERS([sys/socket.h linux/if_packet.h netdb.h sys/uio.h \
+linux/netlink.h \
sys/types.h sys/ioctl.h errno.h stropts.h poll.h sys/un.h ifaddrs.h unistd.h])
AC_CHECK_HEADERS([net/if.h],[],[],[
#if defined(HAVE_SYS_TYPES_H)

------------------------------

Message: 2
Date: Thu, 10 Dec 2009 14:58:39 +0000
From: Sam Steingold <sds@...>
Subject: clisp/src ChangeLog,1.7218,1.7219
To: clisp-cvs@...
Message-ID: <E1NIkTX-0000Zn-IA@...>

Update of /cvsroot/clisp/clisp/src
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv2184/src

Modified Files:
ChangeLog
Log Message:
* modules/rawsock/rawsock.c: include <linux/netlink.h> when present
(check_socket_protocol): add NETLINK_*
* modules/rawsock/configure.in: check for <linux/netlink.h>

Index: ChangeLog
===================================================================
RCS file: /cvsroot/clisp/clisp/src/ChangeLog,v
retrieving revision 1.7218
retrieving revision 1.7219
diff -u -d -r1.7218 -r1.7219
--- ChangeLog 2 Dec 2009 23:03:11 -0000 1.7218
+++ ChangeLog 10 Dec 2009 14:58:36 -0000 1.7219
@@ -1,3 +1,9 @@
+2009-12-08 Sam Steingold <sds@...>
+
+ * modules/rawsock/rawsock.c: include <linux/netlink.h> when present
+ (check_socket_protocol): add NETLINK_*
+ * modules/rawsock/configure.in: check for <linux/netlink.h>
+
2009-12-02 Sam Steingold <sds@...>

* modules/rawsock/demos/sniffer.lisp: add a demo

------------------------------

Message: 3
Date: Thu, 10 Dec 2009 21:41:11 +0000
From: Sam Steingold <sds@...>
Subject: clisp/src ChangeLog, 1.7219, 1.7220 compiler.lisp, 1.354,
1.355 defs1.lisp, 1.75, 1.76
To: clisp-cvs@...
Message-ID: <E1NIql6-0003PN-0S@...>

Update of /cvsroot/clisp/clisp/src
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv13074/src

Modified Files:
ChangeLog compiler.lisp defs1.lisp
Log Message:
when compiling REQUIRE, if the module is not found (e.g., it is a
dynamic module), call REQUIRE right away, at compile time.
* defs1.lisp (augment-load-path, load-path-augmentations)
(with-augmented-load-path): extracted from require
(require): use with-augmented-load-path
* compiler.lisp (load-or-compile): extracted from c-REQUIRE
(c-REQUIRE): use load-or-compile

Index: ChangeLog
===================================================================
RCS file: /cvsroot/clisp/clisp/src/ChangeLog,v
retrieving revision 1.7219
retrieving revision 1.7220
diff -u -d -r1.7219 -r1.7220
--- ChangeLog 10 Dec 2009 14:58:36 -0000 1.7219
+++ ChangeLog 10 Dec 2009 21:41:09 -0000 1.7220
@@ -1,3 +1,13 @@
+2009-12-10 Sam Steingold <sds@...>
+
+ when compiling REQUIRE, if the module is not found (e.g., it is a
+ dynamic module), call REQUIRE right away, at compile time.
+ * defs1.lisp (augment-load-path, load-path-augmentations)
+ (with-augmented-load-path): extracted from require
+ (require): use with-augmented-load-path
+ * compiler.lisp (load-or-compile): extracted from c-REQUIRE
+ (c-REQUIRE): use load-or-compile
+
2009-12-08 Sam Steingold <sds@...>

* modules/rawsock/rawsock.c: include <linux/netlink.h> when present

Index: compiler.lisp
===================================================================
RCS file: /cvsroot/clisp/clisp/src/compiler.lisp,v
retrieving revision 1.354
retrieving revision 1.355
diff -u -d -r1.354 -r1.355
--- compiler.lisp 5 Nov 2009 17:19:52 -0000 1.354
+++ compiler.lisp 10 Dec 2009 21:41:09 -0000 1.355
@@ -3414,38 +3414,48 @@
(defun c-PROVIDE (module-name)
(pushnew (module-name module-name) *compiled-modules* :test #'string=))

+;; load or compile
+(defun load-or-compile (module-name file may-require)
+ (with-augmented-load-path ((make-pathname :name nil :type nil
+ :defaults *compile-file-pathname*))
+ (let* ((present-files
+ (search-file file (append *source-file-types* '("lib")) nil))
+ (newest-file (first present-files)))
+ ;; if the libfile occurs among the found Files
+ ;; and if it is the newest:
+ (if (and (consp present-files)
+ (string= (pathname-type newest-file) "lib"))
+ (load newest-file ; load libfile
+ :verbose (and *load-verbose* *compile-verbose*)
+ :print (and *load-print* *compile-print*))
+ (if newest-file
+ ;; found file in *load-paths*+*compile-file-pathname*
+ (if *compile-file-directory*
+ ;; `compile-file' was given :output-file,
+ ;; so put the compiled file there
+ (compile-file newest-file :output-file
+ (merge-pathnames *compile-file-directory*
+ newest-file))
+ ;; `compile-file' was called without an explicit
+ ;; :output-file arg, so compile `in place'
+ (compile-file newest-file))
+ ;; file not found - call require
+ (if may-require
+ (require module-name)
+ (c-error *form*
+ (TEXT "Cannot find file ~S required by feature ~S")
+ file module-name)))))))
+
;; auxiliary function: REQUIRE on file-compilation, cf. function REQUIRE
(defun c-REQUIRE (module-name &optional (pathname nil p-given))
(setq module-name (module-name module-name))
(unless (or (member module-name *modules* :test #'string=)
(member module-name *compiled-modules* :test #'string=))
(unless p-given (setq pathname (pathname module-name)))
- (flet ((load-lib (file)
- (let* ((*load-paths*
- (cons (make-pathname :name nil :type nil
- :defaults *compile-file-truename*)
- *load-paths*))
- (present-files
- (search-file file (append *source-file-types* '("lib"))))
- (newest-file (first present-files)))
- ;; if the libfile occurs among the found Files
- ;; and if it is the newest:
- (if (and (consp present-files)
- (string= (pathname-type newest-file) "lib"))
- (load newest-file ; load libfile
- :verbose (and *load-verbose* *compile-verbose*)
- :print (and *load-print* *compile-print*))
- (let ((fi (or newest-file file)))
- (if (null *compile-file-directory*)
- ;; `compile-file' was called without an explicit
- ;; :output-file arg, so compile `in place'
- (compile-file fi)
- ;; `compile-file' was given :output-file,
- ;; so put the compiled file there
- (compile-file fi :output-file
- (merge-pathnames *compile-file-directory*
- fi))))))))
- (if (atom pathname) (load-lib pathname) (mapcar #'load-lib pathname)))))
+ (if (atom pathname)
+ (load-or-compile module-name pathname t)
+ (mapcar (lambda (path) (load-or-compile module-name path nil))
+ pathname))))

;;; auxiliary functions for
;;; LET/LET*/MULTIPLE-VALUE-BIND/Lambda-Expression/FLET/LABELS:

Index: defs1.lisp
===================================================================
RCS file: /cvsroot/clisp/clisp/src/defs1.lisp,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -d -r1.75 -r1.76
--- defs1.lisp 29 Sep 2009 21:59:08 -0000 1.75
+++ defs1.lisp 10 Dec 2009 21:41:09 -0000 1.76
@@ -168,22 +168,32 @@
(defvar *user-lib-directory* nil
"The location of user-installed modules.")

+(defun augment-load-path (paths)
+ (dolist (path paths *load-paths*)
+ (when path (setq *load-paths* (adjoin path *load-paths* :test #'equal)))))
+
+(defun load-path-augmentations (dynmod)
+ (list (merge-pathnames dynmod *lib-directory*)
+ (and *user-lib-directory*
+ (merge-pathnames dynmod *user-lib-directory*))
+ (and *load-pathname* ; not truename to respect symlinks
+ (make-pathname :name nil :type nil :defaults *load-pathname*))
+ (and *compile-file-pathname* ; could be called by eval-when-compile
+ (make-pathname :name nil :type nil
+ :defaults *compile-file-pathname*))))
+
+(defmacro with-augmented-load-path (dirs &body body)
+ `(let ((*load-paths*
+ ;; the name "dynmod/" used here should be in sync with clisp-link
+ (augment-load-path
+ ,(if dirs `(list ,@dirs) '(load-path-augmentations "dynmod/")))))
+ ,@body))
+
(defun require (module-name &optional (pathname nil p-given))
(setq module-name (module-name module-name))
(unless (member module-name *modules* :test #'string=)
(unless p-given (setq pathname (pathname module-name)))
- (let (#+CLISP (*load-paths* *load-paths*)
- #-CLISP (*default-pathname-defaults* '#""))
- ;; "dynmod/" should be in sync with clisp-link
- #+CLISP (pushnew (merge-pathnames "dynmod/" *lib-directory*) *load-paths*
- :test #'equal)
- #+CLISP (when *user-lib-directory*
- (pushnew (merge-pathnames "dynmod/" *user-lib-directory*)
- *load-paths* :test #'equal))
- #+CLISP (when *load-truename*
- (pushnew (make-pathname :name nil :type nil
- :defaults *load-truename*)
- *load-paths* :test #'equal))
+ (with-augmented-load-path ()
(if (atom pathname) (load pathname) (mapcar #'load pathname)))))

------------------------------

Message: 4
Date: Thu, 10 Dec 2009 21:41:11 +0000
From: Sam Steingold <sds@...>
Subject: clisp/doc impbody.xml,1.582,1.583 impent.xml,1.362,1.363
To: clisp-cvs@...
Message-ID: <E1NIql5-0003PG-Gq@...>

Update of /cvsroot/clisp/clisp/doc
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv13074/doc

Modified Files:
impbody.xml impent.xml
Log Message:
when compiling REQUIRE, if the module is not found (e.g., it is a
dynamic module), call REQUIRE right away, at compile time.
* defs1.lisp (augment-load-path, load-path-augmentations)
(with-augmented-load-path): extracted from require
(require): use with-augmented-load-path
* compiler.lisp (load-or-compile): extracted from c-REQUIRE
(c-REQUIRE): use load-or-compile

Index: impbody.xml
===================================================================
RCS file: /cvsroot/clisp/clisp/doc/impbody.xml,v
retrieving revision 1.582
retrieving revision 1.583
diff -u -d -r1.582 -r1.583
--- impbody.xml 25 Nov 2009 20:46:42 -0000 1.582
+++ impbody.xml 10 Dec 2009 21:41:09 -0000 1.583
@@ -4471,7 +4471,7 @@
<warning id="stream-eltype-stdio"><simpara>&clisp; expects to be able to
do &character-t; i/o on standard streams like &terminal-io-var;,
&standard-output-var;, &standard-input-var;, &error-output-var;,
- &query-io-var; et al, thus is is a <emphasis>very</emphasis> bad idea
+ &query-io-var; et al, thus is is a &very-e; bad idea
to change their &stream-element-type; even when you can. Use
&make-stream; instead, see <xref linkend="bin-stdio"/>.</simpara></warning>

@@ -5154,7 +5154,14 @@
forms are treated specially: &load-paths; is searched for
&foolisp-f; &and-e; <filename>#P"foo.lib"</filename>.
If the latest such file is a &lisp-file;, it is compiled;
-otherwise the &lib-file; is loaded.</para>
+otherwise the &lib-file; is loaded.
+If neither is found, <code>(&require; &foo-f;)</code> is called.</para>
+<warning id="module-user-file-name-conflict"><para>It is a &very-e; bad
+idea to name your files the same way as &clisp; modules
+(whether <link linkend="included-modules">system-supplied</link>
+or <olink targetdoc="clink" targetptr="opt-install">user-installed</olink>)
+because then &require-my; will use different files at compile
+and execution times.</para></warning>

<para>The &lib-file; is a <quote>header</quote> file which contains the
constant, variable, inline and macro definitions necessary for

Index: impent.xml
===================================================================
RCS file: /cvsroot/clisp/clisp/doc/impent.xml,v
retrieving revision 1.362
retrieving revision 1.363
diff -u -d -r1.362 -r1.363
--- impent.xml 1 Dec 2009 22:43:43 -0000 1.362
+++ impent.xml 10 Dec 2009 21:41:09 -0000 1.363
@@ -1077,6 +1077,7 @@
<!ENTITY before-e '<emphasis role="strong">before</emphasis>'>
<!ENTITY must-e '<emphasis role="strong">must</emphasis>'>
<!ENTITY cannot-e '<emphasis role="strong">cannot</emphasis>'>
+<!ENTITY very-e '<emphasis role="strong">very</emphasis>'>
<!ENTITY charset-glibc-libiconv 'This character set is only available on
platforms with &glibc; or &libiconv;.'>
<!ENTITY charset-libiconv 'This character set is only available on

------------------------------

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev

------------------------------

_______________________________________________
clisp-cvs mailing list
clisp-cvs@...
https://lists.sourceforge.net/lists/listinfo/clisp-cvs

End of clisp-cvs Digest, Vol 44, Issue 7
****************************************

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

[ clisp-Bugs-2903819 ] return character (cygwin?)

2009-12-09T18:20:18Z

Bugs item #2903819, was opened at 2009-11-25 15:52
Message generated for change (Comment added) made by sf-robot
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2903819&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: lisp error
>Status: Closed
Resolution: Invalid
Priority: 5
Private: No
Submitted By: TheBeaNerd (thebeanerd)
Assigned to: Sam Steingold (sds)
Summary: return character (cygwin?)

Initial Comment:
There seems to be an issue with the return character generated by the following code (at least under cygwin).

In particular, executing the form:

(with-open-file (stream "test.sh" :direction :output)
(format stream "#!/bin/sh~%~%")
(format stream "echo \"howdy\"~%"))

Then, at the shell:

$> chmod +x test.sh
$> ./test.sh
./test.sh line 2: $'\r' : command not found
howdy

Note the "command not found" message.

This issue effects applications such as ACL2 built using CLISP under cygwin.

----------------------------------------------------------------------

>Comment By: SourceForge Robot (sf-robot)
Date: 2009-12-10 02:20

Message:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2009-11-25 16:05

Message:
This bug report is now marked as "pending"/"invalid".
This means that we think that the problem you report is not a problem with
CLISP.
Unless you - the reporter - act within 2 weeks, the bug will be
permanently closed.
Sorry about the inconvenience - we hope your silence means that you agree
that this is not a bug in CLISP.

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2009-11-25 16:05

Message:
this is not a bug. CUSTOM:*DEFAULT-FILE-ENCODING* defaults to :DOS on
cygwin, so #\Newline is printed as "\r\n' (CRLF).
try (with-open-file (stream "test.sh" :direction :output :external-format
:unix) (format stream "#!/bin/sh~%~%echo \"howdy\"~%"))

required reading:
http://clisp.cons.org/impnotes/encoding.html#newline
http://clisp.cons.org/impnotes/clhs-newline.html
http://clisp.cons.org/impnotes/encoding.html#def-file-enc
http://clisp.cons.org/impnotes/open.html#extfmt

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2903819&group_id=1355

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

clisp-cvs Digest, Vol 44, Issue 6

2009-12-08T04:04:34Z

Re: small corrections to latest cvs updates

2009-12-07T07:52:07Z

Don Cohen wrote:
> I suggest that the sniffer code make the buffer size also a
> configuration parameter.

done

> (Just realized, you can't enter #x300 into shell without \ and even
> then it won't parse as an integer!)

use base 10, not base 16.
otoh....
please try again.

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

clisp-cvs Digest, Vol 44, Issue 5

2009-12-07T04:08:36Z

Re: small corrections to latest cvs updates

2009-12-06T11:34:15Z

> > (rawsock:socket :inet :raw <ip protocol>)
> > - does not include the ether header
> > (which is also what it says in man RAW(7))
The changes I saw in the doc indicate that the ether header is present
and evidently that has to be changed - whether it is depends on the
arguments. In fact, it seems quite plausible that other arguments we
have not yet tried might result in even less (or more) information,
such as removing IPv4 headers or removing UDP headers.

> > Note
> > that packet sockets don't reassemble IP fragments, unlike raw
> > sockets.
Note that in this case one might also get IP packets of up to 64K.
(Actually I've noticed that high speed nics tend to support ethernet
packets of >> 1500 bytes.)

I suggest that the sniffer code make the buffer size also a
configuration parameter. Also that the comment on top show all of
the parameters and their defaults, e.g.,
sudo clisp sniffer.lisp
is the same as
sudo clisp sniffer.lisp -domain inet -type packet -protocol #x300 -repeat 10 -size 1518

(Just realized, you can't enter #x300 into shell without \ and even
then it won't parse as an integer!)

> > I still get the impression that (rawsock:socket :packet :raw #x300) is
> > the right way to capture all packets in linux, though it requires
> > some fancier code for identifying the device.
Namely comparing with the results of ifaddrs.

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

clisp-cvs Digest, Vol 44, Issue 4

2009-12-06T04:03:58Z

Re: small corrections to latest cvs updates

2009-12-05T16:10:56Z

Sam Steingold writes:
> > > still awaiting demo code for checksum functions.
> > These will only be useful when you want to send raw packets.
> > We've not yet discussed when this might be useful.
>
> the functions are there.
> ergo, they are useful for _something_.
I don't think this follows - I don't want to admit it for CONFIGDEV

> what?
> can we have an example?

They're useful when you want to send ip packets from a "raw" socket -
one created with either AF packet or AF ip and type packet. A socket
created with AF ip and type raw, by contrast, I'll call an "ip" socket.

I'm trying to decide whether I think that's strictly necessary. Even
if it's not, it might be convenient in cases where you are using the
same raw socket for everything and you happen to want to send ip
packets. It would be necessary to use a raw socket, and therefore to
compute checksums, if you wanted to control the ethernet header of IP
packets. I've never tried all the stuff for controlling the IP fields
from an ip socket, so I'm not sure whether you ever have to compute
checksums in that case. The impression I got from the man page was
that you could control everything that made sense and in the end the
checksum would be computed for you. Of course, if you want to send
illegal IP packets then you almost certainly need to use raw sockets.
And in that case if you want to send correct checksums then the
checksum functions are handy. Even if you want to send incorrect
checksums that are closely related to correct checksums, e.g., with
the bytes swapped, it's handy to have checksum functions.

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

Re: small corrections to latest cvs updates

2009-12-05T15:30:25Z

> * Don Cohen <qba-fbheprsbetr-kkm@...> [2009-12-03 12:29:05 -0800]:
>
> > still awaiting demo code for checksum functions.
> These will only be useful when you want to send raw packets.
> We've not yet discussed when this might be useful.

the functions are there.
ergo, they are useful for _something_.
what?
can we have an example?

--
Sam Steingold (http://sds.podval.org/) on Ubuntu 9.04 (jaunty)
http://ffii.org http://www.PetitionOnline.com/tap12009/ http://dhimmi.com
http://iris.org.il http://jihadwatch.org http://truepeace.org
Software is like sex: it's better when it's free.

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

clisp-cvs Digest, Vol 44, Issue 3

2009-12-04T04:04:44Z

Send clisp-cvs mailing list submissions to
clisp-cvs@...

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/clisp-cvs
or, via email, send a message with subject or body 'help' to
clisp-cvs-request@...

You can reach the person managing the list at
clisp-cvs-owner@...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of clisp-cvs digest..."

CLISP CVS commits for today

Today's Topics:

1. clisp/modules/rawsock/demos sniffer.lisp,1.1,1.2 (Sam Steingold)
2. clisp/modules/rawsock/demos README,1.1,1.2 (Sam Steingold)
3. clisp/modules/rawsock/demos sniffer.lisp,1.2,1.3 (Sam Steingold)
4. clisp/modules/rawsock Makefile.in,1.14,1.15 (Sam Steingold)
5. clisp/doc cl-ent.xml,1.142,1.143 (Sam Steingold)
6. clisp/modules/rawsock rawsock.c,1.128,1.129
rawsock.xml,1.62,1.63 (Sam Steingold)

----------------------------------------------------------------------

Message: 1
Date: Thu, 03 Dec 2009 16:10:22 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock/demos sniffer.lisp,1.1,1.2
To: clisp-cvs@...
Message-ID: <E1NGEG6-0006EV-EP@...>

Update of /cvsroot/clisp/clisp/modules/rawsock/demos
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv23953

Modified Files:
sniffer.lisp
Log Message:
ensure the socket is closed before exit

Index: sniffer.lisp
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/demos/sniffer.lisp,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- sniffer.lisp 2 Dec 2009 23:03:11 -0000 1.1
+++ sniffer.lisp 3 Dec 2009 16:10:20 -0000 1.2
@@ -12,33 +12,40 @@
(setf (fill-pointer buffer) len)))

(defun print-buffer (buffer)
- (format t "len=~:D" (length buffer))
+ (format t " len=~:D" (length buffer))
(loop :for byte :across buffer :do (format t " ~2,'0X" byte))
(terpri))

-(defun sniff (socket repeat)
- (loop
- :with buffer = (make-array *buffer-len* :element-type '(unsigned-byte 8)
- :fill-pointer 0)
- :and device = (rawsock:make-sockaddr :UNSPEC)
- :repeat repeat :do
- (my-rcvfrom socket buffer device)
- (format t "~%family ~a " (rawsock:sockaddr-family device))
- (loop :for c :across (rawsock:sockaddr-data device)
- :do (format t "~c" (if (= c 0) #\space (code-char c ))))
- (print-buffer buffer)))
+(defun print-sockaddr (device)
+ (let ((family (rawsock:sockaddr-family device)))
+ (format t "family: ~A " family)
+ (case family
+ (:UNIX
+ (loop :for c :across (rawsock:sockaddr-data device)
+ :do (format t "~c" (if (= c 0) #\space (code-char c )))))
+ (t (prin1 (rawsock:sockaddr-data device))))))
+
+(defun my-open-socket (domain)
+ (cond ((string= domain "inet")
+ (rawsock:socket :inet :packet #x300))
+ ((string= domain "packet")
+ (rawsock:socket :packet :raw #x300))
+ (t (error "invalid socket domain ~S" domain))))
+
+(defun sniff (domain repeat)
+ (let ((socket (my-open-socket domain)))
+ (unwind-protect
+ (loop
+ :with buffer = (make-array *buffer-len* :fill-pointer 0
+ :element-type '(unsigned-byte 8))
+ :and device = (rawsock:make-sockaddr :UNSPEC)
+ :repeat repeat :do
+ (my-rcvfrom socket buffer device)
+ (print-sockaddr device)
+ (print-buffer buffer))
+ (rawsock:sock-close socket))))

(unless (= 2 (length *args*))
(error "Expected: ({inet|packet} repeat-count), got ~S" *args*))

-(defparameter *socket*
- (let ((arg (pop *args*)))
- (cond ((string= arg "inet")
- (rawsock:socket :inet :packet #x300))
- ((string= arg "packet")
- (rawsock:socket :packet :raw #x300))
- (t (error "invalid socket argument ~S" arg)))))
-(unless (plusp *socket*)
- (error "Invalid socket created for ~S: ~S" *args* *socket*))
-
-(sniff *socket* (parse-integer (pop *args*)))
+(sniff (pop *args*) (parse-integer (pop *args*)))

------------------------------

Message: 2
Date: Thu, 03 Dec 2009 17:05:35 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock/demos README,1.1,1.2
To: clisp-cvs@...
Message-ID: <E1NGF7X-0000H9-6e@...>

Update of /cvsroot/clisp/clisp/modules/rawsock/demos
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv1054

Modified Files:
README
Log Message:
more safety advice

Index: README
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/demos/README,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- README 2 Dec 2009 23:03:11 -0000 1.1
+++ README 3 Dec 2009 17:05:33 -0000 1.2
@@ -1,3 +1,11 @@
These are various Rawsock demos.
Most have to be run as a superuser, so beware!
We assume no responsibility for your use of this software.
+
+It is best to test all such things on a system that you can easily
+reboot and that is not critical to anything, e.g., use bootable CDs and
+floppy-based configuration files (write locked except during down-time).
+Thus one can push reset and try again on a moment's notice.
+
+Improper use may disrupt not only the local machine, but also
+surrounding networks, and who knows what else.

------------------------------

Message: 3
Date: Thu, 03 Dec 2009 17:26:08 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock/demos sniffer.lisp,1.2,1.3
To: clisp-cvs@...
Message-ID: <E1NGFRQ-00018p-40@...>

Update of /cvsroot/clisp/clisp/modules/rawsock/demos
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv4378

Modified Files:
sniffer.lisp
Log Message:
use options instead of positional args

Index: sniffer.lisp
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/demos/sniffer.lisp,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- sniffer.lisp 3 Dec 2009 16:10:20 -0000 1.2
+++ sniffer.lisp 3 Dec 2009 17:26:06 -0000 1.3
@@ -1,9 +1,30 @@
;;; Packet sniffer
;; run as root like this:
-;; sudo clisp sniffer.lisp inet 100
+;; $ sudo clisp sniffer.lisp
+;; or
+;; $ sudo clisp sniffer.lisp -domain packet -type raw

(require "rawsock")

+;; parse command line
+(defun get-arg-ht ()
+ (loop :with ht = (make-hash-table :test 'equal)
+ :for (key val) :on *args* :by #'cddr :do
+ (unless val (error "Odd number of arguments: ~S" *args*))
+ (unless (char= #\- (char key 0)) (error "Non-option argument: ~S" key))
+ (let ((v (gethash key ht)))
+ (when v (error "Option ~S given more than once: ~S and ~S" key v val)))
+ (setf (gethash key ht) val)
+ :finally (return ht)))
+
+(defun get-opt (ht opt default pack)
+ (let ((val (gethash opt ht)))
+ (if val
+ (or (parse-integer val :junk-allowed t)
+ (and pack (find-symbol (string-upcase val) pack))
+ (error "Invalid ~S: ~S" opt val))
+ default)))
+
(defvar *buffer-len* 1518)

(defun my-rcvfrom (socket buffer device)
@@ -25,27 +46,20 @@
:do (format t "~c" (if (= c 0) #\space (code-char c )))))
(t (prin1 (rawsock:sockaddr-data device))))))

-(defun my-open-socket (domain)
- (cond ((string= domain "inet")
- (rawsock:socket :inet :packet #x300))
- ((string= domain "packet")
- (rawsock:socket :packet :raw #x300))
- (t (error "invalid socket domain ~S" domain))))
-
-(defun sniff (domain repeat)
- (let ((socket (my-open-socket domain)))
+(defun sniff (args)
+ (let ((socket (rawsock:socket
+ (get-opt args "-domain" :INET "KEYWORD")
+ (get-opt args "-type" :PACKET "KEYWORD")
+ (get-opt args "-protocol" #x300 "KEYWORD"))))
(unwind-protect
(loop
:with buffer = (make-array *buffer-len* :fill-pointer 0
:element-type '(unsigned-byte 8))
:and device = (rawsock:make-sockaddr :UNSPEC)
- :repeat repeat :do
+ :repeat (get-opt args "-repeat" 10 nil) :do
(my-rcvfrom socket buffer device)
(print-sockaddr device)
(print-buffer buffer))
(rawsock:sock-close socket))))

-(unless (= 2 (length *args*))
- (error "Expected: ({inet|packet} repeat-count), got ~S" *args*))
-
-(sniff (pop *args*) (parse-integer (pop *args*)))
+(sniff (get-arg-ht))

------------------------------

Message: 4
Date: Thu, 03 Dec 2009 20:27:12 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock Makefile.in,1.14,1.15
To: clisp-cvs@...
Message-ID: <E1NGIGe-0000Qd-1R@...>

Update of /cvsroot/clisp/clisp/modules/rawsock
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv1642

Modified Files:
Makefile.in
Log Message:
fix last patch

Index: Makefile.in
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/Makefile.in,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -d -r1.14 -r1.15
--- Makefile.in 2 Dec 2009 23:03:11 -0000 1.14
+++ Makefile.in 3 Dec 2009 20:27:09 -0000 1.15
@@ -33,12 +33,12 @@

preload.lisp : $(srcdir)/preload.lisp
$(LN_S) $(srcdir)/preload.lisp .
- mkdir -p $(distribdir)/demos
- $(LN) $(srcdir)/demos/*.lisp $(srcdir)/demos/README $(distribdir)/demos/

# Make a module distribution into $(distribdir)
clisp-module-distrib : clisp-module force
$(LN) $(DISTRIBFILES) $(distribdir)
+ mkdir -p $(distribdir)/demos
+ $(LN) $(srcdir)/demos/*.lisp $(srcdir)/demos/README $(distribdir)/demos/

clean : force
rm -f core *.o *.a *.m.c *.fas *.lib

------------------------------

Message: 5
Date: Thu, 03 Dec 2009 21:04:00 +0000
From: Sam Steingold <sds@...>
Subject: clisp/doc cl-ent.xml,1.142,1.143
To: clisp-cvs@...
Message-ID: <E1NGIqG-0002Fj-Hu@...>

Update of /cvsroot/clisp/clisp/doc
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv8650/doc

Modified Files:
cl-ent.xml
Log Message:
extra fix for rawsock checksum docs

Index: cl-ent.xml
===================================================================
RCS file: /cvsroot/clisp/clisp/doc/cl-ent.xml,v
retrieving revision 1.142
retrieving revision 1.143
diff -u -d -r1.142 -r1.143
--- cl-ent.xml 14 Sep 2009 14:46:35 -0000 1.142
+++ cl-ent.xml 3 Dec 2009 21:03:58 -0000 1.143
@@ -173,6 +173,7 @@
<!ENTITY icmp '<ulink url="792" role="rfc"><command>ICMP</command></ulink>'>
<!ENTITY tcp '<ulink url="793" role="rfc"><command>TCP</command></ulink>'>
<!ENTITY udp '<ulink url="768" role="rfc"><command>UDP</command></ulink>'>
+<!ENTITY arp '<ulink url="826" role="rfc"><command>ARP</command></ulink>'>
<!ENTITY netiquette '<ulink url="1855" role="rfc">Netiquette</ulink>'>
<!ENTITY gcc '<ulink url="http://gcc.gnu.org/"><command>gcc</command></ulink>'>
<!ENTITY gdb '<ulink url="http://sources.redhat.com/gdb/"><command>gdb</command></ulink>'>

------------------------------

Message: 6
Date: Thu, 03 Dec 2009 21:04:00 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock rawsock.c,1.128,1.129
rawsock.xml,1.62,1.63
To: clisp-cvs@...
Message-ID: <E1NGIqG-0002Fn-KW@...>

Update of /cvsroot/clisp/clisp/modules/rawsock
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv8650/modules/rawsock

Modified Files:
rawsock.c rawsock.xml
Log Message:
extra fix for rawsock checksum docs

Index: rawsock.xml
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/rawsock.xml,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -d -r1.62 -r1.63
--- rawsock.xml 2 Dec 2009 23:17:23 -0000 1.62
+++ rawsock.xml 3 Dec 2009 21:03:58 -0000 1.63
@@ -317,11 +317,16 @@
- &udp;</term>
<listitem><simpara>Compute the appropriate protocol checksum and record
it in the appropriate location. &buf-r; is assumed to be a suitable
- ethernet frame (starting with a 14 byte MAC address) for the protocol,
- with the appropriate header etc.</simpara>
- <simpara>A typical packet you send is both &ip; and &tcp; and thus has two
- checksums, so you would want to call <emphasis>two</emphasis> functions.
-</simpara></listitem></varlistentry>
+ ethernet frame for the protocol, with the appropriate header etc.</simpara>
+ <simpara>Note that &buf-r; is an <emphasis>ethernet frame</emphasis>,
+ starting with 6 bytes of the destination MAC address, 6 bytes of the
+ source MAC address, and 2 bytes specifying the next level protocol,
+ (e.g., <literal>#x0800</literal> for &ip; and <literal>#x0806</literal>
+ for &arp;), i.e., the first 14 bytes of &buf-r; are ignored by these
+ functions.</simpara>
+ <simpara>A typical packet you send is both &ip; and &tcp; and thus
+ has two checksums, so you would want to call <emphasis>two</emphasis>
+ functions.</simpara></listitem></varlistentry>
<varlistentry><term><code>(RAWSOCK:CONFIGDEV &sock-r;
<replaceable>ifname</replaceable> &addr-r; &key-amp;
<replaceable>promisc</replaceable>

Index: rawsock.c
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/rawsock.c,v
retrieving revision 1.128
retrieving revision 1.129
diff -u -d -r1.128 -r1.129
--- rawsock.c 2 Dec 2009 21:42:02 -0000 1.128
+++ rawsock.c 3 Dec 2009 21:03:58 -0000 1.129
@@ -1439,8 +1439,11 @@
#endif

/* ================== CHECKSUM from Fred Cohen ================== */
-/* these check sum functions operate on ethernet _frames_,
- i.e., the 14 bytes MAC address followed by an IP datagram. */
+/* these check sum functions operate on ethernet _frames_, i.e.:
+ - 6 bytes of the destination MAC address
+ - 6 bytes of the source MAC address
+ - 2 bytes specifying the next level protocol (e.g., 0800 for IP)
+ followed by an IP datagram, so the first 14 bytes are ignored. */
static unsigned short ipcsum (unsigned char* buffer, size_t length) {
register long sum=0; /* assumes long == 32 bits */
unsigned short result;

------------------------------

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev

------------------------------

_______________________________________________
clisp-cvs mailing list
clisp-cvs@...
https://lists.sourceforge.net/lists/listinfo/clisp-cvs

End of clisp-cvs Digest, Vol 44, Issue 3
****************************************

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

Re: small corrections to latest cvs updates

2009-12-03T12:46:19Z

Sam Steingold writes:
> Don Cohen wrote:
> > clisp-cvs-request@... writes:
> > > +++ rawsock.xml 2 Dec 2009 21:05:59 -0000 1.61
> > > + ethernet frame (starting with a 14 byte MAC address) for the protocol,
> > The ethernet frame actually contains 2 6 byte mac addresses and 2
> > bytes for next level protocol
>
> what does "2 bytes for next level protocol" mean?

That same rfc 1700 (which I believe to be now obsolete) says:

The following list of EtherTypes is contributed unverified information
from various sources.

Assignments:
Ethernet Exp. Ethernet Description References
------------- ------------- ----------- ----------
decimal Hex decimal octal
000 0000-05DC - - IEEE802.3 Length Field [XEROX]
257 0101-01FF - - Experimental [XEROX]
512 0200 512 1000 XEROX PUP (see 0A00) [8,XEROX]
513 0201 - - PUP Addr Trans (see 0A01)[XEROX]
...

The normal ones you see in tcpdump are
2048 0800 513 1001 Internet IP (IPv4) [105,JBP]
and
2054 0806 - - ARP [88,JBP]

Recall I said that not all packets are IP ?
An IP packet will have as the last two bytes of the ethernet header
0800
An ARP packet will have instead 0806
And of course there are 2^16-2 other possible values.

I still can't find the rfc with this packet format map.
I'm sure I once saw it.
BTW, the destination mac address comes first - I guess so the
receiving nic can decide whether to ignore it earlier.

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

Re: small corrections to latest cvs updates

2009-12-03T12:29:05Z

Sam Steingold writes:
> thanks.
> this is why I always ask for explicit patches.
> OTOH, the good news is that you at least read the diffs.
I try to look for things that I might actually know or care about.
And this is why I hate those updates that automatically generate
dozens of changes (like the ones that affect all modules).

> still awaiting demo code for checksum functions.
These will only be useful when you want to send raw packets.
We've not yet discussed when this might be useful.
If you want to write some normal thing like ping or dns lookup
then (I'm hoping) you don't need raw packets and the checksums
will be computed for you by the higher level programs you use.
I've not actually looked at them. For instance, I bet the current
tcp code used by clisp never has to compute checksums. It probably
also does not worry about TOS or IP fragmentation or TCP sequence
numbers, all of which would be explicitly required in sending with
(what I call) the raw socket interface.

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

Re: errors in nightly builds

2009-12-03T12:27:51Z

Don Cohen wrote:
> This happens on both machines, but only in the mt builds.
> > mkdir -p /demos
> > ln /root/clisp/modules/rawsock/demos/*.lisp /root/clisp/modules/rawsock/demos/README /demos/
> > ln: creating hard link `/demos/sniffer.lisp': File exists
> > ln: creating hard link `/demos/README': File exists

OUCH!!!
sorry.
fixed.
please do "rm -rf /demos/"

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

Re: small corrections to latest cvs updates

2009-12-03T12:22:41Z

Don Cohen wrote:
> clisp-cvs-request@... writes:
> > +++ rawsock.xml 2 Dec 2009 21:05:59 -0000 1.61
> > + ethernet frame (starting with a 14 byte MAC address) for the protocol,
> The ethernet frame actually contains 2 6 byte mac addresses and 2
> bytes for next level protocol

what does "2 bytes for next level protocol" mean?

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

Re: small corrections to latest cvs updates

2009-12-03T12:19:04Z

Don Cohen wrote:

> clisp-cvs-request@... writes:
> > +++ rawsock.xml 2 Dec 2009 21:05:59 -0000 1.61
> > + ethernet frame (starting with a 14 byte MAC address) for the protocol,
> The ethernet frame actually contains 2 6 byte mac addresses and 2
> bytes for next level protocol
>
> > +++ rawsock.c 2 Dec 2009 21:05:58 -0000 1.127
> > +/* these check sum functions operate on ethernet _frames_,
> > + i.e., the 14 bytes MAC address followed by an IP datagram. */
> ditto

thanks.
this is why I always ask for explicit patches.
OTOH, the good news is that you at least read the diffs.

still awaiting demo code for checksum functions.

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

errors in nightly builds

2009-12-03T12:16:23Z

This happens on both machines, but only in the mt builds.
> mkdir -p /demos
> ln /root/clisp/modules/rawsock/demos/*.lisp /root/clisp/modules/rawsock/demos/README /demos/
> ln: creating hard link `/demos/sniffer.lisp': File exists
> ln: creating hard link `/demos/README': File exists
> make[1]: *** [preload.lisp] Error 1
> make[1]: Leaving directory `/root/clisp/build-mt/rawsock'
> make: *** [rawsock] Error 2

It looks like the build then proceeded and finished fine.
I can look further into the transcripts or even send them if it will
help.

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

small corrections to latest cvs updates

2009-12-03T12:09:37Z

clisp-cvs-request@... writes:
> +++ rawsock.xml 2 Dec 2009 21:05:59 -0000 1.61
> + ethernet frame (starting with a 14 byte MAC address) for the protocol,
The ethernet frame actually contains 2 6 byte mac addresses and 2
bytes for next level protocol

> +++ rawsock.c 2 Dec 2009 21:05:58 -0000 1.127
> +/* these check sum functions operate on ethernet _frames_,
> + i.e., the 14 bytes MAC address followed by an IP datagram. */
ditto

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

clisp-cvs Digest, Vol 44, Issue 2

2009-12-03T04:04:41Z

Send clisp-cvs mailing list submissions to
clisp-cvs@...

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/clisp-cvs
or, via email, send a message with subject or body 'help' to
clisp-cvs-request@...

You can reach the person managing the list at
clisp-cvs-owner@...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of clisp-cvs digest..."

CLISP CVS commits for today

Today's Topics:

1. clisp/modules/rawsock rawsock.c,1.126,1.127
rawsock.xml,1.60,1.61 (Sam Steingold)
2. clisp/modules/rawsock rawsock.c,1.127,1.128 (Sam Steingold)
3. clisp/src ChangeLog,1.7216,1.7217 (Sam Steingold)
4. clisp/modules/rawsock test.tst,1.58,1.59 (Sam Steingold)
5. clisp/modules/rawsock/demos - New directory (Sam Steingold)
6. clisp/modules/rawsock/demos README,NONE,1.1
sniffer.lisp,NONE,1.1 (Sam Steingold)
7. clisp/modules/rawsock Makefile.in,1.13,1.14 (Sam Steingold)
8. clisp/src ChangeLog,1.7217,1.7218 (Sam Steingold)
9. clisp/modules/rawsock rawsock.xml,1.61,1.62 (Sam Steingold)

----------------------------------------------------------------------

Message: 1
Date: Wed, 02 Dec 2009 21:06:04 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock rawsock.c,1.126,1.127
rawsock.xml,1.60,1.61
To: clisp-cvs@...
Message-ID: <E1NFwOi-0003TA-15@...>

Update of /cvsroot/clisp/clisp/modules/rawsock
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv13314/modules/rawsock

Modified Files:
rawsock.c rawsock.xml
Log Message:
checksum buffer is an ethernet frame starting with 14 byte MAC address

Index: rawsock.xml
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/rawsock.xml,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -d -r1.60 -r1.61
--- rawsock.xml 1 Dec 2009 22:43:43 -0000 1.60
+++ rawsock.xml 2 Dec 2009 21:05:59 -0000 1.61
@@ -316,8 +316,9 @@
- &udp;</term>
<listitem><simpara>Compute the appropriate protocol checksum and record
it in the appropriate location. &buf-r; is assumed to be a suitable
- packet for the protocol, with the appropriate header etc.
- The typical packet you send is both &ip; and &tcp; and thus has two
+ ethernet frame (starting with a 14 byte MAC address) for the protocol,
+ with the appropriate header etc.</simpara>
+ <simpara>A typical packet you send is both &ip; and &tcp; and thus has two
checksums, so you would want to call <emphasis>two</emphasis> functions.
</simpara></listitem></varlistentry>
<varlistentry><term><code>(RAWSOCK:CONFIGDEV &sock-r;

Index: rawsock.c
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/rawsock.c,v
retrieving revision 1.126
retrieving revision 1.127
diff -u -d -r1.126 -r1.127
--- rawsock.c 1 Dec 2009 18:39:27 -0000 1.126
+++ rawsock.c 2 Dec 2009 21:05:58 -0000 1.127
@@ -1439,6 +1439,8 @@
#endif

/* ================== CHECKSUM from Fred Cohen ================== */
+/* these check sum functions operate on ethernet _frames_,
+ i.e., the 14 bytes MAC address followed by an IP datagram. */
static unsigned short ipcsum (unsigned char* buffer, size_t length) {
register long sum=0; /* assumes long == 32 bits */
unsigned short result;

------------------------------

Message: 2
Date: Wed, 02 Dec 2009 21:42:05 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock rawsock.c,1.127,1.128
To: clisp-cvs@...
Message-ID: <E1NFwxZ-0005Tw-Du@...>

Update of /cvsroot/clisp/clisp/modules/rawsock
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv21002/modules/rawsock

Modified Files:
rawsock.c
Log Message:
(get_socket_protocol) [HAVE_GETPROTOBYNAME]: fix argument order in the error message

Index: rawsock.c
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/rawsock.c,v
retrieving revision 1.127
retrieving revision 1.128
diff -u -d -r1.127 -r1.128
--- rawsock.c 2 Dec 2009 21:05:58 -0000 1.127
+++ rawsock.c 2 Dec 2009 21:42:02 -0000 1.128
@@ -657,7 +657,7 @@
});
if (pe) return pe->p_proto;
pushSTACK(NIL); /* no PLACE */
- pushSTACK(TheSubr(subr_self)->name); pushSTACK(proto);
+ pushSTACK(proto); pushSTACK(TheSubr(subr_self)->name);
check_value(error_condition,GETTEXT("~S: invalid protocol name ~S"));
proto = value1;
goto get_socket_protocol_restart;

------------------------------

Message: 3
Date: Wed, 02 Dec 2009 21:42:06 +0000
From: Sam Steingold <sds@...>
Subject: clisp/src ChangeLog,1.7216,1.7217
To: clisp-cvs@...
Message-ID: <E1NFwxa-0005U2-8v@...>

Update of /cvsroot/clisp/clisp/src
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv21002/src

Modified Files:
ChangeLog
Log Message:
(get_socket_protocol) [HAVE_GETPROTOBYNAME]: fix argument order in the error message

Index: ChangeLog
===================================================================
RCS file: /cvsroot/clisp/clisp/src/ChangeLog,v
retrieving revision 1.7216
retrieving revision 1.7217
diff -u -d -r1.7216 -r1.7217
--- ChangeLog 1 Dec 2009 18:39:28 -0000 1.7216
+++ ChangeLog 2 Dec 2009 21:42:03 -0000 1.7217
@@ -1,3 +1,8 @@
+2009-12-02 Sam Steingold <sds@...>
+
+ * modules/rawsock/rawsock.c (get_socket_protocol)
+ [HAVE_GETPROTOBYNAME]: fix argument order in the error message
+
2009-12-01 Sam Steingold <sds@...>

* modules/clx/new-clx/clx.f, modules/rawsock/rawsock.c (unused):

------------------------------

Message: 4
Date: Wed, 02 Dec 2009 21:48:58 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock test.tst,1.58,1.59
To: clisp-cvs@...
Message-ID: <E1NFx4E-0005sM-AZ@...>

Update of /cvsroot/clisp/clisp/modules/rawsock
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv22581

Modified Files:
test.tst
Log Message:
add a test for check_socket_protocol

Index: test.tst
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/test.tst,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -d -r1.58 -r1.59
--- test.tst 8 Oct 2009 18:58:39 -0000 1.58
+++ test.tst 2 Dec 2009 21:48:56 -0000 1.59
@@ -106,11 +106,15 @@

(catch 'type-error-handler
(handler-bind ((type-error #'type-error-handler))
- (rawsock:socket :INET :FOO nil)))
+ (rawsock:socket :INET t nil)))
NIL
(catch 'type-error-handler
(handler-bind ((type-error #'type-error-handler))
- (rawsock:socket :FOO :STREAM nil)))
+ (rawsock:socket t :STREAM nil)))
+NIL
+(catch 'type-error-handler
+ (handler-bind ((type-error #'type-error-handler))
+ (rawsock:socket :INET :STREAM t)))
NIL

(integerp (show (setq *sock* (rawsock:socket :INET :STREAM nil)))) T

------------------------------

Message: 5
Date: Wed, 02 Dec 2009 23:00:46 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock/demos - New directory
To: clisp-cvs@...
Message-ID: <E1NFyBi-0001tI-9k@...>

Update of /cvsroot/clisp/clisp/modules/rawsock/demos
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv7228/demos

Log Message:
Directory /cvsroot/clisp/clisp/modules/rawsock/demos added to the repository

------------------------------

Message: 6
Date: Wed, 02 Dec 2009 23:03:14 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock/demos README,NONE,1.1
sniffer.lisp,NONE,1.1
To: clisp-cvs@...
Message-ID: <E1NFyE6-000243-1N@...>

Update of /cvsroot/clisp/clisp/modules/rawsock/demos
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv7919/modules/rawsock/demos

Added Files:
README sniffer.lisp
Log Message:
* modules/rawsock/demos/sniffer.lisp: add a demo
* modules/rawsock/Makefile.in (clisp-module-distrib): install it

--- NEW FILE: README ---
These are various Rawsock demos.
Most have to be run as a superuser, so beware!
We assume no responsibility for your use of this software.

--- NEW FILE: sniffer.lisp ---
;;; Packet sniffer
;; run as root like this:
;; sudo clisp sniffer.lisp inet 100

(require "rawsock")

(defvar *buffer-len* 1518)

(defun my-rcvfrom (socket buffer device)
(setf (fill-pointer buffer) 1518)
(let ((len (rawsock:recvfrom socket buffer device)))
(setf (fill-pointer buffer) len)))

(defun print-buffer (buffer)
(format t "len=~:D" (length buffer))
(loop :for byte :across buffer :do (format t " ~2,'0X" byte))
(terpri))

(defun sniff (socket repeat)
(loop
:with buffer = (make-array *buffer-len* :element-type '(unsigned-byte 8)
:fill-pointer 0)
:and device = (rawsock:make-sockaddr :UNSPEC)
:repeat repeat :do
(my-rcvfrom socket buffer device)
(format t "~%family ~a " (rawsock:sockaddr-family device))
(loop :for c :across (rawsock:sockaddr-data device)
:do (format t "~c" (if (= c 0) #\space (code-char c ))))
(print-buffer buffer)))

(unless (= 2 (length *args*))
(error "Expected: ({inet|packet} repeat-count), got ~S" *args*))

(defparameter *socket*
(let ((arg (pop *args*)))
(cond ((string= arg "inet")
(rawsock:socket :inet :packet #x300))
((string= arg "packet")
(rawsock:socket :packet :raw #x300))
(t (error "invalid socket argument ~S" arg)))))
(unless (plusp *socket*)
(error "Invalid socket created for ~S: ~S" *args* *socket*))

(sniff *socket* (parse-integer (pop *args*)))

------------------------------

Message: 7
Date: Wed, 02 Dec 2009 23:03:13 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock Makefile.in,1.13,1.14
To: clisp-cvs@...
Message-ID: <E1NFyE6-000244-1M@...>

Update of /cvsroot/clisp/clisp/modules/rawsock
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv7919/modules/rawsock

Modified Files:
Makefile.in
Log Message:
* modules/rawsock/demos/sniffer.lisp: add a demo
* modules/rawsock/Makefile.in (clisp-module-distrib): install it

Index: Makefile.in
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/Makefile.in,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- Makefile.in 3 Sep 2009 15:28:58 -0000 1.13
+++ Makefile.in 2 Dec 2009 23:03:11 -0000 1.14
@@ -33,6 +33,8 @@

preload.lisp : $(srcdir)/preload.lisp
$(LN_S) $(srcdir)/preload.lisp .
+ mkdir -p $(distribdir)/demos
+ $(LN) $(srcdir)/demos/*.lisp $(srcdir)/demos/README $(distribdir)/demos/

# Make a module distribution into $(distribdir)
clisp-module-distrib : clisp-module force

------------------------------

Message: 8
Date: Wed, 02 Dec 2009 23:03:15 +0000
From: Sam Steingold <sds@...>
Subject: clisp/src ChangeLog,1.7217,1.7218
To: clisp-cvs@...
Message-ID: <E1NFyE7-00024E-Jl@...>

Update of /cvsroot/clisp/clisp/src
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv7919/src

Modified Files:
ChangeLog
Log Message:
* modules/rawsock/demos/sniffer.lisp: add a demo
* modules/rawsock/Makefile.in (clisp-module-distrib): install it

Index: ChangeLog
===================================================================
RCS file: /cvsroot/clisp/clisp/src/ChangeLog,v
retrieving revision 1.7217
retrieving revision 1.7218
diff -u -d -r1.7217 -r1.7218
--- ChangeLog 2 Dec 2009 21:42:03 -0000 1.7217
+++ ChangeLog 2 Dec 2009 23:03:11 -0000 1.7218
@@ -1,5 +1,10 @@
2009-12-02 Sam Steingold <sds@...>

+ * modules/rawsock/demos/sniffer.lisp: add a demo
+ * modules/rawsock/Makefile.in (clisp-module-distrib): install it
+
+2009-12-02 Sam Steingold <sds@...>
+
* modules/rawsock/rawsock.c (get_socket_protocol)
[HAVE_GETPROTOBYNAME]: fix argument order in the error message

------------------------------

Message: 9
Date: Wed, 02 Dec 2009 23:17:25 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock rawsock.xml,1.61,1.62
To: clisp-cvs@...
Message-ID: <E1NFyRp-0002qS-6u@...>

Update of /cvsroot/clisp/clisp/modules/rawsock
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv10930

Modified Files:
rawsock.xml
Log Message:
mention modules/rawsock/demos/

Index: rawsock.xml
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/rawsock.xml,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -d -r1.61 -r1.62
--- rawsock.xml 2 Dec 2009 21:05:59 -0000 1.61
+++ rawsock.xml 2 Dec 2009 23:17:23 -0000 1.62
@@ -29,8 +29,9 @@
so you <emphasis>still</emphasis> have to &close; the original raw socket.
</simpara></warning>

-<para>File <filename role="clisp-cvs">modules/rawsock/test.tst</filename>
- contains plenty of examples.</para>
+<para>Test file <filename role="clisp-cvs">modules/rawsock/test.tst</filename>
+ and the demos in <filename role="clisp-cvs">modules/rawsock/demos/</filename>
+ contain plenty of examples.</para>
</section>

<section id="rawsock-func"><title>Single System Call Functions</title>

------------------------------

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev

------------------------------

_______________________________________________
clisp-cvs mailing list
clisp-cvs@...
https://lists.sourceforge.net/lists/listinfo/clisp-cvs

End of clisp-cvs Digest, Vol 44, Issue 2
****************************************

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

clisp-cvs Digest, Vol 44, Issue 1

2009-12-02T04:04:26Z

Send clisp-cvs mailing list submissions to
clisp-cvs@...

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/clisp-cvs
or, via email, send a message with subject or body 'help' to
clisp-cvs-request@...

You can reach the person managing the list at
clisp-cvs-owner@...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of clisp-cvs digest..."

CLISP CVS commits for today

Today's Topics:

1. clisp/src ChangeLog,1.7214,1.7215 (Sam Steingold)
2. clisp/modules/rawsock rawsock.c,1.124,1.125 (Sam Steingold)
3. clisp/doc common.xsl,1.77,1.78 (Sam Steingold)
4. clisp/modules/rawsock rawsock.c,1.125,1.126 (Sam Steingold)
5. clisp/modules/clx/new-clx clx.f,2.178,2.179 (Sam Steingold)
6. clisp/src ChangeLog,1.7215,1.7216 (Sam Steingold)
7. clisp/modules/rawsock rawsock.xml,1.58,1.59 (Sam Steingold)
8. clisp/modules/rawsock rawsock.xml,1.59,1.60 (Sam Steingold)
9. clisp/doc impent.xml,1.361,1.362 (Sam Steingold)

----------------------------------------------------------------------

Message: 1
Date: Tue, 01 Dec 2009 18:34:22 +0000
From: Sam Steingold <sds@...>
Subject: clisp/src ChangeLog,1.7214,1.7215
To: clisp-cvs@...
Message-ID: <E1NFXYN-0007rS-1n@...>

Update of /cvsroot/clisp/clisp/src
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv30172/src

Modified Files:
ChangeLog
Log Message:
(configdev): use strncpy/IFNAMSIZ
instead of strcpy for copying the interface name

Index: ChangeLog
===================================================================
RCS file: /cvsroot/clisp/clisp/src/ChangeLog,v
retrieving revision 1.7214
retrieving revision 1.7215
diff -u -d -r1.7214 -r1.7215
--- ChangeLog 30 Nov 2009 04:30:27 -0000 1.7214
+++ ChangeLog 1 Dec 2009 18:34:20 -0000 1.7215
@@ -1,3 +1,8 @@
+2009-12-01 Sam Steingold <sds@...>
+
+ * modules/rawsock/rawsock.c (configdev): use strncpy/IFNAMSIZ
+ instead of strcpy for copying the interface name
+
2009-11-29 Sam Steingold <sds@...>

* m4/clisp.m4 (CL_CLISP): use "." instead of "source" (bash-specific)

------------------------------

Message: 2
Date: Tue, 01 Dec 2009 18:34:22 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock rawsock.c,1.124,1.125
To: clisp-cvs@...
Message-ID: <E1NFXYM-0007rM-Ka@...>

Update of /cvsroot/clisp/clisp/modules/rawsock
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv30172/modules/rawsock

Modified Files:
rawsock.c
Log Message:
(configdev): use strncpy/IFNAMSIZ
instead of strcpy for copying the interface name

Index: rawsock.c
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/rawsock.c,v
retrieving revision 1.124
retrieving revision 1.125
diff -u -d -r1.124 -r1.125
--- rawsock.c 12 Nov 2009 20:36:13 -0000 1.124
+++ rawsock.c 1 Dec 2009 18:34:20 -0000 1.125
@@ -1145,12 +1145,12 @@
}

#if defined(HAVE_NET_IF_H)
-/* STACK_1 = name, for error reporting */
-static void configdev (rawsock_t sock, char* name, int ipaddress, int flags) {
+/* STACK_1 = ifname, for error reporting */
+static void configdev (rawsock_t sock, char* ifname, int ipaddress, int flags) {
struct ifreq ifrequest;
#if defined(SIOCGIFFLAGS) && defined(SIOCSIFFLAGS)
memset(&ifrequest, 0, sizeof(struct ifreq));
- strcpy(ifrequest.ifr_name, name);
+ strncpy(ifrequest.ifr_name, ifname, IFNAMSIZ);
if (ioctl(sock, SIOCGIFFLAGS, &ifrequest) < 0)
OS_file_error(STACK_1);
ifrequest.ifr_flags |= flags;
@@ -1159,7 +1159,7 @@
#endif
#if defined(SIOCGIFADDR) && defined(SIOCSIFADDR)
memset(&ifrequest, 0, sizeof(struct ifreq));
- strcpy(ifrequest.ifr_name, name);
+ strncpy(ifrequest.ifr_name, ifname, IFNAMSIZ);
if (ioctl(sock, SIOCGIFADDR, &ifrequest) < 0)
OS_file_error(STACK_1);
/* address was 0.0.0.0 -> error */
@@ -1177,13 +1177,13 @@
}

DEFFLAGSET(configdev_flags,IFF_PROMISC IFF_NOARP)
-DEFUN(RAWSOCK:CONFIGDEV, socket name ipaddress &key PROMISC NOARP) {
+DEFUN(RAWSOCK:CONFIGDEV, socket ifname ipaddress &key PROMISC NOARP) {
int flags = configdev_flags();
uint32 ipaddress = I_to_UL(check_uint32(STACK_0));
rawsock_t sock = I_to_uint(check_uint(STACK_2));
- with_string_0(check_string(STACK_1),Symbol_value(S(utf_8)),name, {
+ with_string_0(check_string(STACK_1),Symbol_value(S(utf_8)),ifname, {
begin_blocking_system_call();
- configdev(sock, name, ipaddress, flags);
+ configdev(sock, ifname, ipaddress, flags);
end_blocking_system_call();
});
VALUES0; skipSTACK(3);

------------------------------

Message: 3
Date: Tue, 01 Dec 2009 18:35:46 +0000
From: Sam Steingold <sds@...>
Subject: clisp/doc common.xsl,1.77,1.78
To: clisp-cvs@...
Message-ID: <E1NFXZi-00087P-47@...>

Update of /cvsroot/clisp/clisp/doc
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv31185

Modified Files:
common.xsl
Log Message:
RFC: rfc.net seems dead, use www.ietf.org/rfc instead

Index: common.xsl
===================================================================
RCS file: /cvsroot/clisp/clisp/doc/common.xsl,v
retrieving revision 1.77
retrieving revision 1.78
diff -u -d -r1.77 -r1.78
--- common.xsl 29 Jun 2009 18:12:25 -0000 1.77
+++ common.xsl 1 Dec 2009 18:35:44 -0000 1.78
@@ -88,9 +88,9 @@
><xsl:apply-templates/></a></xsl:template>


-<xsl:param name="rfc.top" select="'http://rfc.net/rfc'"/>
+<xsl:param name="rfc.top" select="'http://www.ietf.org/rfc/rfc'"/>
<xsl:template match="ulink[@role='rfc']">
- <a class="{@role}" href="{$rfc.top}{@url}.html"><code>
+ <a class="{@role}" href="{$rfc.top}{@url}.txt"><code>
<xsl:choose><xsl:when test=".=''"><xsl:text>RFC</xsl:text>
<xsl:value-of select="@url"/></xsl:when>
<xsl:otherwise><xsl:apply-templates/></xsl:otherwise></xsl:choose>

------------------------------

Message: 4
Date: Tue, 01 Dec 2009 18:39:30 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock rawsock.c,1.125,1.126
To: clisp-cvs@...
Message-ID: <E1NFXdK-0000Mu-1H@...>

Update of /cvsroot/clisp/clisp/modules/rawsock
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv1382/modules/rawsock

Modified Files:
rawsock.c
Log Message:
(unused): define depending on __GNUC__, not GNU

Index: rawsock.c
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/rawsock.c,v
retrieving revision 1.125
retrieving revision 1.126
diff -u -d -r1.125 -r1.126
--- rawsock.c 1 Dec 2009 18:34:20 -0000 1.125
+++ rawsock.c 1 Dec 2009 18:39:27 -0000 1.126
@@ -1548,7 +1548,7 @@
VALUES1(fixnum(length)); skipSTACK(1);
}

-#ifdef GNU /* to prevent a gcc-warning "statement with no effect" */
+#ifdef __GNUC__ /* to prevent a gcc-warning "statement with no effect" */
# define unused (void)
#else
# define unused

------------------------------

Message: 5
Date: Tue, 01 Dec 2009 18:39:29 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/clx/new-clx clx.f,2.178,2.179
To: clisp-cvs@...
Message-ID: <E1NFXdK-0000Ms-0m@...>

Update of /cvsroot/clisp/clisp/modules/clx/new-clx
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv1382/modules/clx/new-clx

Modified Files:
clx.f
Log Message:
(unused): define depending on __GNUC__, not GNU

Index: clx.f
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/clx/new-clx/clx.f,v
retrieving revision 2.178
retrieving revision 2.179
diff -u -d -r2.178 -r2.179
--- clx.f 12 Nov 2009 20:36:13 -0000 2.178
+++ clx.f 1 Dec 2009 18:39:27 -0000 2.179
@@ -442,7 +442,7 @@
#include <X11/extensions/shape.h>
##endif

-#ifdef GNU /* to prevent a gcc-warning "statement with no effect" */
+#ifdef __GNUC__ /* to prevent a gcc-warning "statement with no effect" */
# define unused (void)
#else
# define unused

------------------------------

Message: 6
Date: Tue, 01 Dec 2009 18:39:30 +0000
From: Sam Steingold <sds@...>
Subject: clisp/src ChangeLog,1.7215,1.7216
To: clisp-cvs@...
Message-ID: <E1NFXdK-0000N2-9A@...>

Update of /cvsroot/clisp/clisp/src
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv1382/src

Modified Files:
ChangeLog
Log Message:
(unused): define depending on __GNUC__, not GNU

Index: ChangeLog
===================================================================
RCS file: /cvsroot/clisp/clisp/src/ChangeLog,v
retrieving revision 1.7215
retrieving revision 1.7216
diff -u -d -r1.7215 -r1.7216
--- ChangeLog 1 Dec 2009 18:34:20 -0000 1.7215
+++ ChangeLog 1 Dec 2009 18:39:28 -0000 1.7216
@@ -1,5 +1,10 @@
2009-12-01 Sam Steingold <sds@...>

+ * modules/clx/new-clx/clx.f, modules/rawsock/rawsock.c (unused):
+ define depending on __GNUC__, not GNU
+
+2009-12-01 Sam Steingold <sds@...>
+
* modules/rawsock/rawsock.c (configdev): use strncpy/IFNAMSIZ
instead of strcpy for copying the interface name

------------------------------

Message: 7
Date: Tue, 01 Dec 2009 19:16:39 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock rawsock.xml,1.58,1.59
To: clisp-cvs@...
Message-ID: <E1NFYDH-0002O0-PH@...>

Update of /cvsroot/clisp/clisp/modules/rawsock
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv9168

Modified Files:
rawsock.xml
Log Message:
typos

Index: rawsock.xml
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/rawsock.xml,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -d -r1.58 -r1.59
--- rawsock.xml 1 Sep 2009 14:25:23 -0000 1.58
+++ rawsock.xml 1 Dec 2009 19:16:37 -0000 1.59
@@ -242,9 +242,9 @@
<varlistentry id="rawsock-if-name-index"><term><code>(RAWSOCK:IF-NAME-INDEX
&optional-amp; &what-r;)</code></term>
<listitem><simpara>Call <function role="unix">if_nametoindex</function>
- when &net-r; is a &string-t; and return an &integer-t;;
+ when &when-r; is a &string-t; and return an &integer-t;;
or call <function role="unix">if_indextoname</function> when
- &net-r; is an &integer-t; and return a &string-t;.
+ &what-r; is an &integer-t; and return a &string-t;.
When &what-r; is &nil;, return an &alist; of
pairs <literal role="data">(&index-r; . &name-r;)</literal>
using <function role="unix">if_nameindex</function>.
@@ -320,8 +320,9 @@
The typical packet you send is both &ip; and &tcp; and thus has two
checksums, so you would want to call <emphasis>two</emphasis> functions.
</simpara></listitem></varlistentry>
-<varlistentry><term><code>(RAWSOCK:CONFIGDEV &sock-r; &name-r; &addr-r;
- &key-amp; <replaceable>promisc</replaceable>
+<varlistentry><term><code>(RAWSOCK:CONFIGDEV &sock-r;
+ <replaceable>ifname</replaceable> &addr-r; &key-amp;
+ <replaceable>promisc</replaceable>
<replaceable>noarp</replaceable>)</code></term>
<listitem><simpara>Set some socket options and &ip; &addr-r;
with <function role="unix">ioctl</function>.

------------------------------

Message: 8
Date: Tue, 01 Dec 2009 22:43:45 +0000
From: Sam Steingold <sds@...>
Subject: clisp/modules/rawsock rawsock.xml,1.59,1.60
To: clisp-cvs@...
Message-ID: <E1NFbRh-0005ZI-JK@...>

Update of /cvsroot/clisp/clisp/modules/rawsock
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv21392/modules/rawsock

Modified Files:
rawsock.xml
Log Message:
add &or-e;

Index: rawsock.xml
===================================================================
RCS file: /cvsroot/clisp/clisp/modules/rawsock/rawsock.xml,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -d -r1.59 -r1.60
--- rawsock.xml 1 Dec 2009 19:16:37 -0000 1.59
+++ rawsock.xml 1 Dec 2009 22:43:43 -0000 1.60
@@ -256,7 +256,7 @@
filtered using flags, e.g., <code>(ifaddrs :flags-or '(a b)
:flags-and '(c d))</code> will return a list of objects which have
flags <literal>c</literal> &and-e; <literal>d</literal> &and-e; at
- least one of <literal>a</literal> or <literal>b</literal> set.
+ least one of <literal>a</literal> &or-e; <literal>b</literal> set.
</simpara></listitem></varlistentry>
<varlistentry id="rawsock-sockopt"><term><code>(RAWSOCK:SOCKET-OPTION
&sock-r; &name-r; &key-amp; :LEVEL)</code></term>

------------------------------

Message: 9
Date: Tue, 01 Dec 2009 22:43:45 +0000
From: Sam Steingold <sds@...>
Subject: clisp/doc impent.xml,1.361,1.362
To: clisp-cvs@...
Message-ID: <E1NFbRh-0005ZG-I7@...>

Update of /cvsroot/clisp/clisp/doc
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv21392/doc

Modified Files:
impent.xml
Log Message:
add &or-e;

Index: impent.xml
===================================================================
RCS file: /cvsroot/clisp/clisp/doc/impent.xml,v
retrieving revision 1.361
retrieving revision 1.362
diff -u -d -r1.361 -r1.362
--- impent.xml 19 Nov 2009 21:02:22 -0000 1.361
+++ impent.xml 1 Dec 2009 22:43:43 -0000 1.362
@@ -1070,6 +1070,7 @@
<!ENTITY yes-en '<entry>yes</entry>'>
<!ENTITY no-en '<entry>no</entry>'>
<!ENTITY and-e '<emphasis role="strong">and</emphasis>'>
+<!ENTITY or-e '<emphasis role="strong">or</emphasis>'>
<!ENTITY not-e '<emphasis role="strong">not</emphasis>'>
<!ENTITY is-e '<emphasis role="strong">is</emphasis>'>
<!ENTITY after-e '<emphasis role="strong">after</emphasis>'>

------------------------------

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev

------------------------------

_______________________________________________
clisp-cvs mailing list
clisp-cvs@...
https://lists.sourceforge.net/lists/listinfo/clisp-cvs

End of clisp-cvs Digest, Vol 44, Issue 1
****************************************

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

clisp-cvs Digest, Vol 43, Issue 19

2009-11-30T04:03:35Z

clisp-cvs Digest, Vol 43, Issue 18

2009-11-26T04:10:30Z

Send clisp-cvs mailing list submissions to
clisp-cvs@...

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/clisp-cvs
or, via email, send a message with subject or body 'help' to
clisp-cvs-request@...

You can reach the person managing the list at
clisp-cvs-owner@...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of clisp-cvs digest..."

CLISP CVS commits for today

Today's Topics:

1. clisp/doc impbody.xml,1.581,1.582 (Sam Steingold)
2. clisp/tests ChangeLog,1.645,1.646 streamslong.tst,1.25,1.26
(Sam Steingold)
3. clisp/src ChangeLog, 1.7211, 1.7212 NEWS, 1.516, 1.517
stream.d, 1.668, 1.669 (Sam Steingold)
4. clisp/tests streamslong.tst,1.26,1.27 (Sam Steingold)
5. clisp/src ChangeLog,1.7212,1.7213 pathname.d,1.509,1.510
(Sam Steingold)

----------------------------------------------------------------------

Message: 1
Date: Wed, 25 Nov 2009 20:46:45 +0000
From: Sam Steingold <sds@...>
Subject: clisp/doc impbody.xml,1.581,1.582
To: clisp-cvs@...
Message-ID: <E1NDOlB-0004jO-Ti@...>

Update of /cvsroot/clisp/clisp/doc
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv18152/doc

Modified Files:
impbody.xml
Log Message:
fix bug #[ 2902716 ]: CLEAR-INPUT should clear the EOF condition
* stream.d (clear_input_unbuffered): reset status and
strm_rd_ch_last slots on all streams, not just tty
(clear_input_buffered): add, clear the have_eof_p slot
(clear_input): call clear_input_buffered

Index: impbody.xml
===================================================================
RCS file: /cvsroot/clisp/clisp/doc/impbody.xml,v
retrieving revision 1.581
retrieving revision 1.582
diff -u -d -r1.581 -r1.582
--- impbody.xml 20 Nov 2009 14:50:39 -0000 1.581
+++ impbody.xml 25 Nov 2009 20:46:42 -0000 1.582
@@ -19,13 +19,10 @@
</varlistentry></variablelist>
This final delimiter is never actually seen by programs; no need to
test for <keysym>#\^D</keysym> or <keysym>#\^Z</keysym> - use
- &read-char-no-hang; to check for &eos;.
- Calling &clear-input; on the stream removes the &eos; state,
- thus making it available for further input.</para>
-
+ &read-char-no-hang; to check for &eos;.</para>
<para>A newline character can be entered by the user by pressing the
&enter; key.</para>
-
+<para>See also <xref linkend="clear-input"/>.</para>
</section>

@@ -4656,6 +4653,13 @@

</section>

+<section id="clear-input"><title>Function &clear-input;</title>
+<para>Calling &clear-input; on a &stream-t; removes the &eos; state,
+ thus making it available for further input.</para>
+<para>This allows reading from a file as it is being appended to,
+as if with <command role="unix">tail -f</command>.</para>
+</section>
+
<section id="close"><title>Function &close;</title>

<para>Function &close; is a &generic-function-t;, see

------------------------------

Message: 2
Date: Wed, 25 Nov 2009 20:46:47 +0000
From: Sam Steingold <sds@...>
Subject: clisp/tests ChangeLog,1.645,1.646 streamslong.tst,1.25,1.26
To: clisp-cvs@...
Message-ID: <E1NDOlD-0004jg-HY@...>

Update of /cvsroot/clisp/clisp/tests
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv18152/tests

Modified Files:
ChangeLog streamslong.tst
Log Message:
fix bug #[ 2902716 ]: CLEAR-INPUT should clear the EOF condition
* stream.d (clear_input_unbuffered): reset status and
strm_rd_ch_last slots on all streams, not just tty
(clear_input_buffered): add, clear the have_eof_p slot
(clear_input): call clear_input_buffered

Index: streamslong.tst
===================================================================
RCS file: /cvsroot/clisp/clisp/tests/streamslong.tst,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -d -r1.25 -r1.26
--- streamslong.tst 16 Dec 2008 17:15:52 -0000 1.25
+++ streamslong.tst 25 Nov 2009 20:46:45 -0000 1.26
@@ -234,3 +234,20 @@
((:DOS :DOS) (:UNIX :UNIX)
(CHARACTER CHARACTER) (UNSIGNED-BYTE 8)
((UNSIGNED-BYTE 8) (UNSIGNED-BYTE 8))))
+
+(let ((fname "test-eof"))
+ (open fname :direction :probe :if-exists :overwrite ; touch
+ :if-does-not-exist :create)
+ (flet ((f (buf new)
+ (with-open-file (in fname :direction :input)
+ (list (read-line in nil :eof)
+ (progn
+ (#+clisp ext:appease-cerrors #-clisp progn
+ (with-open-file (out fname :direction :output
+ :if-exists :append)
+ (write-line new out)))
+ #+clisp (clear-input in)
+ (read-line in nil :eof))))))
+ (unwind-protect (list (f t "foo") (f nil "bar"))
+ (delete-file fname))))
+((:EOF "foo") ("foo" "bar"))

Index: ChangeLog
===================================================================
RCS file: /cvsroot/clisp/clisp/tests/ChangeLog,v
retrieving revision 1.645
retrieving revision 1.646
diff -u -d -r1.645 -r1.646
--- ChangeLog 19 Nov 2009 21:02:23 -0000 1.645
+++ ChangeLog 25 Nov 2009 20:46:45 -0000 1.646
@@ -1,3 +1,8 @@
+2009-11-25 Sam Steingold <sds@...>
+
+ * streamslong.tst: fix bug #[ 2902716 ]: CLEAR-INPUT should clear
+ the EOF condition
+
2009-11-19 Sam Steingold <sds@...>

* path.tst: test RENAME-FILE :IF-EXISTS

------------------------------

Message: 3
Date: Wed, 25 Nov 2009 20:46:47 +0000
From: Sam Steingold <sds@...>
Subject: clisp/src ChangeLog, 1.7211, 1.7212 NEWS, 1.516, 1.517
stream.d, 1.668, 1.669
To: clisp-cvs@...
Message-ID: <E1NDOlD-0004jZ-EM@...>

Update of /cvsroot/clisp/clisp/src
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv18152/src

Modified Files:
ChangeLog NEWS stream.d
Log Message:
fix bug #[ 2902716 ]: CLEAR-INPUT should clear the EOF condition
* stream.d (clear_input_unbuffered): reset status and
strm_rd_ch_last slots on all streams, not just tty
(clear_input_buffered): add, clear the have_eof_p slot
(clear_input): call clear_input_buffered

Index: NEWS
===================================================================
RCS file: /cvsroot/clisp/clisp/src/NEWS,v
retrieving revision 1.516
retrieving revision 1.517
diff -u -d -r1.516 -r1.517
--- NEWS 19 Nov 2009 21:02:23 -0000 1.516
+++ NEWS 25 Nov 2009 20:46:44 -0000 1.517
@@ -21,6 +21,7 @@
+ Do not eliminate function calls which are advertised to have
exceptional situation in unsafe code. [ 2868166 ]
+ Fix an nternal error in DECLAIM on bad OPTIMIZE quality. [ 2868147 ]
+ + CLEAR-INPUT now clears the EOF condition on file streams. [ 2902716 ]

* ANSI compliance:
+ Implement the ANSI issue COMPILER-DIAGNOSTICS:USE-HANDLER: use the

Index: stream.d
===================================================================
RCS file: /cvsroot/clisp/clisp/src/stream.d,v
retrieving revision 1.668
retrieving revision 1.669
diff -u -d -r1.668 -r1.669
--- stream.d 29 Oct 2009 20:07:33 -0000 1.668
+++ stream.d 25 Nov 2009 20:46:44 -0000 1.669
@@ -5299,9 +5299,10 @@
> stream: Unbuffered-Channel-Stream
< result: true if Input was deleted, else false */
local maygc bool clear_input_unbuffered (object stream) {
+ UnbufferedStream_status(stream) = 0; /* forget about past EOF & bytebuf */
+ TheStream(stream)->strm_rd_ch_last = NIL; /* forget last char */
if (nullp(TheStream(stream)->strm_isatty))
return false; /* it's a file -> nothing to do */
- TheStream(stream)->strm_rd_ch_last = NIL; /* forget about past EOF */
#ifdef WIN32_NATIVE
/* Our low_listen_unbuffered_handle function, when applied to a WinNT
console, cannot tell when there is an LF pending after the
@@ -6745,6 +6746,16 @@
return LISTEN_AVAIL;
}

+/* UP: discard already entered input from a Buffered Stream.
+ clear_input_buffered(stream);
+ > stream: Buffered Stream
+ < result: true if Input was deleted, else false */
+local maygc bool clear_input_buffered (object stream) {
+ bool ret = BufferedStream_have_eof_p(stream);
+ BufferedStream_have_eof_p(stream) = false;
+ return ret;
+}
+
/* READ-CHAR-ARRAY - Pseudo-Function for File-Streams of Characters: */
local maygc uintL rd_ch_array_buffered (const gcv_object_t* stream_,
const gcv_object_t* chararray_,
@@ -16471,7 +16482,7 @@
&& !ChannelStream_buffered(stream))
result = clear_input_unbuffered(stream);
else
- result = false;
+ result = clear_input_buffered(stream);
break;
#ifdef KEYBOARD
case strmtype_keyboard:

Index: ChangeLog
===================================================================
RCS file: /cvsroot/clisp/clisp/src/ChangeLog,v
retrieving revision 1.7211
retrieving revision 1.7212
diff -u -d -r1.7211 -r1.7212
--- ChangeLog 21 Nov 2009 20:54:58 -0000 1.7211
+++ ChangeLog 25 Nov 2009 20:46:43 -0000 1.7212
@@ -1,3 +1,11 @@
+2009-11-25 Sam Steingold <sds@...>
+
+ fix bug #[ 2902716 ]: CLEAR-INPUT should clear the EOF condition
+ * stream.d (clear_input_unbuffered): reset status and
+ strm_rd_ch_last slots on all streams, not just tty
+ (clear_input_buffered): add, clear the have_eof_p slot
+ (clear_input): call clear_input_buffered
+
2009-11-21 Vladimir Tzankov <vtzankov@...>

* spvw.d (dynload_modules): guard libopen() with

------------------------------

Message: 4
Date: Wed, 25 Nov 2009 22:16:33 +0000
From: Sam Steingold <sds@...>
Subject: clisp/tests streamslong.tst,1.26,1.27
To: clisp-cvs@...
Message-ID: <E1NDQA5-0001ui-7z@...>

Update of /cvsroot/clisp/clisp/tests
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv7346

Modified Files:
streamslong.tst
Log Message:
simplify last test

Index: streamslong.tst
===================================================================
RCS file: /cvsroot/clisp/clisp/tests/streamslong.tst,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -d -r1.26 -r1.27
--- streamslong.tst 25 Nov 2009 20:46:45 -0000 1.26
+++ streamslong.tst 25 Nov 2009 22:16:31 -0000 1.27
@@ -235,17 +235,17 @@
(CHARACTER CHARACTER) (UNSIGNED-BYTE 8)
((UNSIGNED-BYTE 8) (UNSIGNED-BYTE 8))))

-(let ((fname "test-eof"))
+(let ((fname "test-eof")
+ #+clisp (custom:*reopen-open-file* nil))
(open fname :direction :probe :if-exists :overwrite ; touch
:if-does-not-exist :create)
(flet ((f (buf new)
(with-open-file (in fname :direction :input)
(list (read-line in nil :eof)
(progn
- (#+clisp ext:appease-cerrors #-clisp progn
- (with-open-file (out fname :direction :output
- :if-exists :append)
- (write-line new out)))
+ (with-open-file (out fname :direction :output
+ :if-exists :append)
+ (write-line new out))
#+clisp (clear-input in)
(read-line in nil :eof))))))
(unwind-protect (list (f t "foo") (f nil "bar"))

------------------------------

Message: 5
Date: Thu, 26 Nov 2009 04:58:25 +0000
From: Sam Steingold <sds@...>
Subject: clisp/src ChangeLog,1.7212,1.7213 pathname.d,1.509,1.510
To: clisp-cvs@...
Message-ID: <E1NDWQz-00041h-MU@...>

Update of /cvsroot/clisp/clisp/src
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv15430/src

Modified Files:
ChangeLog pathname.d
Log Message:
(RENAME-FILE): fix the error_too_many_args invocation for the ANSI case

Index: pathname.d
===================================================================
RCS file: /cvsroot/clisp/clisp/src/pathname.d,v
retrieving revision 1.509
retrieving revision 1.510
diff -u -d -r1.509 -r1.510
--- pathname.d 23 Nov 2009 21:32:40 -0000 1.509
+++ pathname.d 26 Nov 2009 04:58:23 -0000 1.510
@@ -6351,11 +6351,11 @@
rename_existing_path(STACK_2,STACK_0);
}

-/* (RENAME-FILE filename newname), CLTL p. 423 */
+/* (RENAME-FILE filename newname &if-exists), CLTL p. 423 */
LISPFUN(rename_file,seclass_default,2,0,norest,key,1,(kw(if_exists))) {
var if_exists_t if_exists = check_if_exists(popSTACK());
if (!nullp(O(ansi)) && if_exists != IF_EXISTS_UNBOUND)
- error_too_many_args(unbound,S(rename_file),3,2);
+ error_too_many_args(unbound,S(rename_file),4,2);
var object filename = STACK_1; /* filename-argument */
if (builtin_stream_p(filename)) { /* stream -> treat extra: */
/* must be file-stream: */

Index: ChangeLog
===================================================================
RCS file: /cvsroot/clisp/clisp/src/ChangeLog,v
retrieving revision 1.7212
retrieving revision 1.7213
diff -u -d -r1.7212 -r1.7213
--- ChangeLog 25 Nov 2009 20:46:43 -0000 1.7212
+++ ChangeLog 26 Nov 2009 04:58:21 -0000 1.7213
@@ -1,5 +1,10 @@
2009-11-25 Sam Steingold <sds@...>

+ * pathname.d (RENAME-FILE): fix the error_too_many_args invocation
+ for the ANSI case
+
+2009-11-25 Sam Steingold <sds@...>
+
fix bug #[ 2902716 ]: CLEAR-INPUT should clear the EOF condition
* stream.d (clear_input_unbuffered): reset status and
strm_rd_ch_last slots on all streams, not just tty

------------------------------

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july

------------------------------

_______________________________________________
clisp-cvs mailing list
clisp-cvs@...
https://lists.sourceforge.net/lists/listinfo/clisp-cvs

End of clisp-cvs Digest, Vol 43, Issue 18
*****************************************

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

[ clisp-Bugs-2902716 ] CLEAR-INPUT should clear the EOF condition

2009-11-25T12:57:53Z

Bugs item #2902716, was opened at 2009-11-23 15:35
Message generated for change (Settings changed) made by sds
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2902716&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: lisp error
Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Sam Steingold (sds)
>Assigned to: Sam Steingold (sds)
>Summary: CLEAR-INPUT should clear the EOF condition

Initial Comment:
when clisp reaches eof, it remembers it and never clears the condition even if when the file on disk changes.
sbcl and C (both FILE/fopen and int/fd/open interfaces) do not exhibit this behavior.

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2009-11-25 15:57

Message:
thank you for your bug report.
the bug has been fixed in the CVS tree.
you can either wait for the next release (recommended)
or check out the current CVS tree (see http://clisp.cons.org)
and build CLISP from the sources (be advised that between
releases the CVS tree is very unstable and may not even build
on your platform).

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2009-11-24 19:07

Message:
nope,
(let ((fname "test-eof"))
(open fname :direction :probe :if-exists :overwrite ; touch
:if-does-not-exist :create)
(unwind-protect
(with-open-file (in fname :direction :input)
(list (read-line in nil :eof)
(progn
(with-open-file (out fname :direction :output
:if-exists :append)
(write-line "foo" out))
(clear-input in)
(read-line in nil :eof))))
(delete-file fname)))
==> (:EOF :EOF) instead of (:EOF "foo")

----------------------------------------------------------------------

Comment By: Bruno Haible (haible)
Date: 2009-11-24 18:16

Message:
> how about a new CLEAR-EOF function which would remove that EOF marker
from
> the stream and try reading again?

This function already exists. It is part of CLEAR-INPUT (in clisp; I don't
know what SBCL does).

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2009-11-24 17:00

Message:
1. I don't see the implication that st_size means it's a constant, since
read(2) sees the data (see attached code).
2. the extra syscall is only necessary if we have see EOF already, which
is rare (who would want to read beyond EOF?) and cheap (the alternative is
signaling an error which dwarfs the cost of an extra syscall).
3. what you are saying is that tty programs should exit on the first EOF.
This is a valid point.

how about a new CLEAR-EOF function which would remove that EOF marker from
the stream and try reading again?

----------------------------------------------------------------------

Comment By: Bruno Haible (haible)
Date: 2009-11-23 20:37

Message:
There are three reasons for remembering that EOF has happened on an input
stream:
1) For regular files and block devices: The normal situation
is that a file's size does not change while it is being read
by an application. This is the only supported situation.
The mere fact that stat() returns an st_size information
indicates that files are supposed to stay at the same size
while they are being accessed. ("tail -f" being a notable
exception.)
2) I cannot imagine that an implementation can do the behaviour
that you suggest without doing additional system calls. In
other words, the price that SBCL users pay for SBCL's behaviour
are more system calls. But Linus taught us: Optimize for the
frequent case, not for the infrequent case. Here the frequent
case is that files don't change in size. Can you implement
SBCL's behaviour without extra system calls in this case?
I don't believe so.
3) For character devices such as ttys: It is important that
applications don't call read() a second time after they
EOF. Because when the an application reads from standard
input, the user should need to press Ctrl-D *once* to
terminate the input. If the user needs to press Ctrl-D
twice (as is the case e.g. with some versions of the 'patch'
program), it is a bug.

Finally, regarding files in the Linux /proc/ file system: They
look like regular files of size 0, but they don't behave like
regular files. Rather they behave like pipes. My proposal to
make them look like pipes was unfortunately rejected by Linus.
So, you have to apply a heuristic, and treat either all "regular"
files under /proc or all "regular" files of size 0 as pipes.
I think clisp already does this.

Regarding <http://article.gmane.org/gmane.lisp.clisp.general/13172>:
> if ... there is no data ready in the com port, I receive the eof-value,
as expected.
If Windows COM ports are supposed to behave like this (i.e. if unlike
pipes,
reading does not wait) then you have to create a new stream in order to
restart
reading from COM. But honestly, that sounds more like a bug, either in
Windows
or in clisp's detection whether input is available on a stream. In any
case, this
is not a reason for changing the fundamentals of the stream design in
clisp.

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2009-11-23 15:44

Message:
just to clarify, this behavior can cause problems with special files
("COM1" on woe32 and "/proc/*" on unix).
<http://article.gmane.org/gmane.lisp.clisp.general/13172>

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2902716&group_id=1355

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

[ clisp-Bugs-2903819 ] return character (cygwin?)

2009-11-25T08:05:17Z

Bugs item #2903819, was opened at 2009-11-25 10:52
Message generated for change (Comment added) made by sds
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2903819&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
>Group: lisp error
>Status: Pending
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: TheBeaNerd (thebeanerd)
>Assigned to: Sam Steingold (sds)
Summary: return character (cygwin?)

Initial Comment:
There seems to be an issue with the return character generated by the following code (at least under cygwin).

In particular, executing the form:

(with-open-file (stream "test.sh" :direction :output)
(format stream "#!/bin/sh~%~%")
(format stream "echo \"howdy\"~%"))

Then, at the shell:

$> chmod +x test.sh
$> ./test.sh
./test.sh line 2: $'\r' : command not found
howdy

Note the "command not found" message.

This issue effects applications such as ACL2 built using CLISP under cygwin.

----------------------------------------------------------------------

>Comment By: Sam Steingold (sds)
Date: 2009-11-25 11:05

Message:
this is not a bug. CUSTOM:*DEFAULT-FILE-ENCODING* defaults to :DOS on
cygwin, so #\Newline is printed as "\r\n' (CRLF).
try (with-open-file (stream "test.sh" :direction :output :external-format
:unix) (format stream "#!/bin/sh~%~%echo \"howdy\"~%"))

required reading:
http://clisp.cons.org/impnotes/encoding.html#newline
http://clisp.cons.org/impnotes/clhs-newline.html
http://clisp.cons.org/impnotes/encoding.html#def-file-enc
http://clisp.cons.org/impnotes/open.html#extfmt

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2009-11-25 11:05

Message:
This bug report is now marked as "pending"/"invalid".
This means that we think that the problem you report is not a problem with
CLISP.
Unless you - the reporter - act within 2 weeks, the bug will be
permanently closed.
Sorry about the inconvenience - we hope your silence means that you agree
that this is not a bug in CLISP.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2903819&group_id=1355

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

[ clisp-Bugs-2903819 ] return character (cygwin?)

2009-11-25T07:52:25Z

Bugs item #2903819, was opened at 2009-11-25 15:52
Message generated for change (Tracker Item Submitted) made by thebeanerd
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2903819&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: segfault
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: TheBeaNerd (thebeanerd)
Assigned to: Bruno Haible (haible)
Summary: return character (cygwin?)

Initial Comment:
There seems to be an issue with the return character generated by the following code (at least under cygwin).

In particular, executing the form:

(with-open-file (stream "test.sh" :direction :output)
(format stream "#!/bin/sh~%~%")
(format stream "echo \"howdy\"~%"))

Then, at the shell:

$> chmod +x test.sh
$> ./test.sh
./test.sh line 2: $'\r' : command not found
howdy

Note the "command not found" message.

This issue effects applications such as ACL2 built using CLISP under cygwin.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2903819&group_id=1355

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

[ clisp-Bugs-2902716 ] clisp does not notice when the file on disk has been changed

2009-11-24T16:07:20Z

Bugs item #2902716, was opened at 2009-11-23 15:35
Message generated for change (Comment added) made by sds
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2902716&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: lisp error
Status: Closed
Resolution: Rejected
Priority: 5
Private: No
Submitted By: Sam Steingold (sds)
Assigned to: Bruno Haible (haible)
Summary: clisp does not notice when the file on disk has been changed

Initial Comment:
when clisp reaches eof, it remembers it and never clears the condition even if when the file on disk changes.
sbcl and C (both FILE/fopen and int/fd/open interfaces) do not exhibit this behavior.

----------------------------------------------------------------------

>Comment By: Sam Steingold (sds)
Date: 2009-11-24 19:07

Message:
nope,
(let ((fname "test-eof"))
(open fname :direction :probe :if-exists :overwrite ; touch
:if-does-not-exist :create)
(unwind-protect
(with-open-file (in fname :direction :input)
(list (read-line in nil :eof)
(progn
(with-open-file (out fname :direction :output
:if-exists :append)
(write-line "foo" out))
(clear-input in)
(read-line in nil :eof))))
(delete-file fname)))
==> (:EOF :EOF) instead of (:EOF "foo")

----------------------------------------------------------------------

Comment By: Bruno Haible (haible)
Date: 2009-11-24 18:16

Message:
> how about a new CLEAR-EOF function which would remove that EOF marker
from
> the stream and try reading again?

This function already exists. It is part of CLEAR-INPUT (in clisp; I don't
know what SBCL does).

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2009-11-24 17:00

Message:
1. I don't see the implication that st_size means it's a constant, since
read(2) sees the data (see attached code).
2. the extra syscall is only necessary if we have see EOF already, which
is rare (who would want to read beyond EOF?) and cheap (the alternative is
signaling an error which dwarfs the cost of an extra syscall).
3. what you are saying is that tty programs should exit on the first EOF.
This is a valid point.

how about a new CLEAR-EOF function which would remove that EOF marker from
the stream and try reading again?

----------------------------------------------------------------------

Comment By: Bruno Haible (haible)
Date: 2009-11-23 20:37

Message:
There are three reasons for remembering that EOF has happened on an input
stream:
1) For regular files and block devices: The normal situation
is that a file's size does not change while it is being read
by an application. This is the only supported situation.
The mere fact that stat() returns an st_size information
indicates that files are supposed to stay at the same size
while they are being accessed. ("tail -f" being a notable
exception.)
2) I cannot imagine that an implementation can do the behaviour
that you suggest without doing additional system calls. In
other words, the price that SBCL users pay for SBCL's behaviour
are more system calls. But Linus taught us: Optimize for the
frequent case, not for the infrequent case. Here the frequent
case is that files don't change in size. Can you implement
SBCL's behaviour without extra system calls in this case?
I don't believe so.
3) For character devices such as ttys: It is important that
applications don't call read() a second time after they
EOF. Because when the an application reads from standard
input, the user should need to press Ctrl-D *once* to
terminate the input. If the user needs to press Ctrl-D
twice (as is the case e.g. with some versions of the 'patch'
program), it is a bug.

Finally, regarding files in the Linux /proc/ file system: They
look like regular files of size 0, but they don't behave like
regular files. Rather they behave like pipes. My proposal to
make them look like pipes was unfortunately rejected by Linus.
So, you have to apply a heuristic, and treat either all "regular"
files under /proc or all "regular" files of size 0 as pipes.
I think clisp already does this.

Regarding <http://article.gmane.org/gmane.lisp.clisp.general/13172>:
> if ... there is no data ready in the com port, I receive the eof-value,
as expected.
If Windows COM ports are supposed to behave like this (i.e. if unlike
pipes,
reading does not wait) then you have to create a new stream in order to
restart
reading from COM. But honestly, that sounds more like a bug, either in
Windows
or in clisp's detection whether input is available on a stream. In any
case, this
is not a reason for changing the fundamentals of the stream design in
clisp.

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2009-11-23 15:44

Message:
just to clarify, this behavior can cause problems with special files
("COM1" on woe32 and "/proc/*" on unix).
<http://article.gmane.org/gmane.lisp.clisp.general/13172>

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2902716&group_id=1355

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

[ clisp-Bugs-2902716 ] clisp does not notice when the file on disk has been changed

2009-11-24T15:16:03Z

Bugs item #2902716, was opened at 2009-11-23 21:35
Message generated for change (Comment added) made by haible
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2902716&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: lisp error
Status: Closed
Resolution: Rejected
Priority: 5
Private: No
Submitted By: Sam Steingold (sds)
Assigned to: Bruno Haible (haible)
Summary: clisp does not notice when the file on disk has been changed

Initial Comment:
when clisp reaches eof, it remembers it and never clears the condition even if when the file on disk changes.
sbcl and C (both FILE/fopen and int/fd/open interfaces) do not exhibit this behavior.

----------------------------------------------------------------------

>Comment By: Bruno Haible (haible)
Date: 2009-11-25 00:16

Message:
> how about a new CLEAR-EOF function which would remove that EOF marker
from
> the stream and try reading again?

This function already exists. It is part of CLEAR-INPUT (in clisp; I don't
know what SBCL does).

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2009-11-24 23:00

Message:
1. I don't see the implication that st_size means it's a constant, since
read(2) sees the data (see attached code).
2. the extra syscall is only necessary if we have see EOF already, which
is rare (who would want to read beyond EOF?) and cheap (the alternative is
signaling an error which dwarfs the cost of an extra syscall).
3. what you are saying is that tty programs should exit on the first EOF.
This is a valid point.

how about a new CLEAR-EOF function which would remove that EOF marker from
the stream and try reading again?

----------------------------------------------------------------------

Comment By: Bruno Haible (haible)
Date: 2009-11-24 02:37

Message:
There are three reasons for remembering that EOF has happened on an input
stream:
1) For regular files and block devices: The normal situation
is that a file's size does not change while it is being read
by an application. This is the only supported situation.
The mere fact that stat() returns an st_size information
indicates that files are supposed to stay at the same size
while they are being accessed. ("tail -f" being a notable
exception.)
2) I cannot imagine that an implementation can do the behaviour
that you suggest without doing additional system calls. In
other words, the price that SBCL users pay for SBCL's behaviour
are more system calls. But Linus taught us: Optimize for the
frequent case, not for the infrequent case. Here the frequent
case is that files don't change in size. Can you implement
SBCL's behaviour without extra system calls in this case?
I don't believe so.
3) For character devices such as ttys: It is important that
applications don't call read() a second time after they
EOF. Because when the an application reads from standard
input, the user should need to press Ctrl-D *once* to
terminate the input. If the user needs to press Ctrl-D
twice (as is the case e.g. with some versions of the 'patch'
program), it is a bug.

Finally, regarding files in the Linux /proc/ file system: They
look like regular files of size 0, but they don't behave like
regular files. Rather they behave like pipes. My proposal to
make them look like pipes was unfortunately rejected by Linus.
So, you have to apply a heuristic, and treat either all "regular"
files under /proc or all "regular" files of size 0 as pipes.
I think clisp already does this.

Regarding <http://article.gmane.org/gmane.lisp.clisp.general/13172>:
> if ... there is no data ready in the com port, I receive the eof-value,
as expected.
If Windows COM ports are supposed to behave like this (i.e. if unlike
pipes,
reading does not wait) then you have to create a new stream in order to
restart
reading from COM. But honestly, that sounds more like a bug, either in
Windows
or in clisp's detection whether input is available on a stream. In any
case, this
is not a reason for changing the fundamentals of the stream design in
clisp.

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2009-11-23 21:44

Message:
just to clarify, this behavior can cause problems with special files
("COM1" on woe32 and "/proc/*" on unix).
<http://article.gmane.org/gmane.lisp.clisp.general/13172>

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2902716&group_id=1355

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel

[ clisp-Bugs-2902716 ] clisp does not notice when the file on disk has been changed

2009-11-24T14:00:43Z

Bugs item #2902716, was opened at 2009-11-23 15:35
Message generated for change (Comment added) made by sds
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2902716&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: lisp error
Status: Closed
Resolution: Rejected
Priority: 5
Private: No
Submitted By: Sam Steingold (sds)
Assigned to: Bruno Haible (haible)
Summary: clisp does not notice when the file on disk has been changed

Initial Comment:
when clisp reaches eof, it remembers it and never clears the condition even if when the file on disk changes.
sbcl and C (both FILE/fopen and int/fd/open interfaces) do not exhibit this behavior.

----------------------------------------------------------------------

>Comment By: Sam Steingold (sds)
Date: 2009-11-24 17:00

Message:
1. I don't see the implication that st_size means it's a constant, since
read(2) sees the data (see attached code).
2. the extra syscall is only necessary if we have see EOF already, which
is rare (who would want to read beyond EOF?) and cheap (the alternative is
signaling an error which dwarfs the cost of an extra syscall).
3. what you are saying is that tty programs should exit on the first EOF.
This is a valid point.

how about a new CLEAR-EOF function which would remove that EOF marker from
the stream and try reading again?

----------------------------------------------------------------------

Comment By: Bruno Haible (haible)
Date: 2009-11-23 20:37

Message:
There are three reasons for remembering that EOF has happened on an input
stream:
1) For regular files and block devices: The normal situation
is that a file's size does not change while it is being read
by an application. This is the only supported situation.
The mere fact that stat() returns an st_size information
indicates that files are supposed to stay at the same size
while they are being accessed. ("tail -f" being a notable
exception.)
2) I cannot imagine that an implementation can do the behaviour
that you suggest without doing additional system calls. In
other words, the price that SBCL users pay for SBCL's behaviour
are more system calls. But Linus taught us: Optimize for the
frequent case, not for the infrequent case. Here the frequent
case is that files don't change in size. Can you implement
SBCL's behaviour without extra system calls in this case?
I don't believe so.
3) For character devices such as ttys: It is important that
applications don't call read() a second time after they
EOF. Because when the an application reads from standard
input, the user should need to press Ctrl-D *once* to
terminate the input. If the user needs to press Ctrl-D
twice (as is the case e.g. with some versions of the 'patch'
program), it is a bug.

Finally, regarding files in the Linux /proc/ file system: They
look like regular files of size 0, but they don't behave like
regular files. Rather they behave like pipes. My proposal to
make them look like pipes was unfortunately rejected by Linus.
So, you have to apply a heuristic, and treat either all "regular"
files under /proc or all "regular" files of size 0 as pipes.
I think clisp already does this.

Regarding <http://article.gmane.org/gmane.lisp.clisp.general/13172>:
> if ... there is no data ready in the com port, I receive the eof-value,
as expected.
If Windows COM ports are supposed to behave like this (i.e. if unlike
pipes,
reading does not wait) then you have to create a new stream in order to
restart
reading from COM. But honestly, that sounds more like a bug, either in
Windows
or in clisp's detection whether input is available on a stream. In any
case, this
is not a reason for changing the fundamentals of the stream design in
clisp.

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2009-11-23 15:44

Message:
just to clarify, this behavior can cause problems with special files
("COM1" on woe32 and "/proc/*" on unix).
<http://article.gmane.org/gmane.lisp.clisp.general/13172>

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2902716&group_id=1355

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
clisp-devel mailing list
clisp-devel@...
https://lists.sourceforge.net/lists/listinfo/clisp-devel