Programming Building Blocks "Where do these stairs go?""They go up." --Ray Stantz and Peter Venkman, Ghostbusters What is programming, anyway? What is programming, anyway? If you don't want a good grade, the computer can do that without your intervention. The second thing you need to get started is the knowledge of how to tell the computer to do these things. What you can do as a programmer, though, is get through the assignments doing something that works, and then look back at it and see how you could have made it better or faster or more concise. Eventually what you'll find is that the stuff you wrote back in college (e.g. The only way to go is up. 2.1. In the beginning was the planAnd then came the assumptionsAnd the assumptions were without formAnd the plan was completely without substanceAnd the darkness was upon the face of workers --Excerpt from The Plan, early Internet folklore Ooooo! Ok, maybe I'm being a little too overdramatic here. So what do you do with this specification? That didn't work? "Wait!
Git Git for Computer Scientists Abstract Quick introduction to git internals for people who are not scared by words like Directed Acyclic Graph. Storage In simplified form, git object storage is "just" a DAG of objects, with a handful of different types of objects. They are all stored compressed and identified by an SHA-1 hash (that, incidentally, isn't the SHA-1 of the contents of the file they represent, but of their representation in git). blob: The simplest object, just a bunch of bytes. tree: Directories are represented by tree object. When a node points to another node in the DAG, it depends on the other node: it cannot exist without it. commit: A commit refers to a tree that represents the state of the files at the time of the commit. refs: References, or heads or branches, are like post-it notes slapped on a node in the DAG. git commit adds a node to the DAG and moves the post-it note for current branch to this new node. The HEAD ref is special in that it actually points to another ref. History
tortoisegit - Porting TortoiseSVN to TortoiseGit Git Version of TortoiseSVN. It is a port of TortoiseSVN for Git. TortoiseGit supports you by regular tasks, such as committing, showing logs, diffing two versions, creating branches and tags, creating patches and so on (see our Screenshots or documentation). If you upgraded to TortoiseGit 184.108.40.206 and TortoisePLink reports "missing MSVCR110.dll", go to TortoiseGit settings, Network and select "TortoiseGitPLink.exe" as ssh client (which is located in the TortoiseGit\bin directory; issue #2156 ). The latest and recommended release of TortoiseGit is: 220.127.116.11, see ReleaseNotes for details. Download TortoiseGit System prerequisites and installation howto Git for Windows 1.7.10 or above (sometimes also called msysgit; the "Full installer for official Git for Windows" download package is sufficient) is also required for TortoiseGit (recommended order: install TortoiseGit first). Get a full list of screenshots. Context menu Commit Dialog Support spell check(English) and autolist Log Dialog 难道被盾了吗？ Donate
Preface Git is a version control Swiss army knife. A reliable versatile multipurpose revision control tool whose extraordinary flexibility makes it tricky to learn, let alone master. As Arthur C. Clarke observed, any sufficiently advanced technology is indistinguishable from magic. Rather than go into details, we provide rough instructions for particular effects. I’m humbled that so many people have worked on translations of these pages. Dustin Sallings, Alberto Bertogli, James Cameron, Douglas Livingstone, Michael Budde, Richard Albury, Tarmigan, Derek Mahar, Frode Aannevik, Keith Rarick, Andy Somerville, Ralf Recker, Øyvind A. François Marier maintains the Debian package originally created by Daniel Baumann. My gratitude goes to many others for your support and praise. If I’ve left you out by mistake, please tell me or just send me a patch! This guide is released under the GNU General Public License version 3. $ git clone # Creates "gitmagic" directory.
Programming a Game in OCaml Herein I'll provide an introductory taste of what it's been like making a game in OCaml. I've been developing a "Tactical RPG" game, which is based on the Ars Magica roleplaying setting and rules. Developement name is "Ars Tactica". (I haven't sought out Atlas Games about legal ramifications, deals, or licensing — not until I have something worthwhile to share!) There isn't much to show off now, but here's a screenshot: The figures are placeholders. I'm writing code, in a language which should be better known: OCaml. OCaml is an unusual choice for games. Rising awareness In the past couple of years I've watched the growing interest in functional programming with some elation. How do you make a game in a functional language? When I was first looking into OCaml (2005), it was beyond my comprehension how a (non-trivial) game could be made. Functional code favors return-values, rather than changing a variable in-place. let rec loop count = Printf.printf "Countdown: %d\n%!"
Recherche et téléchargement de fichiers sur Github Github est un service formidable où les gens stockent leurs codes sources et leurs projets... Mais c'est aussi une mine d'or de fichiers en tout genre. Certains utilisateurs de Github font d'ailleurs preuve de négligence et synchronisent même parfois des fichiers contenant des mots de passe en clair ou des infos plus ou moins confidentielles. Pour effectuer ce genre de recherches sur Github, il existe un petit script python qui permet tout simplement de récupérer sur votre ordinateur, les fichiers qui vous intéressent. Par exemple, en tapant : . vous récupérerez tous les historiques bash qui trainent. . vous récupérerez tous les htpasswd qui trainent . vous récupérez des boites mails qui trainent . et des logins/passwords de connexions à des bases de données. Je ne passe pas tout en revue. Pour installer ghrabber, il faut faire un petit : sudo easy_install pip sudo pip install beautifulsoup requests Puis téléchargez ghrabber ici. Vous avez aimé cet article ?
Understanding Git Conceptually Introduction This is a tutorial on the Git version control system. Git is quickly becoming one of the most popular version control systems in use. There are plenty of tutorials on Git already. A Story When I first started using Git, I read plenty of tutorials, as well as the user manual. After a few months, I started to understand those under-the-hood concepts. Understanding Git The conclusion I draw from this is that you can only really use Git if you understand how Git works. Half of the existing resources on Git, unfortunately, take just that approach: they walk you through which commands to run when, and expect that you should do fine if you just mimic those commands. This tutorial, then, will take a conceptual approach to Git. Go on to the next page: Repositories