Hi Brandon,

On 11.07.2016 19:19, Brandon Cherry wrote:
> I think I still have commit rights, but it has been awhile. I can update the 
> copyright and drop
> the files where ever you might want. If I lost commit rights, I can also send 
> it to whomever you
> deem necessary. You can take this as my permission.
Thanks!

You should be able to test whether you have still commit rights by 
(re-)creating a sandbox entry and
place the program there with the license, which then could be picked up there 
(also via the
Sourceforge interface).

> I guess it should be noted that there are a couple of things I did not know 
> how best to address.
>
> - No Unicode support
>
> ooRexx did not support Unicode, so I figured that this was not a big deal. I 
> will admit I have not
> been keeping up with the status of the project lately, so I do not know if 
> this has already been
> addressed.
No, not yet.

For the time being I have been using BSF4ooRexx as this allows one to use Java 
and the Java-Unicode
support, including .

>
> - .True and .False are not really types in ooRexx
>
> Boolean values in JSON do not translate very well to ooRexx. I remember if 
> you run a boolean value
> through both sides of this code, it would turn the boolean into an integer. I 
> even posted a
> question on the list about this and Rick said that there was a way in 3.2 to 
> tell the difference
> between .True and 1. I was running on 3.1, so I could not use his solution. 
> If there is a better
> way in newer releases, it might be nice to update this part.
Hmm, in ooRexx .true is always "1" (= Rexx) and .false "0" (= Rexx). As a 
dynamically typed language
[oo]Rexx has no explicit Boolean type but mandates logical (Boolean) values to 
be "0" or "1". The
datatype()-built-in-function (BIF) has the argument "Logical" for testing 
whether a value is of type
"logical" or not.

As long as JSON "true" and "false" values get translated to "1" and "0" 
everything is fine.

Going the other route, from ooRexx to JSON, it would be interesting to learn, 
whether it might make
a difference whether ooRexx passes "0" and "1" on as numbers. If makes a 
difference, then a solution
would be necessary for that particular problem (which could be as simple as 
expecting from the
ooRexx programmers to supply "true" and "false" as explicit values in the case 
that a JSON structure
must supply these strings as Boolean values).


> It has been awhile since I wrote this, but I do remember these two issues.
>
> One more issue that might be a problem is that this routine is recursive. The 
> call stack might be
> a problem if you get too many children, but I remember testing this and for 
> what I was doing it
> was fine. One might want to rewrite it not to use recursion to prevent fix 
> this. I even thought
> about doing this on the side. It did not seem like I got much feed back, so I 
> decided it was not
> worth spending a whole lot of time on something only me and three other guys 
> in the world used.
Hmm, usually recursive structures are never really very deep when exchanging 
data, so I would doubt,
that this might turn into a practical problem. (With todays hardware I 
personally prefer legibility
of code over maximum efficiency for bread and butter problems.)

---rony



>
> ----------------------------------------------------------------------------------------------------
> *From: *"Rony G. Flatscher" <[email protected]>
> *To: *[email protected]
> *Sent: *Monday, July 11, 2016 6:32:19 AM
> *Subject: *Re: [Oorexx-devel] About adding JSON-support for ooRexx 5.0
>
> Hi Brandon,
>
> On 08.07.2016 17:14, Brandon Cherry wrote:
>
>     I am actually surprised that no one else came up with something better. I 
> just wanted
>     something quick for the web work I was doing at the time.
>
> It seems you have hit the nail right on the head and it seems that it has 
> been a good solution
> already! Do you happen to know whether there are new encodings that have been 
> added to JSON since
> you wrote that class?
>
>
>     I have no problem with adding it to the project, but keep in mind I 
> originally wrote it to
>     work against ooRexx 3.1 (that was what was on our oldest web server at 
> the time).
>
> So does this mean, that the ooRexx needed CPL license is granted, such that 
> your class could be
> added to the ooRexx project?
>
> ---rony
>
>
>     
> ----------------------------------------------------------------------------------------------------
>     *From: *"Erich Steinböck" <[email protected]>
>     *To: *"Open Object Rexx Developer Mailing List" 
> <[email protected]>
>     *Sent: *Friday, July 8, 2016 10:22:03 AM
>     *Subject: *Re: [Oorexx-devel] About adding JSON-support for ooRexx 5.0
>
>     I have opened enhancement request #625 Add json class to ooRexx 
> Distribution
>     <https://sourceforge.net/p/oorexx/feature-requests/625/> some time ago.
>
>     I assume that a first step would be to get the original author's written 
> confirmation to grant
>     json.cls to the ooRexx project to be released under the CPL we're using.
>

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to