- iterate-devel - mailman3.common-lisp.net

[iterate-devel] making sbcl depend on iterate
by Patrick X 17 Mar '07

17 Mar '07

hello i can't since to get the iterate to work via slime (asdf:operate 'asdf:load-op 'iterate) ;is how i normally load the package i tried putting the depends-on function from the site in .emacs but it didn't work. I can I make sbcl depends on iterate everytime it is fire up. reading the iterate manual i still confuse on how to open files with iterate (iterate:iter (for line in-file #p"/var/log/messages") (do (print line))) this is how i thought I should use it. -- ================================= knot in cables caused data stream to become twisted and kinked. http://groups.google.com/group/lispstl http://www.cwelug.org/ Patrick Pippen

3 2

[iterate-devel] use within a package
by Patrick X 17 Feb '07

17 Feb '07

I just installed iterate and I'd like to use it in a package i'm making, how can I include the iterate package within a program I'm writing with a defpackage. -- ================================= knot in cables caused data stream to become twisted and kinked. http://groups.google.com/group/lispstl http://www.cwelug.org/ Patrick Pippen

2 1

[iterate-devel] Request to mailing list elephant-devel rejected
by elephant-devel-bounces＠common-lisp.net 17 Jan '07

17 Jan '07

Your request to the elephant-devel mailing list Posting of your message titled "[SPAM] PRESADO CLIENTE TEVE UM PROBLEMA NO SEU EMAIL DO ORKUT VEJA E RESOLVA!!!" has been rejected by the list moderator. The moderator gave the following reason for rejecting your request: "Blind carbon copies or other implicit destinations are not allowed. Try reposting your message by explicitly including the list address in the To: or Cc: fields." Any questions or comments should be directed to the list administrator at: elephant-devel-owner(a)common-lisp.net

1 0

[iterate-devel] Your message to closer-devel awaits moderator approval
by closer-devel-bounces＠common-lisp.net 17 Jan '07

17 Jan '07

Your mail to 'closer-devel' with the subject [SPAM] PRESADO CLIENTE TEVE UM PROBLEMA NO SEU EMAIL DO ORKUT VEJA E RESOLVA!!! Is being held until the list moderator can review it for approval. We're sorry, due to the volume of spam we receive most mailinglists require you to subscribe before posting. You may cancel this post (at the URL below) or waiting for the moderator to approve it. Thanks and sorry for the inconvenience. The reason it is being held: Message has implicit destination Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://common-lisp.net/cgi-bin/mailman/confirm/closer-devel/3804add18347ae6…

1 0

[iterate-devel] Your message to cl-muproc-devel awaits moderator approval
by cl-muproc-devel-bounces＠common-lisp.net 17 Jan '07

17 Jan '07

Your mail to 'cl-muproc-devel' with the subject [SPAM] PRESADO CLIENTE TEVE UM PROBLEMA NO SEU EMAIL DO ORKUT VEJA E RESOLVA!!! Is being held until the list moderator can review it for approval. We're sorry, due to the volume of spam we receive most mailinglists require you to subscribe before posting. You may cancel this post (at the URL below) or waiting for the moderator to approve it. Thanks and sorry for the inconvenience. The reason it is being held: Message has implicit destination Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://common-lisp.net/cgi-bin/mailman/confirm/cl-muproc-devel/c3128d4e0369…

1 0

[iterate-devel] Your message to cl-darcs-devel awaits moderator approval
by cl-darcs-devel-bounces＠common-lisp.net 17 Jan '07

17 Jan '07

Your mail to 'cl-darcs-devel' with the subject [SPAM] PRESADO CLIENTE TEVE UM PROBLEMA NO SEU EMAIL DO ORKUT VEJA E RESOLVA!!! Is being held until the list moderator can review it for approval. We're sorry, due to the volume of spam we receive most mailinglists require you to subscribe before posting. You may cancel this post (at the URL below) or waiting for the moderator to approve it. Thanks and sorry for the inconvenience. The reason it is being held: Message has implicit destination Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://common-lisp.net/cgi-bin/mailman/confirm/cl-darcs-devel/2396f24b5665f…

1 0

[iterate-devel] Your message to cffi-devel awaits moderator approval
by cffi-devel-bounces＠common-lisp.net 17 Jan '07

17 Jan '07

Your mail to 'cffi-devel' with the subject [SPAM] PRESADO CLIENTE TEVE UM PROBLEMA NO SEU EMAIL DO ORKUT VEJA E RESOLVA!!! Is being held until the list moderator can review it for approval. We're sorry, due to the volume of spam we receive most mailinglists require you to subscribe before posting. You may cancel this post (at the URL below) or waiting for the moderator to approve it. Thanks and sorry for the inconvenience. The reason it is being held: Message has implicit destination Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://common-lisp.net/cgi-bin/mailman/confirm/cffi-devel/5d54c1244be30339d…

1 0

[iterate-devel] [SPAM] PRESADO CLIENTE TEVE UM PROBLEMA NO SEU EMAIL DO ORKUT VEJA E RESOLVA!!!
by iterate-devel 17 Jan '07

17 Jan '07

Spam detection software, running on the system "clnet", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Orkut Problemas com sua conta. Prezado usuário, Atenção [...] Content analysis details: (7.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.2 INVALID_DATE Invalid Date: header (not RFC 2822) 1.7 MSGID_FROM_MTA_ID Message-Id for external message added locally 0.7 SUBJ_ALL_CAPS Subject is all capitals 0.1 HTML_80_90 BODY: Message is 80% to 90% HTML 0.5 HTML_IMAGE_ONLY_24 BODY: HTML: images with 2000-2400 bytes of words -1.1 BAYES_40 BODY: Bayesian spam probability is 20 to 40% [score: 0.3128] 0.0 HTML_MESSAGE BODY: HTML included in message 0.2 MIME_HTML_ONLY BODY: Message only has text/html MIME parts 0.3 MIME_BASE64_TEXT RAW: Message text disguised using base64 encoding 0.6 FORGED_OUTLOOK_HTML Outlook can't send HTML message only 0.1 HTML_MIME_NO_HTML_TAG HTML-only message, but there is no HTML tag 0.1 FORGED_OUTLOOK_TAGS Outlook can't send HTML in this format 0.0 PLING_PLING Subject has lots of exclamation marks 0.0 MIME_BOUND_NEXTPART Spam tool pattern in MIME boundary 3.9 FORGED_MUA_OUTLOOK Forged mail pretending to be from MS Outlook The original message was not completely plain text, and may be unsafe to open with some email clients; in particular, it may contain a virus, or confirm that your address can receive spam. If you wish to view it, it may be safer to save it to a file and open it with an editor.

1 0

[iterate-devel] bug and fix, multiple nil tags in tagbody
by Henrik Hjelte 05 Dec '06

05 Dec '06

The Allegro compiler won't compile some iterate forms that expand to a tagbody form that has several nil tags. At first I thought that it was a bug with allegro, since it worked fine in sbcl, and in allegros own interpreter. But on second thought and some reading of the hyperspec, I think it is the allegro compiler that is right: hyperspec: ...The statements in a tagbody are evaluated in order from left to right, and their values are discarded. If at any time there are no remaining statements, tagbody returns nil. However, if (go tag) is evaluated, control jumps to the part of the body labeled with the tag. (Tags are compared with eql.) ... and since tags are compared with eql, how can we allow several nils? If tags with the same label was allowed, the description should say something about "the first" or "the last" tag. Now it says labeled with THE tag, singularis. I have attached two bundled darcs-patches, first a testcase that shows the problem, then a solution. I have run all tests with sbcl and allegro. As usual it turns out it was more difficult to write a test than to fix the bug. /Henrik Hjelte (TAGBODY (print "hi") NIL (print "ciao") LOOP-TOP-NIL (print "hello") NIL (print "second nil") ) ; the Allegro error is : ;;Tag NIL is used more than once ;;Problem detected when processing ;; (TAGBODY (PRINT "hi") NIL...) ;;inside (BLOCK MYTEST (TAGBODY (PRINT "hi") NIL...)) ;;inside (PROGN (BLOCK MYTEST (TAGBODY # NIL...))) ;; ;; [Condition of type PARSE-ERROR] And why these nils turn up in iterate, see the testcase in the patch for an example.

3 3

[iterate-devel] envs
by Attila Lendvai 03 Aug '06

03 Aug '06

hi! for reference see this UCW common pitfall note: Consider this code in a render method: (iter (for newval in '("a" "b" "c")) (let ((newval-1 newval)) (<ucw:a :action (setf (value test) newval-1) (<:as-html newval)))) Seems like it should work fine, the variable is even rebound, but in fact it won't work due to something that can be considered a bug, but a non-trivial to fix one. segv it's iterates 'fault'. iterate walks and macroexpands its body but doesn't modify the lexical environment while it does that, so it causes with-call/cc to get expanded with the iter's env, and not the iter's env + the let binding. attila_lendvai ehh segv (fwiw arnesi's own code walker doesn't do that either) segv this explains why it works fine with loop and dolist segv and dolist* attila_lendvai is it easy to fix? i can push to iterate, but have no experience with envs segv attila_lendvai: i requires looking through the various lisps to figure out how to do that, and fixing iterate's code-walker to do the proper environment augmentation for let, let*, flet, labels, macrolet and symbol-macrolet forms. segv doable, but not trivial. segv at that point it'd probbaly be easier to rework iterate to use arnesi's code walker (which would be easier to fix since some of the non portable environment stuff is already there) attila_lendvai hm, doesn't sound like something i would chop my axe in... :) attila_lendvai iterate is non-trivial in itself segv yup. Workarounds: - use loop or dolist until iterate is fixed. - in the ajax branch you can disable with-call/cc wrapping (which is not needed here): (iter (for newval in '("a" "b" "c")) (let ((newval newval)) (<ucw:a :action (register-action () ;; :with-call/cc is #f by default (setf (value self) newval)) (<:ah newval)))) -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" Ingmar Bergman - Smultronstället (Wild Strawberries)

1 0