Serializing/Deserializing Objeck object to/from JSON

[ghost]

The idea is to be able to send/receive Objeck objects between processes, over the network,...

[objeck]

Just data?

[ghost]

Just data?

I think so.

[objeck]

JSON elements would have to map to the existing Collection classes.

[ghost]

JSON elements would have to map to the existing Collection classes.

https://github.com/objeck/objeck-lang/issues/421 https://github.com/objeck/objeck-lang/issues/422

[ghost]

https://github.com/objeck/objeck-lang/issues/384 https://github.com/objeck/objeck-lang/issues/385 https://github.com/objeck/objeck-lang/issues/398

[objeck]

For clarity, the code must use an existing JSON parser and return associated collections.

Mapping:

• Class to Hash
• Array to Vector
• String to String
• True/False to BoolRef
• Number to FloatRef
• Null to Nil

All of the above types are supported in the JsonElement class, so the ask is really to map the JsonElement to the internal collections it uses.

[objeck]

I will defer this; it seems like a "nice to have," which I do have time to implement. Please, refer to the prior comment.

[objeck]

After looking into this more...

What about type-checking? Generate an exception if the wrong data type is cast?

The existing JsonElement class supports a type and a value. In dynamically typed languages, a value is a type/value. However, a value must map to a type in statically typed languages, which requires runtime type checking.

What is your proposed solution?

[ghost]

After looking into this more...

What about type-checking? Generate an exception if the wrong data type is cast?

The existing JsonElement class supports a type and a value. In dynamically typed languages, a value is a type/value. However, a value must map to a type in statically typed languages, which requires runtime type checking.

What is your proposed solution?

Does Objeck support Reflection? What does System.Introspection do?

Does Objeck support something equivalent?

https://www.geeksforgeeks.org/typeof-operator-keyword-in-c-sharp/

Btw, yes, this is the advantage of a language that supports exceptions. Everything is so much easier with exceptions.

https://code-maze.com/csharp-how-to-ensure-a-string-is-valid-json/

[ghost]

I know you will never add support for exceptions, so I will close this.

[objeck]

Objeck supports reflection via the System.Introspection class; however, that is not tied to supporting exceptions. In my professional experience, most developers either log or throw exceptions versus writing proper error-handling routines.

[objeck]

Please refer to the code below. I don't think parsing JSON into Collection classes is beneficial in Objeck since it is a strongly typed language. The cast statements are distracting.

With Collections

root := JsonParser->New(document)<Base>;
if(root <> Nil) {
    success := root->As(Map)->Find("success");
    if(success <> Nil) {
        success->As(String)->Equals("true")->PrintLine();
    };
};

With JsonElement

parser := JsonParser->New(document);
if(parser->Parse()) {
    root := parser->GetRoot();
    success := root->Get("success");
    if(success <> Nil) {
        success->GetString()->Equals("true")->PrintLine();
    };
};