■_
・シルバーウィーク
なんかわりと違和感なく受け入れて使っている人が多いみたいですね。
自分はどうも積極的に使う気にはならんのですが(止めろという気もない)。
2009年09月19日
■_
・ぐすたふ
(う)さんのついったでの呟きを眺めてたら、たださんのところのにゃんこの名前に対する
突込みらしいタイミングで「カール・グスタフ」と。
んー、わたしはグスタフというとこの人が真っ先に思い浮かぶのですが、
ほかにはいないんでしょうかねえw。
→
グスタフ2世アドルフ (スウェーデン王) - Wikipedia
読んだ
エニグマ・コードを解読せよ
買ったのはだいぶ前のはずなんですが、例によってこれまで積まれてましたw
んで、感想などですが、見事にアマゾンのレビューと重なってしまう内容で面白くない(^^;
もうちょっとチューリングを中心として、プレッチレーパークのエピソードがあると期待してたんですが。
まあ、太平洋戦線での「コードトーカー」の話は知らないエピソードもあったので
それは良かったんですが、全体としてはちょっとはずしたかなあと。
少しだけ解読の戦術的な内容も載っていますが、殆どは関係者達の回顧録を集めたような構成です。
という指摘はそのとおりだと思います。
■_
reddit からネタ拾い。 ただし大元だけw
"When they talk about code re-use around here, they mean cut and paste." : programming I test code as part of my job with a medium-sized, world-wide corporation that develops software. Today, I ran into a problem where I thought there shouldn't be any. I went to one of the programming gurus here to inquire, as he originally programmed this bit of functionality that was since applied by other programmers. We checked out the applicable code and took a look. I don't get a chance to look at the code much, but when I do, I always come away a bit queasy. Today's problem has to do with the title above. That's the exact quote the programmer gave me. I was horrified; he less so, since he long ago resigned himself to grappling with the sub-standard coding that goes on around here. I remarked to him that what goes on violates the principle of orthogonality. "And encapsulation," he added. He went on. "Take a look at this class. It's 15,000 lines long." Anyone here dealing with this kind of horror show?
■_ ちっ
reddit 経由で見つけた Never mind the language, the programmer is what matters | Psychology of Programming を元に話を広げようとしたら2000年の話じゃないか。あー、このページ自体は今書いたものか。
Never mind the language, the programmer is what matters | Psychology of Programming Another piece of old research. It’s so interesting, though, I can’t help putting a note up about it. In a piece of research released in 2000, Lutz Prechelt compared C, C++, Java, Perl, Python, Rexx, and Tcl. (It’s gotten a fair bit of attention before, so it’s not new material)
Never mind the language, the programmer is what matters | Psychology of Programming What’s so interesting, though, is how this demonstrates in hard numbers the importance of human variables in programming. It’s almost like framework matters less than the people using it.. funny, eh?
■_
お次は stackoverflow.com から。
What is your favorite esoteric programming language? - Stack Overflow In the spirit of "fun polls"... What is your favorite esoteric programming language? Guidelines: * One language per response, upvote to echo others' responses * If you can, describe what makes it your favorite * Provide a code sample (if practical) See Also: * Is it worth it to learn an esoteric programming language? * What is the strangest programming language you have used? * Most interesting non-mainstream language? I thought it might be nice to summarize the responses, because although there are other lists (see comments below), it turns out that this list resulted in some (arguably) non-esoteric languages getting in. Also, to my knowledge none of the other lists is ranked based on votes, but these of course are. Note that only responses with at least 1 upvote are listed below. Responses by Votes * LOLCODE * Brainfuck * Whitespace * Ook! * APL * Perl * The Shakespeare Programming Language * HOtMEfSPRIbNG * Scratch * Prolog * Lisp * Piet * LabVIEW * F# * Bash * INTERCAL * Subtext
といろいろ挙がってますが(APLとかPrlogがこのくくりで挙げられるのはなぜなんだw)、 んで、これがいいな。 使える処理系があれば使ってみたい。
What is your favorite esoteric programming language? - Stack Overflow K Language, a wild APL/Scheme crossbreed. http://en.wikipedia.org/wiki/K_programming_language Hello world: "Hello world" Compute maximum running sum inside a list of numbers: |/0(0|+)\ Sudoku solver: p,:3/:_(p:9\:!81)%3 s:{*(,x)(,/{@[x;y;:;]‘&21=x[&|/p[;y]=p]?!10}’)/&~x} N-queen solver: qn:{[n],/{:[n=#*x;,*x;,/_f'f x,\:/:(!n)_dvl,/x]}’(f:0 -1 1+/:)@!n} bd:{[p]`0:”.Q”p=\:!#p} You still think Perl is terse?
この iota ってのもなかなか。
cite="http://stackoverflow.com/questions/187715/what-is-your-favorite-esoteric-programming-language" title="What is your favorite esoteric programming language? - Stack Overflow">Iota: http://barker.linguistics.fas.nyu.edu/Stuff/Iota/#iota an unambiguous Turing-complete language with just two symbols. Iota exploits the amazing fact that any combinator (i.e. lambda-definable term) can be written using only the two combinators S (lambda (x) (lambda (y) (lambda (z) ((x z) (y z))) and K (lambda (x) (lambda (y) x). This fact is closely tied to the Curry-Howard isomorphism: the types of combinators correspond to tautologies of propositional logic. For example, the type of K is A -> B -> (B -> A). Read A, B, C as variables and -> as implication. Try S: A -> B -> C -> ((A -> C) -> (B -> C). Even more, any tautology can be derived from S and K using modus ponens. Why? The rules (for abstraction and application) in typed lambda-calculus correspond to the rules (for introduction and elimination of implication) in a natural deduction system.
■_ FQA
FAQ ではなくFQA。
Writing Your Own Toy Compiler Using Flex, Bison and LLVM : programming I find tools like Flex and Bison a bit outdated. Bison only accepts LALR(1) grammars so that means you are limited to one token of lookahead. I am not even sure if GCC uses Bison for parsing C++. For parser generators, I prefer ANTLR, it has a lot more features and works with multiple languages. But in general, I now favor a completely different approach called parser combinators, where there is no code generation, instead you express the grammar directly in the code by combining different operators (kind of like a EDSL). Although this approach is not really viable if your compiler implementation language is java or C++.It has features that are not immediately obvious if you approach it with basic yacc functionality in mind: * GLR Parsers * Reentrant Parsers limited to one token of lookahead Sure enough, wikipedia seems to state that ANTLR is LL(*). An interesting paragraph: There is contention between the "European school" of language design, who prefer LL-based grammars, and the "US-school", who predominantly prefer LR-based grammars.[citation needed] This is largely due to teaching traditions and the detailed description of specific methods and tools in certain text books; another influence may be Niklaus Wirth at ETH Zürich in Switzerland, whose research has described a number of ways of optimising LL(1) languages and compilers. I always wanted a "universal" parser generator that furthermore doesn't strip control from your hands, ie. you are the one passing input to the generated parser(s), it's not the parsers taking their own input while you stand by. So I wrote a library called Externally Driven Parser, where you specify the LR(1) grammar programmatically. It proved to be more of a programming exercise than production code :) I guess the API is horrible, performance is without doubt horrible. The code is correct, I think, though, and it passes a malloc() test very similar to the Out-Of-Memory Testing of SQLite. I used the word "universal" in the sense that Every LR(k) grammar for k > 1 can be mechanically transformed into an LR(1) grammar for the same language (quote) I am not even sure if GCC uses Bison for parsing C++. It can't, C++ has no context-free grammar. See eg. here or here. I believe I read somewhere that g++ employs a "convolution" (very wrong word here, I know) of otherwise separate compiler components; ie. the lexer, the parser, decorating with attributes all reach over to each other. Or something like that :)
C++ の構文規則は LALR(1) じゃないじゃんという話経由で C++ FQA Lite: Defective C++
C++ FQA Lite: Defective C++ This page summarizes the major defects of the C++ programming language (listing all minor quirks would take eternity). To be fair, some of the items by themselves could be design choices, not bugs. For example, a programming language doesn't have to provide garbage collection. It's the combination of the things that makes them all problematic. For example, the lack of garbage collection makes C++ exceptions and operator overloading inherently defective. Therefore, the problems are not listed in the order of "importance" (which is subjective anyway - different people are hit the hardest by different problems). Instead, most defects are followed by one of their complementary defects, so that when a defect causes a problem, the next defect in the list makes it worse.
いろいろと面白そうな回答がそろっているので、ぜひ誰か訳(ry
■_ ヲチ
Ruby 初心者スレッド Part 31 172 デフォルトの名無しさん [sage] 2009/09/19(土) 14:23:19 ID: Be: "[hoge]"とか"{hoge}"みたいな文字列の前後の括弧を取り外すのに "[hoge]".sub(/\[(.+?)\]/){$1} なんかじゃなくて、なんかもっとスマートな方法はありませんか？ 173 172 [sage] 2009/09/19(土) 14:26:22 ID: Be: できれば "[hoge]".split(//)[1...-1].join も無しの方向で。 174 デフォルトの名無しさん [sage] 2009/09/19(土) 14:28:01 ID: Be: "[hoge]"[1...-1] では駄目と申すか。 175 デフォルトの名無しさん [sage] 2009/09/19(土) 14:36:42 ID: Be: String[] の動作が期待に添っていて、短いのがスマートだと勘違いしているのなら、>>174 そのまんまの正規表現でマッチした部分を取り出す以上のわかりやすいスマートなものはないかと思われ str =~ /\A[\(\{\[<](.+?)[\)\]\}>]\Z/; $1 開きカッコの対応を取るライブラリは標準では無いので自作してくれ 176 デフォルトの名無しさん [sage] 2009/09/19(土) 14:38:04 ID: Be: というかカッコの対応は正規表現では本来書けない。 とCマガで大昔に読んだけど、最近の拡張しまくりのだと可能かもなー。 177 デフォルトの名無しさん [sage] 2009/09/19(土) 14:48:30 ID: Be: 後ろの1文字はchopで毟れるけど、先頭の1文字を毟り取るメソッドっ てないよな。 178 デフォルトの名無しさん [sage] 2009/09/19(土) 14:51:08 ID: Be: >>177 その手があったか "[hoge]".chop.reverse.chop.reverse 179 デフォルトの名無しさん [sage] 2009/09/19(土) 14:52:59 ID: Be: >>178 ちょwwwwwプwwwww 180 デフォルトの名無しさん [sage] 2009/09/19(土) 14:54:21 ID: Be: 小橋の回転チョップを思い出した 181 デフォルトの名無しさん [sage] 2009/09/19(土) 17:26:08 ID: Be: 右のほうをチョップされたら左のほうを差し出せ 182 デフォルトの名無しさん [sage] 2009/09/19(土) 20:20:22 ID: Be: ×ほう ○ほお 183 デフォルトの名無しさん [sage] 2009/09/19(土) 20:28:43 ID: Be: >>172 "[hoge]"[/\[(.+?)\]/, 1] とも書ける。 >>175 Onigurumaならできるはず。 184 デフォルトの名無しさん [sage] 2009/09/19(土) 21:00:13 ID: Be: すんません。このスレどっからドコまで自作自演なんてしょうか? 185 デフォルトの名無しさん [] 2009/09/19(土) 21:06:16 ID: Be: ココまで俺の自演
■_ 本日の巡回から
-
Programming in Haskell
A Japanese version will be published around October 2009.
- 【ミミズクの目】ネコの髭が USB 機器に「The！髭 USB メモリー」 - japan.internet.com E-コマース
- Oneliners to promote Perl
- Question: why hasn't anyone made Python generate C or asm, then compile that? : Python
- Coroが何故重要であるか - 金利0無利息キャッシング – キャッシングできます - subtech
- ライブラリのAPIデザインの間違いは早い段階で直した方が良い - 金利0無利息キャッシング – キャッシングできます - subtech
- モチベーションツール、読書記録など、Twitterを活用した新サービス4種（WIRED VISION）：ニュース
- Word is smart, but OpenOffice is wise | Pyevolve
- History of FORTRAN and FORTRAN II — Software Preservation Group
- もう娯楽で金取るっつーのが無理なのかもしれない。
- C言語って何？Cの略を教えて。 - Yahoo!知恵袋
- Scala Vs Clojure – Let’s get down to business « Best In Class – The Blog
- GHC to JavaScript backend - Trac
-
JITRewrite – Parrot
The current JIT system is not a suitable implementation of JIT for Parrot. It should be deprecated and replaced with a better system
-
何故かあたり前にならない文字エンコーディングバリデーション
Perlについては小飼 弾氏が今年になって、文字エンコーディング変換を利用した文字エンコーディングバリデーションを提案しているので、 日本のPerl開発者は一部の(先進的?)PHP開発者と同程度の対策は取るようになると思います。
Ruby、Pythonについても、何方か有名な方が文字エンコーディング変換を利用したバリデーションをする方法をブログに書くべきです。
-
MarkupDancing » 「WordPress のセキュリティ対策」を書いているときに思ったこと
プログラマやサイトマスターは、一時限りの薀蓄を語るためにつまらない「情報」を集め回るよりも、離散数学やアルゴリズムから、 他業種の業務工程まで、それで食っていくつもりなら職業人として必要な「知識」の習得に精を出すほうが絶対によい。 - 『PSPgo』、「DSi」や「iPhone」や「旧型PSP」との大きさ比較画像 : はちま起稿
- 舩坂弘 - Wikipedia
