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

None
by Dan Weinreb 18 Mar '09

18 Mar '09

1 0

Re: [iterate-devel] USA Menshealth ID216905967 Recall her senses
by $FIRST_NAMES $LAST_NAMES 05 Mar '09

05 Mar '09

1 0

[iterate-devel] I have patched iterate to accept keywords as clause heads
by Denis Budyak 26 Nov '08

26 Nov '08

Hi there. Patch is attached. Also I've added Ilya Perminov's fix for result-type with at beginning. Sorry this is one large patch... I know it is hard to read.

1 0

Re: [iterate-devel] "collect at beginning" ignores specified sequence type
by Denis Budyak 25 Nov '08

25 Nov '08

(deftest k.result-type-at-beginning.1 (iter (:for i below 2) (:collect i at beginning result-type vector)) #(1 0)) (deftest k.result-type-at-beginning.2 (iter (:for i below 2) (:collect i at beginning result-type list)) (1 0)) (deftest k.result-type-at-beginning.2a (iter (:for i below 2) (:collect i at beginning)) (1 0)) (deftest k.result-type-at-beginning.3 (iter (:for c in-string "ab") (:collect c at beginning result-type string)) "ba") Did I miss something?

1 0

[iterate-devel] I have patched iterate to accept keywords as clause heads
by Denis Budyak 25 Nov '08

25 Nov '08

Hi there! It is known that loop macro allows keywords as clause start designators: (loop :for i :from 1 :to 10 :collect i) So do many html generation libs, e.g. cl-who: (:a :href ...) Iterate didn't do that and it caused problems while using iterate in conjunction with other libraries such as cl-utilities which defines collecting and collect macros. I patched iterate so that it can use keywords now: (iter:iter (:for i :from 1 :to 5) (when (oddp i) (:collect i)) (:finally (print "hurray!"))) So one need no more to import any symbols from iterate (maybe except iter itself). I also added test of "iterate with keywords" to a regression test suite. you can find a patch and a new file here. http://paste.lisp.org/display/69869 Discussion (currently empty) can be found here: http://groups.google.com/group/comp.lang.lisp/browse_thread/thread/f252c793… Would iterate developers like to incorporate the changes to the main branch? If not, would you object against creating separate iterate-keywords project on the net? best regards Denis Budyak

3 3

[iterate-devel] problem with maybe-quoted
by Vsevolod 24 Nov '08

24 Nov '08

Hi! I'm experimenting with iterate and wanted to use it for a simple sequence splitting function (yeah, I know about the SPLIT-SEQUENCE lib): (defun split (seq pred) (iter (for el in-sequence seq) (if (funcall pred el) (collect el into sat result-type (type-of seq)) (collect el into nsat result-type (type-of seq))) (finally (return (values sat nsat))))) But such a construct won't work because result-type is recognized as a literal (not evaluated). I think it's rather a bug, than a feature, because this somewhat inhibits the possibilities of programmatic extension of the ITER macro. Isn't it? Best regards, Vsevolod

2 1

[iterate-devel] "collect at beginning" ignores specified sequence type
by Ilya Perminov 21 Nov '08

21 Nov '08

Hi, If both AT BEGINNING and RESULT-TYPE are specified, RESULT-TYPE is ignored. Example: (iter (for i below 2) (collect i at beginning result-type vector)) returns (1 0). A patch to fix this bug is attached. Best regards, Ilya

1 0

[iterate-devel] I have patched iterate to accept keywords as clause heads
by Denis Budyak 13 Nov '08

13 Nov '08

Hi there! It is known that loop macro allows keywords as clause start designators: (loop :for i :from 1 :to 10 :collect i) So do many html generation libs, e.g. cl-who: (:a :href ...) Iterate didn't do that and it caused problems while using iterate in conjunction with other libraries such as cl-utilities which defines collecting and collect macros. I patched iterate so that it can use keywords now: (iter:iter (:for i :from 1 :to 5) (when (oddp i) (:collect i)) (:finally (print "hurray!"))) So one need no more to import any symbols from iterate (maybe except iter itself). I also added test of "iterate with keywords" to a regression test suite. you can find a patch and a new file here. http://paste.lisp.org/display/69869 Discussion (currently empty) can be found here: http://groups.google.com/group/comp.lang.lisp/browse_thread/thread/f252c793… Would iterate developers like to incorporate the changes to the main branch? If not, would you object against creating separate iterate-keywords project on the net? best regards Denis Budyak

1 0

[iterate-devel] in-stream closes stream at the end: bad idea?
by daniel radetsky 22 Oct '08

22 Oct '08

Iterators: Was working with iterate, and noticed this issue. I did a quick-n-dirty fix to get rid of it (copy and paste to a new in-ostream driver). But I thought: Is there actually a good reason to close the stream at the end of the loop? Or, is there a correct way to make in-stream not close the stream that I should have been using? If not, and if there is still development going on for iterate, I can fix it up more nicely and submit a patch. My thoughts: - in-stream should, by default, not close the stream. Unlike in-file, we should expect that the stream was created by some process that will handle closing the stream at the end, such as with-open-file. - If the user wants to close the stream at the end, he should do something like (finally (close stream)). More complicated abstractions here aren't really helpful. I had also been thinking that in-stream/in-file could be modified to make it easier to pass them user-defined reading functions, but that's another post. Daniel

3 3

[iterate-devel] [SPAM] FIM DO DRAMA.
by FIM＠common-lisp.net 13 Jun '08

13 Jun '08

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: FIM DO DRAMA, CASO ISABELLA NARDONI CHEGOU AO FIM! Alexandre Nardoni confessa que a sua esposa Ana Carolina a madastra de Isabella foi a autora do crime de Isabella. [...] Content analysis details: (7.5 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 1.6 FROM_HAS_MIXED_NUMS3 From: contains numbers mixed in with letters 1.7 MSGID_FROM_MTA_ID Message-Id for external message added locally 0.7 SUBJ_ALL_CAPS Subject is all capitals 1.2 FORGED_HOTMAIL_RCVD2 hotmail.com 'From' address, but no 'Received:' 0.0 HTML_MESSAGE BODY: HTML included in message 0.2 MIME_HTML_ONLY BODY: Message only has text/html MIME parts -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 0.6 FORGED_OUTLOOK_HTML Outlook can't send HTML message only 0.0 UPPERCASE_25_50 message body is 25-50% uppercase 0.0 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE 3.9 FORGED_MUA_OUTLOOK Forged mail pretending to be from MS Outlook 0.2 AWL AWL: From: address is in the auto white-list 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