Re: require macro/function [was clojure.contrib.[duck-streams io]]

2010-02-03 Thread Michał Marczyk
On 3 February 2010 17:14, Stephen C. Gilardi wrote: > I believe it's also possible to make the change backward compatible so > arguments to the new require macro would work quoted or not. (by detecting > and ignoring (quote ...) special forms in arguments). That's a good idea! A simple-minded m

Re: require macro/function [was clojure.contrib.[duck-streams io]]

2010-02-03 Thread ataggart
On Feb 3, 10:06 am, Stuart Sierra wrote: > On Feb 2, 8:40 pm, Stuart Halloway wrote: > > > SS: is require* an acceptable name for the function version? > > I don't care what it's called so long as there's a function there. > While we're at it, I want import* back as a function. > > -SS Out of

Re: require macro/function [was clojure.contrib.[duck-streams io]]

2010-02-03 Thread Stuart Sierra
On Feb 2, 8:40 pm, Stuart Halloway wrote: > SS: is require* an acceptable name for the function version? I don't care what it's called so long as there's a function there. While we're at it, I want import* back as a function. -SS -- You received this message because you are subscribed to the G

Re: require macro/function [was clojure.contrib.[duck-streams io]]

2010-02-03 Thread Stephen C. Gilardi
On Feb 2, 2010, at 8:40 PM, Stuart Halloway wrote: > In teaching people Clojure, non-intuitive behavior with use/require is the #1 > problem for beginners, by a mile. I believe we need both ordinary function > and macro versions, and I am pretty sure that a well-considered patch > implementing

require macro/function [was clojure.contrib.[duck-streams io]]

2010-02-02 Thread Stuart Halloway
In teaching people Clojure, non-intuitive behavior with use/require is the #1 problem for beginners, by a mile. I believe we need both ordinary function and macro versions, and I am pretty sure that a well- considered patch implementing this would be accepted. SS: is require* an acceptable n

Re: clojure.contrib.[duck-streams io]

2010-02-02 Thread Michał Marczyk
On 2 February 2010 16:05, Stuart Sierra wrote: > On Feb 2, 2:46 am, ataggart wrote: >> On a related note, it is my sincere hope that we get a version of >> require and use which no longer require (ha!) the use of quoted >> parens. > > Absolutely not!  Having 'require' as an ordinary function (not

Re: clojure.contrib.[duck-streams io]

2010-02-02 Thread ataggart
And of course, that *does* work, thus my complaint was moot, and the symbol non-resolution was probably what Stuart was so aghast about (even though it wasn't my point). As Michael said: I wish I'd realised that just before posting rather than just after :) On Feb 2, 10:50 am, ataggart wrote:

Re: clojure.contrib.[duck-streams io]

2010-02-02 Thread ataggart
And of course that should be (require '[clojure.contrib string io]) or (require ['clojure.contrib 'string 'io]) so the symbols don't try to get resolved. On Feb 2, 10:41 am, ataggart wrote: > On Feb 2, 7:05 am, Stuart Sierra wrote: > > > On Feb 2, 2:46 am, ataggart wrote: > > > > On a related n

Re: clojure.contrib.[duck-streams io]

2010-02-02 Thread ataggart
On Feb 2, 7:05 am, Stuart Sierra wrote: > On Feb 2, 2:46 am, ataggart wrote: > > > On a related note, it is my sincere hope that we get a version of > > require and use which no longer require (ha!) the use of quoted > > parens. > > Absolutely not!  Having 'require' as an ordinary function (not

Re: clojure.contrib.[duck-streams io]

2010-02-02 Thread Michael Wood
On 2 February 2010 17:36, Michael Wood wrote: > On 2 February 2010 17:05, Stuart Sierra wrote: >> On Feb 2, 2:46 am, ataggart wrote: >>> On a related note, it is my sincere hope that we get a version of >>> require and use which no longer require (ha!) the use of quoted >>> parens. >> >> Absolut

Re: clojure.contrib.[duck-streams io]

2010-02-02 Thread Michael Wood
On 2 February 2010 17:05, Stuart Sierra wrote: > On Feb 2, 2:46 am, ataggart wrote: >> On a related note, it is my sincere hope that we get a version of >> require and use which no longer require (ha!) the use of quoted >> parens. > > Absolutely not!  Having 'require' as an ordinary function (not

Re: clojure.contrib.[duck-streams io]

2010-02-02 Thread Stuart Sierra
On Feb 1, 9:23 pm, OGINO Masanori wrote: > Can I write a code on both 1.1 and master using duck-streams/io? For now, yes, as ataggart showed. But I expect names in contrib will be in flux for the next few weeks, so you should probably pick a release and stick with it. -SS -- You received this

Re: clojure.contrib.[duck-streams io]

2010-02-02 Thread Stuart Sierra
On Feb 2, 2:46 am, ataggart wrote: > On a related note, it is my sincere hope that we get a version of > require and use which no longer require (ha!) the use of quoted > parens. Absolutely not! Having 'require' as an ordinary function (not a macro) is important for code-generating code. -SS -

Re: clojure.contrib.[duck-streams io]

2010-02-02 Thread OGINO Masanori
Thank you. I try to use use function and it works, too. -- Name: OGINO Masanori (荻野 雅紀) E-mail: masanori.og...@gmail.com -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts

Re: clojure.contrib.[duck-streams io]

2010-02-01 Thread ataggart
On a related note, it is my sincere hope that we get a version of require and use which no longer require (ha!) the use of quoted parens. Thankfully the ns macro will work with solely nested vectors. -- You received this message because you are subscribed to the Google Groups "Clojure" group. T

Re: clojure.contrib.[duck-streams io]

2010-02-01 Thread ataggart
On Feb 1, 6:23 pm, OGINO Masanori wrote: > Hello. > > I built master branch of clojure and clojure-contrib and then I found > that there is no duck-streams. io exists. > > Can I write a code on both 1.1 and master using duck-streams/io? > > FYI, I want something like this Python code in Clojure

clojure.contrib.[duck-streams io]

2010-02-01 Thread OGINO Masanori
Hello. I built master branch of clojure and clojure-contrib and then I found that there is no duck-streams. io exists. Can I write a code on both 1.1 and master using duck-streams/io? FYI, I want something like this Python code in Clojure: try: from clojure.contrib.io import reader