Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jul 01 2018 17:34
    @greggirwin banned @BIjeuca_twitter
  • Dec 03 2017 05:53
    @PeterWAWood banned @matrixbot
  • Sep 28 2016 12:20
    @PeterWAWood banned @TimeSeriesLord
OneITI
@OneITI
I consider this to be a bug regarding the image process or binary file output.
Moreover, my operating system is macOS High Sierra(10.13.6), and I am utilizing Red 0.6.3 with the Visual Studio Code(1.29.1) plugin.
Vladimir Vasilyev
@9214
Perhaps you should update to the latest version first, before pointing out bugs.
And there's certainly no need in double posting your questions in different rooms.
Gregg Irwin
@greggirwin
Welcome @OneITI!
Palaing
@Palaing
wrong syntax, but the error message is weird too:
>> 1 < 2 or 2 > 3
*** Script Error: < does not allow integer! for its value2 argument
*** Where: <
*** Stack:
Toomas Vooglaid
@toomasv
Should be Error: or does not allow...
Somehow op in message is not updated?
Boleslav Březovský
@rebolek
but or allows integer!
Toomas Vooglaid
@toomasv
>> true or 3
*** Script Error: or does not allow integer! for its value2 argument
Boleslav Březovský
@rebolek
Yeah, but
>> 2 or 3
== 3
The error message probably should say something like incompatible values
Toomas Vooglaid
@toomasv
Yes
Can you explain treatment of integers by or and and?
Boleslav Březovský
@rebolek
@toomasv like in C.
1 or 2 -> 3
in binary: 01 or 10 -> 11
Toomas Vooglaid
@toomasv
Ok, thanks!
0x11
@codenoid
hi
how it's goig
going
Boleslav Březovský
@rebolek
Hi @codenoid
Vladimir Vasilyev
@9214
Infix logic operators dispatch on leftmost (rightmost?) operand, so IMO this is an expected error message.
Boleslav Březovský
@rebolek

If I compare R2 and Red:

>> 1 < 2 or 2 > 3
*** Script Error: < does not allow integer! for its value2 argument
*** Where: <
*** Stack:

vs

>> 1 < 2 or 2 > 3
** Script Error: Expected one of: logic! - not: integer!
** Near: 1 < 2 or 2

Rebol message seems to make more sense

Vladimir Vasilyev
@9214
Agreed.
Luis Vale Mendes
@lpvm
@9214 Hi, regarding the solution you've presented yesterday, there's something I don't understand.
What I've seen and done is ... into [rules]. You've built something like ... into [one rule] [another rule] third rule and the third rule is not in a block.
Another thing is the first block of rules [keep pick to end]. I read something about pick in parse context, but could never arrive at such formulation by myself based solely on that.
Would you mind explaining all this?
Vladimir Vasilyev
@9214
Can you elaborate on "not a block" part? As for pick, see here. It basically collects matched values one-by-one instead of collecting matched group as a "unity".
Luis Vale Mendes
@lpvm
It's getting more clear, now, but yet not fully bright...
You've build into [keep pick to end]. To play with this, I tried into [keep pick to ":" to end] if the minute part of the time was not important. But returns [].
Shouldn't it return everything up to the hour part?
Vladimir Vasilyev
@9214
>> parse ["123:456"][collect [into [keep pick to ":" to end]]]
== [#"1" #"2" #"3"]
>> parse ["123:456"][collect [into [keep to ":" to end]]]
== ["123"]
Luis Vale Mendes
@lpvm
Taking your previous example:
input: [
    "[1518-02-24 23:58] Guard #853 begins shift"
    "[1518-02-25 00:20] falls asleep"
    "[1518-02-25 00:43] wakes up"
]

forall input [
    probe parse load input/1 [
        collect [
            into [keep pick to ":"  to end ]                    ;  inserting `to ":"`
            [thru set ID keep issue! | keep (ID)]
            set action skip keep (index? find actions action)

        ]
    ]
]
==  []
Vladimir Vasilyev
@9214
How can it work if you just loaded the string?
Luis Vale Mendes
@lpvm
Fine, skipped that one. Thank you for your time, patience and overall help @9214
Vladimir Vasilyev
@9214
@lpvm no problem, have fun. :wink:
Luis Vale Mendes
@lpvm
Spot on, that's really my thrive at this phase on my life!
Toomas Vooglaid
@toomasv
What structure did you choose for representing/gathering Day4 data?
Luis Vale Mendes
@lpvm
Hi @toomasv I haven't yet studied your code proposal and haven't choose any yet.
LP Olivier
@olivier_lp_twitter
Is a multitasking or multithreading implementation planned ?
Vladimir Vasilyev
@9214
@olivier_lp_twitter consult the roadmap.
LP Olivier
@olivier_lp_twitter
@9214 thanx, i got my answer :-)
rpherman
@rpherman
@greggirwin I put the DLL in the same folder as the executable. I think it is a 32 bit / 64 bit issue. I am running 64 bit Red, and I saw a snippet about redCV being 32 bit.
Vladimir Vasilyev
@9214
@rpherman there's no 64-bit Red.
Senenmut
@Senenmut
Hi there. winter + time = programmingtime ### May i ask for news about the compiling of a android .apk executable program file in red ? Are there any news ? Pleased to share them here. ## signed by The barbarian programmer ##
Vladimir Vasilyev
@9214

@Mennohexo read the latest blog post, esp. P.6:

Android will come after Full I/O

Senenmut
@Senenmut
oh that's great news. thanks. The only tool right now is RFO Basic but they have a little slowdown in development , however it still works. Noone wants to load hundreds of MB and install a shop of hocus pokus like the official java android solution is. ha ## To professional programming frames slow down production ideas. Is my view. Few other think too. ##BP
Senenmut
@Senenmut
i mean the dangerous programmer named : iArnold
ok. its a programmers joke. really. Thanks and see you again here. Regards BP
rpherman
@rpherman
@9214 Thanks about pointing out there is no 64-bit Red! There are no beginner RedCV instructions on what you need to do to set it up. I am familiar with OpenCV in Python, but I am lost in knowing what I need to compile and how and where to put things in the folder structure in order for this to work. Thanks again!
Senenmut
@Senenmut
You can develop modern android apps with win XP. #Its possible. Anyway , a little bit like barbarian.
Luis
@luis-rj
Vladimir Vasilyev
@9214
@rpherman, perhaps @ldci can chime in and help with your issue. Instructions are pretty straightforward, it's a missing DLL that causes the trouble.