Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default initial keyboard in runCJAlgorithm? #8

Open
FrankDMartinez opened this issue Jul 30, 2012 · 2 comments
Open

Default initial keyboard in runCJAlgorithm? #8

FrankDMartinez opened this issue Jul 30, 2012 · 2 comments

Comments

@FrankDMartinez
Copy link

Hi,
In runCJAlgorithm(), the k variable is uninitialized before being copied to prev the first time thru the for-loop. To prevent k from being filled with garbage data, should it be initialized to, say, nilKeyboard before the first loop?

@FrankDMartinez
Copy link
Author

Whatever the answer to the above question is, would that answer also apply to bestk in the same function?

@michaeldickens
Copy link
Owner

nilKeyboard would be a sensible default value. It doesn't matter much,
because prevk is not used on the first time through the loop.

On 7/30/12 11:44 AM, FrankDMartinez wrote:

Hi,
In runCJAlgorithm(), the k variable is uninitialized before being copied to prev the first time thru the for-loop. To prevent k from being filled with garbage data, should it be initialized to, say, nilKeyboard before the first loop?


Reply to this email directly or view it on GitHub:
#8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants