Thanks a lot for your very kind words!
I'm glad our work and contributions to this wonderful project are being
appreciated so much!
Guillaume
On Tue, Apr 12, 2016 at 8:56 PM, Gerald Wiltse
wrote:
> For what it's worth, your blog, and your presentations have kept me very
> motivated about learni
For what it's worth, your blog, and your presentations have kept me very
motivated about learning Groovy. I still refer to them often. Also, I can
say the same about many of the contributors and people on this list as
well. I am grateful to all.
Gerald R. Wiltse
jerrywil...@gmail.com
On Tue, Apr
Ah ah, yes, it's been such a long time, and I've got such a huge backlog :-O
I'd need to automate that process, because it's quite time consuming, and
perhaps even gather a team of a handful of us to collaborate, collect and
curate all those news items!
Resurrecting has been on my long todo list fo
Also, looking forward to a fresh post soon... will you have time to do one?
http://glaforge.appspot.com/
Gerald R. Wiltse
jerrywil...@gmail.com
On Tue, Apr 12, 2016 at 12:58 PM, Gerald Wiltse
wrote:
> Yes you are right about the readLine(). I remember now that my problem
> was actually that
Yes you are right about the readLine(). I remember now that my problem was
actually that the inputStream created by withStreams has "readLines()"
method but not a "readLine()" method. Then I could process each line
directly from the intputStream wouldn't even need the reader.
Gerald R. Wiltse
jer
Oh and actually, when you do input.withReader { reader -> ... }
this is actually a BufferedReader that Groovy gives you.
So you can use BufferedReader's readLine() method!
On Tue, Apr 12, 2016 at 6:39 PM, Guillaume Laforge
wrote:
> Ah good point.
> Well, it's possible to break out of the eachLin
Ah good point.
Well, it's possible to break out of the eachLine call... by throwing an
exception, although it makes the code a little less elegant obviously.
On Tue, Apr 12, 2016 at 6:27 PM, Gerald Wiltse
wrote:
> Thank you for the response!
>
> I had it that way when I started. The problem wit
Thank you for the response!
I had it that way when I started. The problem with using reader.eachLine{}
is there is no way to break out after a specific number of lines have been
received (other than using a GroovyRuntimeException, which is undesirable).
Ref:
http://stackoverflow.com/ques
You can do an input.withReader { reader -> ... } to have a buffered reader
on the input stream.
And with that reader, you can do reader.eachLine { String s -> ... } to
iterate over all the lines.
Last interesting nugget, there's also the class groovy.io.LineColumnReader
potentially, if you're inter
I'm trying to use a "ServerSocket" to receive HTTP messages from a client
which is POSTing them as chunked. I just want to capture the text content
being posted (plain text). Any input on how to do this better would be
welcomed.
Here is my existing and very not-elegant solution. When dealing wi
Hi, any update here? Could you give me some input for further investigation?
2016-04-11 12:58 GMT+02:00 Serega Sheypak :
> *>you wrote there are 20 such replacement cases... executing 20 scripts is
> hardly a problem, so it must happen in a loop...*
> Sorry, didn't understand, what do you mean by
11 matches
Mail list logo