Pages: 1
  Print  
Author Topic: Some functions not implemented yet in ENIGMA  (Read 900 times)
Offline (Unknown gender) Darkstar2
Posted on: March 03, 2014, 08:34:48 PM
Member
Joined: Jan 2014
Posts: 1244

View Profile Email
I have a question regarding certain functions that are not yet implemented in ENIGMA.  How accurate and up to date is the page listing missing functions ? I mean some are obvious like in app, windows8 and html5 specific, but is the page up to date ?

What about these:

    sha1_string_utf8
    sha1_string_unicode
    sha1_file
    md5_string_utf8
    md5_string_unicode
    md5_file
    json_encode
    json_decode
    buffer_base64_decode
    buffer_base64_decode_ext
    buffer_base64_encode
    buffer_md5
    buffer_sha1

Are all of these not compatible in ENIGMA ?

If not, is it possible to have the buffer md5/sha1 and file encode/decode md5/sha1 as well as string encode/decode md5/sha1 functions in ENIGMA?
Logged
Offline (Male) Goombert
Reply #1 Posted on: March 03, 2014, 09:53:28 PM

Developer
Location: Cappuccino, CA
Joined: Jan 2013
Posts: 3110

View Profile
Yes but those would be an extension, Base64 is implemented for strings because it was super simple for me to write, but I did not add it for buffers because buffers need redone I wrote them very porrly (I think). But the sha1 and md5 encryption and JSON require libraries, there is simply too much for us to write that ourselves, so we want those functions implemented through extensions since they will most likely utilize a library of sorts. FYI, I think the current JSON extension is broke, the code looks like it doesn't even do what it's supposed to do.
Logged
I think it was Leonardo da Vinci who once said something along the lines of "If you build the robots, they will make games." or something to that effect.

Pages: 1
  Print