203 Matching Annotations
  1. Feb 2014
    1. The testimony makes it manifest that he was a special police officer to some extent identified with the work of the prosecutor's office, and that position, upon well-settled grounds of public policy, required him to assist, at least, in the prosecution of offenders against the law. The services he rendered, in this instance, must be presumed to have been rendered in pursuance of that public duty, and for its performance he was not entitled to receive a special quid pro quo.
      • Court finds sufficient evidence to characterize this fellow as a public official.

      • His interaction with the prosecutor's office weighed in as a factor in suggesting he had a legal duty.

      • Since he is characterized within the rule as a public official, he cannot, as a matter of law, receive a reward for the performance of his duties.

    1. Reasoning The reasoning gives the reader insight into how the court arrived at its decision. It is instructive in nature. Courts often back their holdings with several lines of reasoning, each of which should be summarized in this section. Unnecessary repetition of facts or the issue should be avoided. A court�s rationale for its holding might be a simple explanation of its thought process. Alternatively, the reasoning might be based on the plain language of the statute, Congressional intent, the re-enactment doctrine, or other common means of resolving judicial disputes.

      Several lines of reasoning may be used to back the Court's holdings and may be:

      • a simple explanation of the Court's thought processes
      • based on the plain language of the statute
      • congressional intent
      • re-enactment doctrine
      • other common means of resolving judicial disputes (what are those?)
  2. Jan 2014
    1. Once you abandon entirely the crazy idea that the type of a value has anything whatsoever to do with the storage, it becomes much easier to reason about it. Of course, my point above stands: you don't need to reason about it unless you are writing unsafe code or doing some sort of heavy interoperating with unmanaged code. Let the compiler and the runtime manage the lifetime of your storage locations; that's what its good at.

      Understanding what you should (and should not) reason about in the language you are using is an important part of good programming; and a language that lets you reason (nee worry) about only the things you need to worry about is an important part of a good programming language.