implement random.pseudo in EO using QQ.sys.call or QQ.sys.win32

[yegor256]

Now, random.pseudo is using Java in order to get currentTimeMillis(). It's possible to get rid of Java, after we enable gettimeofday in eo-sys: objectionary/eo-sys#5

[yegor256]

@mximp please, help or delegate

[mximp]

@potatmen please have a look

[potatmen]

@mximp as I see eo.sys module on the stage of PR. I am interested in implementing pseudo.random using this module!
Btw, I proved that random.pseudo has a uniform distribution with the old implementation, I believe I will need to do it once again after implementation it in EO right?

[mximp]

@potatmen The task is exactly about implementation of Pseudo.random using eo.sys. In particularly to replace using atom Java current time with the function from eo.sys

I believe I will need to do it once again after implementation it in EO right

Yes, would be good to validate.

[potatmen]

@mximp Ok, but still I'm waiting for the merge of your PR to start using this module.

[potatmen]

@mximp I have a question about how to use gettimeofday in EO. If I try to use it like this QQ.sys.system.gettimeofday I get an error The attribute Δ of org.eolang.PhLocated has org.eolang.PhPackage instead of org.eolang.Data. If like this QQ.sys.call "gettimeofday" then I get this error EOorg.EOeolang.EOstringν17="Can't #copy() package object 'org.eolang.sys.call'"SF
Code

[mximp]

@potatmen The function is expected to be called like the following:

+alias org.eolang.sys.call

[] > get-time-of-day-test
  if. > @
    QQ.sys.uname.is-windows
    nop
    assert-that
      QQ.sys.call
        "gettimeofday"
      $.greater-than 0

[potatmen]

@mximp Trying to use it like you proposed code and get The alias "org.eolang.sys.call" is not used (unused-aliases:26)

[mximp]

@potatmen It's strange.. Can you try to use just call?

[mximp]

Also can you try to examine target/eo folder for interim stages. In which .xmir the error appears?

[potatmen]

@mximp Tried to use just call, got this Failed while trying to save to ./target/04-pull/org/eolang/call.eo: https://raw.githubusercontent.com/objectionary/home/85efb6667117cb1f2f003016da99800dec26c5b7/objects/org/eolang/call.eo

[potatmen]

@mximp The directory you recommended to check has only .csv files and no .xmir files

[potatmen]

@mximp Btw, according to this comment we can't use sys.call because it wasn't added to the Objectionary

[potatmen]

@mximp I believe the current version of random written in Java is here. If yes, may I just rewrite this version in EO and show to you?

[mximp]

@mximp The directory you recommended to check has only .csv files and no .xmir files

@potatmen normally target/eo should have the following structure:

 \01-parse\
 \02-steps\
 \03-optimize\
 \04-pull\
 \05-pre\
 \06-resolve\
 \06-transpile\
 foreign.csv
 placed.csv

@mximp I believe the current version of random written in Java is here. If yes, may I just rewrite this version in EO and show to you?

That's is the point of the task - to re-write it in EO. Let's review it as par of PR.

[potatmen]

@mximp objectionary/eo-sys@master...potatmen:eo-sys:master in this file I added random number generator, please check it out. I placed it to the eo-sys repo because it's successfully running inside this repo

[potatmen]

@mximp one thing I have noticed about target/eo is that there are no sys subfolder, I mean that there are subfolders of math collections and no sys.

Also, please take a look at this issue objectionary/eo-sys#9, it's said that sys.call is not added to objectionary

[mximp]

@mximp objectionary/[email protected]:eo-sys:master in this file I added random number generator, please check it out. I placed it to the eo-sys repo because it's successfully running inside this repo

@potatmen As far as I can tell this will look totally different when implemented in correct repo (eo-math). Let's wait for eo-sys is released properly and then solve this task.

[levBagryansky]

@Graur I guess I am able to solve the task

[Graur]

@mximp Is this issue still relevant? If so we can assign @levBagryansky

[mximp]

@Graur @levBagryansky It is relevant. Assigned.

[0pdd]

@yegor256 the puzzle #98 is still not solved.