[ Main Page ]

知的財産法

論文の話題

初心者なりの解釈ですが、もとはセミナーの内容の抜粋で、かなり古い文書です。

Diamond v. Diehr et al / State Street Bank Co & Trust v. Signature Finalcial Group Co / Jazz Photo Corp. and Dynatec International, Inc. and Opticolor v. International Trade Commission and Fuji Photo Film
John v. Duke University / Embrex v. Service Engineering
Bayer HealthCare LLC v. Nagrom, Inc. / Gamut Trading Co. v. United States ITC
Sony Corp. of America v. Universal City Studios, Inc.
Eric Eldred v. John D. Ashcroft
The Future of Ideas by Lawrence Lessig
Danjaq LLC v. Sony Corp.

関連文書

米国における判例法上の試験免責とボーラー条項に関する判決の展開 増岡国久
「試験又は研究」の例外について
我が国における特許権の効力が及ばない「試験又は研究」について
IT時代における紙器・ダンボール業界の特許戦略
This isn't just something that happens with programming languages. It's a
general historical trend. As technologies improve, each generation can do
things that the previous generation would have considered wasteful. People
thirty years ago would be astonished at how casually we make long distance
phone calls. People a hundred years ago would be even more astonished that a
package would one day travel from Boston to New York via Memphis.

    -- Paul Graham
    -- The Hundred-Year Language ( http://www.paulgraham.com/popular.html )

      <krang>  Hey all, what's the best way to call one perl script from
               another? I was thinking I'd just use 'system("script.pl");'
    <dazjorz>  krang: yeah, that, or do "script.pl"
    <dazjorz>  krang: depends on how seperated you want them to be
      <krang>  dazjorz: you mean just a line that has "script.pl"; written
               on it?
   <Khisanth>  you need the do as well
    <dazjorz>  krang: no, exactly this: do "script.pl";
    <rindolf>  krang: system is usually what you want.
    <rindolf>  krang: normally require or use are preferable to do
    <dazjorz>  rindolf: that's for modules, isn't it ?
    <rindolf>  dazjorz: yes.
    <dazjorz>  wait, I think require "script.pl" would work too
    <rindolf>  dazjorz: and doing code is not such a good idea.
    <dazjorz>  rindolf: hmm?
      <krang>  rindolf: what is doing anyway?
    <rindolf>  dazjorz: I mean "perldoc -f do"-ing code.
    <rindolf>  krang: do()-ing
    <rindolf>  krang: it reads the file and evaluates it.
    <rindolf>  krang: perldoc -f do.
    <dazjorz>  rindolf: ah
    <dazjorz>  rindolf: do {}
            *  rindolf would rather be doing hot models than doing code.
               :-)
    <dazjorz>  rindolf: yeah, do BLOCK is quite useless
    <dazjorz>  heh
    <rindolf>  dazjorz: you can do my $var = do { ... }
            *  dazjorz would rather be doing GumbyBRAIN than doing code
 <GumbyBRAIN>  and doing code is not be in the days of immortality!
    <rindolf>  dazjorz: or eval { ... }
    <rindolf>  dazjorz: heh.
    <rindolf>  It's hard to do code.
    <dazjorz>  do $model;
    <dazjorz>  eh.. sorry, do $hotmodel;
    <rindolf>  "Are you into my brother?"
    <rindolf>  "No I'm totally into Perl."
      <krang>  ah ok, I see. Thanks guys!
    <rindolf>  krang: yw.
    <dazjorz>  heh :-)
    <rindolf>  If you want a configuration file, you should be using
               something like INI, YAML, etc.
    <rindolf>  XML perhaps.
    <rindolf>  Something.
    <rindolf>  Apache-like config.
    <dazjorz>  Apache-like is very strong but hard to parse, right ?
    <dazjorz>  Loading and saving configuration never looks good,
               especially when it's XML
    <dazjorz>  the code to load and save is ugly.

    -- Sextalk among Perl cultists
    -- #perl, Freenode


Powered by UNIX fortune(6)
[ Main Page ]