Some interesting facts about characters. ASCII characters are just numbers. You can (usually) directly compare characters the same way you can numbers. For example:
('a' < 'c') && ('c' < 'z')
in Python it's just: mylist=re.findall(r'([A-Za-z]+)', string)
>>> import re
>>> print (re.findall(r'([A-Za-z]+)',"moo cows moo wowowowo344rd4fde"))
['moo', 'cows', 'moo', 'wowowowo', 'rd', 'fde']
TIS-100 is amusing but it's nothing like any real programming language even if the syntax is sort of assembler-like. You'll be shooting yourself in the foot if you actually try learning from it.
Yeah, its Javascript. Also, I tried looking it up again and I saw string.replace() on stack overflow. This post as well as some of the other replies I got were pretty helpful, thank you.
function reverse(str){
let revStr = "";
//reverse string
for(let i = str.length -1; i >= 0; i--){
if(revStr == ""){
revStr = str[i];
} else {
revStr += str[i]
}
}
return revStr
}
The crates in question are not official rust crates and only have around 3000 total downloads ever on crates.io. This is a cherry-picked example of a troon doing weird stuff as they usually do and is not a representative example of crates that are actually used by real people. Cargo already has official benchmarking support built-in, this "diol" benchmarking library is just some troon doing things that already exist for no reason in a worse way than what is officially supported.
Yet Rust is the only language that frequently has people coding in it one-handed.
#include <stdio.h>
#include <stdlib.h>
#include <ctype.h>
#include <string.h>
static int pullNums(char *line){
//purpose is to filter all the numbers in the line
int f, b;
char res[3] = {0};
f=0;
b = strlen(line) - 1;
while(!isdigit(line[f]) && line[f] != '\0')
f++;
res[0] = line[f];
while(!isdigit(line[b]) && b > 0)
b--;
res[1] = line[b];
if(!isdigit(res[0]) || !isdigit(res[1]))
res[0]=res[1]='0';
res[2] = '\0';
printf("Calibration number: %s\n", res);
return atoi(res);
}
static void parseFile(FILE *f){
//read lines held here
char reading[100][100];
int r, c, parseSum, l;
r=c=parseSum=0;
while((l = fgetc(f)) != EOF){
reading[r][c++] = l;
if((l == '\n')||(l == EOF)){
if(l == '\n'){
c-=1;
}
reading[r][c] = '\0';
parseSum += pullNums(reading[r++]);
//printf("%s\n", reading[r]);
c=0;
}//end if
}//end while loop
parseSum += pullNums(reading[r]); //<-- extra pullnums because the while
//loop doesn't go through all of r
printf("Final calibration is: %d\n", parseSum);
}
int main(void) {
//printf("Hello, World!\n");
FILE *ipfi;
ipfi = fopen("InFile.txt", "r");
if(ipfi == NULL){
printf("No such file found. Try again.\n");
return 1;
}
parseFile(ipfi);
fclose(ipfi);
return 0;
}
The while loop in parseFile stops when you reach EOF, even though the code inside of it expects to be executed when the char is EOF. You either need a do while or do another break condition for the loop.
If I was doing it, I'd first convert the whole string to lowercase, then I'd use
string.replace(/[^a-z]/g, '') to remove all the characters that are supposed to be ignored. Then I'd use a simple loop starting at both ends of the string, comparing the characters from both ends, and stepping in toward the middle.
I know from a later post that you solved your problem an other way, but I still wanted to add here that writing a palindrome checker in Regex is impossible, or if you allow some engines with heavy modifications at least super tedious.
It's only natural. Switching from "I'm a coding god" to "I have no idea" is very common in programming.
const txtInput = document.querySelector('#text-input');
const resultTxt = document.getElementById('rslt-txt');
resultTxt.innerText = "Type anything you want into the box above and check if it is a palindrome!";
const checkBtn = document.querySelector('#check-btn');
checkBtn.onclick = check;
function check(value){
value = txtInput.value;
value = value.replace(/[^a-zA-Z0-9]/g,"")
value = value.toLowerCase();
console.log(value)
if(value == ""){
return alert('Please input a value');
} else{
if(value == reverse(value)){
value = txtInput.value;
resultTxt.innerText = `${value} is a palindrome.`
} else {
value = txtInput.value
resultTxt.innerText = `${value} is not a palindrome.`
}
}
}
function reverse(str){
let revStr = "";
//reverse string
for(let i = str.length -1; i >= 0; i--){
if(revStr == ""){
revStr = str[i];
} else {
revStr += str[i];
}
}
return revStr;
}I initially read it the same way, but he was just trying to use regex to do some pre-parsing.
/^([a-z]|)([a-z]|)([a-z]|)([a-z]|)\4?\3\2\1$/i (if you want it to ignore non-alpha, stick a bunch of [^a-z]* in it)
I agree with this point at face value, but my point was more that the crates in question are so archetypally Rust Community™ to the point of being identical to parody; it's all very on the nose. This is the community they foster, actively forcing the "real people" you mention, like ourselves, who aren't depraved coomers into silence. As such, it would be significantly less funny or noteworthy if it were done in literally any other language.
The language itself should not be dismissed as a useful tool on this basis.
But the Rust foundation has a lot of power over the language and has made some concerning moves. I have reasons to never write anything in Rust other than the community but the community does not help and it is a real problem.
You can completely sidestep cargo and use rustc if you want, use a makefile, whatever. There's nothing stopping you and it is just as easy as with your C compiler of choice.
You were going to import a CSPRNG library for cryptographic stuff anyways also /dev/urandom and /dev/random
Debian tried this and it was a failure, the reason you don't want dynamically linked system packages is because you want to be able to take advantage of the rich rust type system which includes using types from other libraries and passing trait impls across the boundary between libraries and programs. When you dynamic link, you have to conform to the lowest common denominator that the loader library provided by your OS supports, which is in every case the C ABI. You can't propagate rust's rich type system across the C ABI boundary between programs and libraries. This is also the reason for static linking. It is a reasonable tradeoff considering hard drive space is incredibly cheap and mmap is basically OS-level magic as far as the average systems programmer is concerned.
Static linking also solves the problem of relying on a dynamic linker when shipping your binaries, if you static link, all the stuff you need is already there. If you dynamic link, you have to pray that whoever consumes your binary has all the things your binary asks the loader for, and also pray they have an ABI-compatible version installed. This isn't an issue when you statically link your libraries. This again, is totally worth the tradeoff and streamlines deployment. Also, the option for dynamic linking is there for rust if you really really want it.
Have you seen C++ template syntax? It's about as bad as rust's explicit lifetime syntax. Complaints about syntax, especially ones that concern aesthetics are purely a skill issue.
The behaviour of the rust foundation is a valid reason to not use rust. I don't particularly care about the few "controversies", they all amount to nothing regarding the technical aspects of the language and ecosystem.
The great thing about """online communities""" is that you can completely ignore and disregard them. They don't exist outside of their horrific discord server(s), probably some fediverse instances somewhere and reddit. They don't exist in the real world outside of some annual conferences that you can just not attend.
How is this any different from just transferring the text file to the client? Are you storing this data locally for some reason instead of downloading it? If you are storing it, why are you not just using a DBMS or document storage system to manage this data? I understand wanting to do C stuff at a low level, but maybe stay in your lane as a beginner and use working storage solutions like mongodb and SQLlite or H2.
... So, compression?