diff options
author | Aaron Ball <nullspoon@iohq.net> | 2016-04-19 21:03:12 -0600 |
---|---|---|
committer | Aaron Ball <nullspoon@iohq.net> | 2016-04-19 21:03:12 -0600 |
commit | bf57edd9bbdcce8cc4ae14b8ff44434eed938600 (patch) | |
tree | ba0d95816a53c6bf4146b25a67d51b95cada4f78 /src | |
parent | 237d51c8d87f7952dcf498ec707ebd778b3842ae (diff) | |
download | oper.io-bf57edd9bbdcce8cc4ae14b8ff44434eed938600.tar.gz oper.io-bf57edd9bbdcce8cc4ae14b8ff44434eed938600.tar.xz |
Updated nullspoon github links
Now all point to their respective locations in the cgit instance at
https://oper.io/src.
Diffstat (limited to 'src')
-rw-r--r-- | src/about.ascii (renamed from src/About.ascii) | 9 | ||||
-rw-r--r-- | src/case_insensitive_matching_in_c.ascii (renamed from src/Case_Insensitive_Matching_in_C++.ascii) | 54 | ||||
-rw-r--r-- | src/index.ascii | 6 | ||||
-rw-r--r-- | src/linux:secure_authentication.ascii (renamed from src/Linux:Secure_Authentication.ascii) | 4 |
4 files changed, 40 insertions, 33 deletions
diff --git a/src/About.ascii b/src/about.ascii index 18ce3f0..1067b35 100644 --- a/src/About.ascii +++ b/src/about.ascii @@ -6,11 +6,16 @@ About == {doctitle} -link:https://iohq.net/[Iohq.net] is my attempt at contributing back to the +link:https://oper.io/[Oper.io] is my attempt at contributing back to the world's largest knowledgebase in history: the internet. Here I document my various experiences with technology and anything else I care to blog about. -link:https://github.com/nullspoon[GitHub page] +I also publish the majority of my code +link:https://oper.io/src/nullspoon[here]. If you're interested in contributing +to anything, send me an email with a pull request and we'll start working +together. + +link:https://oper.io/src/nullspoon[Code (Git)] == Who Am I diff --git a/src/Case_Insensitive_Matching_in_C++.ascii b/src/case_insensitive_matching_in_c.ascii index f27810d..5009eca 100644 --- a/src/Case_Insensitive_Matching_in_C++.ascii +++ b/src/case_insensitive_matching_in_c.ascii @@ -7,30 +7,30 @@ Case Insensitive Matching in C++ == {doctitle} I had this epiphany yesterday while working on my new command line -https://github.com/nullspoon/noteless[note-taking project] and I wanted to +https://oper.io/src/nullspoon/noteless.git[note-taking project] and I wanted to write a blog post about it since I haven't seen anyone on the internet yet take this approach (though there aren't exactly a lot blogs posts on programming -theory of this of this kind in general). - -My program is written in c+\+. It provides a search functionality very similar -to the case insensitive matching of _grep -i_ (you 'nix users should know what -I'm talking about). If you've done much in c+\+, you likely know that string -parsing is not so easy (or is it just different). Thus the question...__how to -perform case insensitive text searching in c++__. - -A few notes though before we proceed. I'm fairly new to c\+\+ (about 9 months -as a hobby) so everything I say here might not be entirely right (it'll work, -it just might not be the _best_ way). If you catch something that's wrong or -could use improvement, please send me User:Nullspoon[ an email] or leave a -comment on the link:{{TALKPAGENAME}}[ talk page]. Secondly, since this is -probably something the c++ gods have already mastered, I will be writing this -post aimed at the newer folk (since I myself am one), so bear with me if you -already know how to do this. One final note. I am still ceaselessly amazed at -how computers work, so I get fairly giddy when it comes to actual memory +theory of this kind in general). + +My program is written in C. It provides a search functionality very similar to +the case insensitive matching of _grep -i_ (you 'nix users should know what I'm +talking about). If you've done much in C, you likely know that string parsing +is not so easy (or is it just different). Thus the question...__how to perform +case insensitive text searching in c__. + +A few notes though before we proceed. I'm fairly new to c (about 1 year as a +hobby) so everything I say here might not be entirely right (it'll work, it +just might not be the _best_ way). If you catch something that's wrong or could +use improvement, please send me link:/?p=About[an email]. Secondly, since this +is probably something the C gods have already mastered, I will be writing +this post aimed at the newer folk (since I myself am one), so bear with me if +you already know how to do this. One final note. I am still ceaselessly amazed +at how computers work, so I get fairly giddy when it comes to actual memory management and whatnot. Brace yourselves... [[chars-ints-kind-of]] -== Chars == Ints (kind of) +Chars == Ints (kind of) +----------------------- To continue, we need to understand a few things about base data types in memory. @@ -74,7 +74,8 @@ Now that that's out of the way... [[a-short-char---integer-list]] -== A Short Char - Integer List +A Short Char - Integer List +--------------------------- * **! " # $ % & ' ( ) * + , - . /**: 35 - 47 @@ -90,7 +91,8 @@ Now that that's out of the way... [[lowercase-uppercase-32]] -== Lowercase == Uppercase + 32 +Lowercase == Uppercase + 32 +--------------------------- You may have noticed an interesting fact about the numbers assigned to characters in [English] computing: uppercase and lowercase letters don't have @@ -104,7 +106,8 @@ lot easier. [[piecing-it-all-together]] -== Piecing it all together +Piecing it all together +----------------------- Since characters are simply just integers, we can perform text matching via number ranges and math operators. For instance... @@ -171,8 +174,8 @@ script. Not having access to the more common symbols is a nightmare for users. If you would like to see another example, the one I wrote for case insensitive matchings in my note program can be found at -https://github.com/nullspoon/noteless/blob/master/src/lib/note.cpp in the -*note::line_matches* method. +https://oper.io/src/nullspoon/noteless.git/tree/src/common.c#n197 in the +*str_contains_case_insensitive* method. Hopefully this is useful for someone besides myself. Either way though, I'm still super excited about the ease of making real-life data programatically @@ -186,8 +189,7 @@ modified the quote a tad) Category:Programming - -Category:C\+\+ +Category:C // vim: set syntax=asciidoc: diff --git a/src/index.ascii b/src/index.ascii index 400227f..e80d541 100644 --- a/src/index.ascii +++ b/src/index.ascii @@ -119,7 +119,7 @@ Git Personal ~~~~~~~~ -* link:?p=About[About] +* link:?p=about[About] * link:?p=A_Usual_Opening[A Usual Opening] * link:?p=My_.bashrc[My .bashrc] * link:?p=Cell_Provider_Comparison[Cell Provider Comparison] @@ -140,7 +140,7 @@ Politics ~~~~~~~~ * link:?p=Aol_Email_Hacked[Aol Email Hacked] -* link:?p=Linux:Secure_Authentication[Linux:Secure Authentication] +* link:?p=linux:secure_authentication[Linux:Secure Authentication] * link:?p=Net_Neutrality[Net Neutrality] * link:?p=dont_censor_me_bro[Don't Censor Me Bro!] * link:?p=When_Innovation_is_Appropriate[When Innovation is Appropriate] @@ -232,7 +232,7 @@ Benchmarks Development ~~~~~~~~~~~ -* link:?p=Case_Insensitive_Matching_in_C\+\+[Case Insensitive Matching in C++] +* link:?p=case_insensitive_matching_in_c[Case Insensitive Matching in C] * link:?p=Finding_Prime_Factors[Finding Prime Factors] * link:?p=Digraphs[Digraphs] * link:?p=Writing_an_Array_to_Sql_Conversion_Function[Writing an Array to Sql Conversion Function] diff --git a/src/Linux:Secure_Authentication.ascii b/src/linux:secure_authentication.ascii index 9b21934..57b51d1 100644 --- a/src/Linux:Secure_Authentication.ascii +++ b/src/linux:secure_authentication.ascii @@ -2,13 +2,13 @@ Linux:Secure Authentication =========================== :author: Aaron Ball :email: nullspoon@iohq.net -:github: https://github.com/nullspoon/ +:git: https://oper.io/src/nullspoon/ == {doctitle} **Edit**: I wrote the script for automating this finally. It can be found on my -link:{github}/keymanage[GitHub]. +link:{git}/keymanage.git[Git page]. In my experience, Linux authentication seems to be one of those problems with so many answers. It's hard to define even a range of methodologies that could |