PragDave: Playing with a Testing Library
I'd like to be able to express my unit tests fairly naturally, using the conditional operators built into the language. So, for example, I'd want to write: expect(factorial(5)) == 120 expect(factorial(10)) > 10000 I'd like the error messages to show both the code that caused the error and the values that caused the error. So, for example, I'd want the following (incorrect) test expect(factorial(6
PragDave: The 'Language' in Domain-Specific Language Doesn't Mean English (or French, or Japanese, or ...)
The 'Language' in Domain-Specific Language Doesn't Mean English (or French, or Japanese, or ...) I'm a really big fan of Domain-Specific Languages. Andy and I plugged them back in '98 when writing The Pragmatic Programmer. I've written my share of them over the years, and I've used even more. Which is why it is distressing to see that a whole group of developers are writing DSLs (and discussing DS
PragDave: Pipelines Using Fibers in Ruby 1.9
Users of the command line are familiar with the idea of building pipelines: a chain of simple commands strung together to the output of one becomes the input of the next. Using pipelines and a basic set of primitives, shell users can accomplish some sophisticated tasks. Here's a basic Unix shell pipeline that reports the ten longest .tip files in the current directory, based on the number of lines
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
PragDave: Two New Groovy Titles
