nextprime() odd behavior?

[EdH]

Doesn't this seem a tiny bit odd?

Script (calling YAFU wip r395):

#!/bin/bash

np=2
while [ $np -lt 30 ]
  do
    printf "nextprime for $np is "
    np=$(./yafu "nextprime($np)" -silent)
    echo "$np"
  done

Result:

$ bash primesgen.sh
nextprime for 2 is 3
nextprime for 3 is 13
nextprime for 13 is 17
nextprime for 17 is 19
nextprime for 19 is 23
nextprime for 23 is 29
nextprime for 29 is 31

Not that anyone would generate primes in this fashion.

[bsquared]

Well, that was silly. Thanks as always for testing! Fixed in r396.

P.s., *cough* "primes(0,1e6,0)" -pscreen *cough*

[EdH]

Originally Posted by bsquared

Well, that was silly. Thanks as always for testing! Fixed in r396.

P.s., *cough* "primes(0,1e6,0)" -pscreen *cough*

Thanks! I remembered nextprime(), but not primes(). And, there's no way I would have remembered it needed 3 values. I'd have had to look it up.

[bsquared]

Originally Posted by EdH

Thanks! I remembered nextprime(), but not primes(). And, there's no way I would have remembered it needed 3 values. I'd have had to look it up.

I had to look it up too . primes(0,1000000) is the same as primes(0,1000000,1) which just counts primes in the range. primes(0,1000000,0) actually computes them and -pscreen dumps them to screen. -pfile puts them in primes.dat.

[EdH]

Originally Posted by bsquared

I had to look it up too . primes(0,1000000) is the same as primes(0,1000000,1) which just counts primes in the range. primes(0,1000000,0) actually computes them and -pscreen dumps them to screen. -pfile puts them in primes.dat.

I need to review the docs more often. I find lots of neat things in there!

Thanks for all!