eigenraven

#!/bin/bash

# To run you need to:
# * Have compiled mem_sim.c to mem_sim in the same folder
# * Have mem_trace.txt in the same folder as this script
# * Save the script as sums.sh
# * Run: chmod +x sums.sh
# * Run: ./sums.sh

declare -A checksums

MPThLee

/**
  * !!!! This code doesn't work anymore !!!!
  * 
  * - You can check working code on comments. I won't update this code anymore.
  *
  * Also, I just decided to remove this code. You can check revisions for old code.
  * Since this code was made for discord client that almost 5 years ago, It seems like doesn't work anymore.
  * I don't want people keep arguing in the comments, i decided to remove this code.
  *
  * Note: This code is now fulfilled with Javascript comments. This code won't work even if you pasted to console. doesn't do anything.

yougg

// +build windows

//go:generate go build -ldflags "-s -w -extldflags '-static'" $GOFILE
package main

import (
	"fmt"
	"syscall"
	"unsafe"
)

nkcmr

Informal Golang Proposal: catch block as an alternative to if err != nil

PLEASE NOTE: I am not a language designer or have any experience in implementing or mainting a language or compiler. So, I would love to write out the EBNF syntax for what I am about to propose, but alas, I wouldn't know where to start. So, please forgive the informal nature of the proposal and feel free to ask questions; hopefully I'll be able to keep up with actual experts in this field and if not I apologize for my naivety in advance!

When the try() proposal was closed, I was relieved. There is a problem to be solved here, but try, to me at least, created more problems while trying to solve one.

The main problems, I think it created were the following:

• try reduced the visiblility of failures. For example:

lunasorcery

/* So how does this work?
I'm using ANSI escape sequences to control the behavior of the terminal while
cat is outputting the text. I deliberately place these control sequences inside
comments so the C++ compiler doesn't try to treat them as code.*/
//
/*The commands in the fake code comment move the cursor to the left edge and
clear out the line, allowing the fake code to take the place of the real code.
And this explanation uses similar commands to wipe itself out too. */
//
#include <cstdio>

pudquick

brew is a bad neighbor

This isn't a guide about locking down homebrew so that it can't touch the rest of your system security-wise.

This guide doesn't fix the inherent security issues of a package management system that will literally yell at you if you try to do something about "huh, maybe it's not great my executables are writeable by my account without requiring authorization first".

But it absolutely is a guide about shoving it into its own little corner so that you can take it or leave it as you see fit, instead of just letting the project do what it likes like completely taking over permissions and ownership of a directory that might be in use by other software on your Mac and stomping all over their contents.

By following this guide you will:

• Never have to run sudo to forcefully change permissions of some directory to be owned by your account