[OT] We're hiring
Mike Bonner
bonnmike at gmail.com
Sun Sep 16 11:42:12 EDT 2012
Interestingly, the base64encode function of livecode does add the padding
to the correct length.
put the base64encode of "support at economy-x-talk.com"
c3VwcG9ydEBlY29ub215LXgtdGFsay5jb20=
Apparently the decode function pads the data to the correct length before
decoding so it works with or without the trailing =.
On Sun, Sep 16, 2012 at 9:42 AM, -=>JB<=- <sundown at pacifier.com> wrote:
> The site below returns it properly with .com at the end
> of the line.
>
> http://www.base64decode.org/
>
> -=>JB<=-
>
>
> On Sep 16, 2012, at 8:07 AM, Colin Holgate wrote:
>
> > You are right about that, but there is very little in your job
> application that is to do with LiveCode, and many applicants will use more
> regular decoding tools. It could be a bug, or hack, in LiveCOde that allows
> it to work ok.
> >
> > Try this page with your existing code:
> >
> > http://opinionatedgeek.com/dotnet/tools/base64decode/
> >
> > or try TextMate. That page shows an error, TextMate converts it ok
> without that last two characters.
> >
> >
> > On Sep 16, 2012, at 10:03 AM, Mark Schonewille <
> m.schonewille at economy-x-talk.com> wrote:
> >
> >> Perhaps RunRev changed something in the decoding algorithm in the last
> version of LiveCode? In all the version of Revolution and LiveCode that I
> have, it doesn't matter whether you add = or == or even === or nothing.
> >
> > _______________________________________________
> > use-livecode mailing list
> > use-livecode at lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
> >
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
More information about the use-livecode
mailing list