Re: Oops

new topic     » goto parent     » topic index » view thread      » older message » newer message

I can't actually try "executing" your wif.e file, since I don't
have fileman.e.

But I do notice one thing right away... in your Encode() function,
you declare the variable Encoded to be of type WIF. But you then
immediately refer to:

   Encoded[WIF_PalRef]

before you've assigned any value to the variable! You're doing the
same thing in your UnEncode() function too. Declaring a variable
doesn't actually fill it in Euphoria... you still must put in some
valid data (in this case, an sequence that is a valid WIF type)
before you can use it. I sometimes declare a DEFAULT_type constant
with my built-in types; if a type requires a sequence of length 5,
I'll have:

   constant DEFAULT_MY_TYPE = {0,0,0,0,0}

and then assign the constant to variables of that type before
using them.

There may be more logic errors, but that was the most obvious one I
saw from just glancing at the code. I take it you're still using the
public domain version of Euphoria, or does the code crash before it
gets to those functions?


Rod Jackson

----------
From:   theskaman at mindspring.com[SMTP:theskaman at mindspring.com]
Sent:   Thursday, April 08, 1999 7:00 AM
To:     EUPHORIA at LISTSERV.MUOHIO.EDU
Subject:        Re: Oops

<<File: ATT00002.html>><<File: WIF.E>><<File: wiftest.ex>>
Ok, now can anyone tell me why this program doesn't work.

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu