Malaclypse
Active Member
- Oct 18, 2001
- 5,408
- 112
- 63
i have never worked with perl, so anything i'll say now could be total bullshit.
anyway,
1. it's usual that DNA sequences won't come out in neat multiples of three, and there's actually no reason to test for that in the beginning. you'd have to truncate any trailing 1 or two bits, however.
2. you can probably reuse the nucleotide checking block for the second sequence without having to copy and paste the code. don't ask me how though, i don't know shit about perl.
3. same goes for basically all larger building blocks of the program - instead of just copying the source for 1st and 2nd sequence, you'd rather out-source them into procedures (if there's any such thing in perl) and reuse them, only changing the input string (the sequence)
a thought on usability:
give the option to read from a file, so you won't bother people to type all these letters. also, you could get rid of the double input to make sure everything was typed down correctly.
anyway,
1. it's usual that DNA sequences won't come out in neat multiples of three, and there's actually no reason to test for that in the beginning. you'd have to truncate any trailing 1 or two bits, however.
2. you can probably reuse the nucleotide checking block for the second sequence without having to copy and paste the code. don't ask me how though, i don't know shit about perl.
3. same goes for basically all larger building blocks of the program - instead of just copying the source for 1st and 2nd sequence, you'd rather out-source them into procedures (if there's any such thing in perl) and reuse them, only changing the input string (the sequence)
a thought on usability:
give the option to read from a file, so you won't bother people to type all these letters. also, you could get rid of the double input to make sure everything was typed down correctly.