Apply values to a procedure

[damien_mattei]

@countvajhula

Yeah, note that unlike bool, the ability to get cooperation from Qi by writing a Qi macro is a special feature provided by only a few macros in Racket (I can only think of Qi's flow (implemented using Syntax Spec which provides this macro-extensibility) and Racket's match which provides "match expanders").

I understand a bit,because probably it should be special Racket features that i do not know. Hope but not sure that all Qi feature could works for now in SRFI-105/curly infix because i do not know all in Qi.

@countvajhula

So doing this infix → prefix tranformation in two stages feels risky in general. One idea is to avoid the $nfx$ macro by doing the entire transformation from curly infix syntax to prefix syntax at the read stage, as that would allow you to do all the transformations before any macros (including bool) get control of the syntax.

I put it in my TODO list to have an option to in the parser to do fully the infix → prefix tranformation in one stage at the parser phase. This , of course , break compatibility with already implemented SRFI 105 curly infix implementations, such as the one of Guile for example, but anyway, my curly infix idea goes beyond what allow the basis of SRFI 105. So it is not a great problem, i should allow too some pragmas in the Scheme+ code that permit to swap dynamically from a strict SRFI 105 mode to an extended mode compatible with Qi macros and other language extensions. But this feature is not my first priority, and it it better to make it at the end when all the code of Scheme+ is done as i will have to duplicate or re-use a lot of routine in the first stage of parser. This is a long work.

@countvajhula

I don't have much experience with this (others here may have suggestions), but you may find readtables and Beautiful Racket useful, to explore this option and see if it's right for your use case.

Beautiful Racket was my starting point when porting SRFI 105 to Racket. The actual version allow the use of a #lang reader SRFI-105 even if you can parse the code externally with curly-infix2prefix4racket.rkt which allow to have the exact line of eventual errors which can not be done (or i do not know?) with a reader. Beautiful Racket explained me step by step how to wrote a reader. (but again it uses Racket features not portable)

@countvajhula

and the red dot spacecraft trajectory are non continous only because the original data are not good

In fact the discontinuous was just an effect of scaling.

I asked the researcher and we checked the data i had because there was two different type of trajectories:

• FlyBy (red plot) when BepiColombo made a fly-by of the Mercury planet (grey sphere) but is currently orbiting around Sun (hope i'm not saying silly thing...)
• Insertion (blue plot), will be at the end of the year, when BepiColombo will be "injected" in the orbit around Mercury.

note: space travelling ( as far as it has been explained to me) require escape from earth but keeping the speed of earth to travel and use gravitational effect with other planets and sun (to accelerate or slow) and a bit reactor of spacecraft.

plotted with Racket/Qi/Scheme+/SRFI-105 code:

@countvajhula

Seems very cool. I didn't realize Mercury had polar ice caps!

yes ,probably ice shadowed in crater

@countvajhula

Are you affiliated with BepiColombo?

We are in France at University of Nice

We find Racket amazing, the 3D axonometric plot is very usefull to quickly display and check data (even if a real 3D - not axonometric- view would be better)

To compare Qi and Scheme, here is 2 version of the data to plot generation:

Scheme/Racket/Scheme+:

;; read all lines
{input-lines := (read-lines src)}
{vl := (list->vector input-lines)}

{tdl := vl[5 :]} ; TABLEDATA lines, skip the header to go to table data lines

(define Lplot  (for/list ([tr tdl])
				    (list->vector (map string->number (rest (string-split tr))))))

and the Scheme/Qi/Scheme+ version:

{Lplot := (src) ~> read-lines ~> list->vector ~> _[5 :] ~> vector->list ~> (△ (string-split ~> rest ~> (△ string->number) ~> vector)) ~> ▽}

Hope it is readable for every one, not only for Qi expert , this code make me think of an alien language with strange characters △ ~> ▽ -< >< like in this sci-fi movie .

I think Qi is good but the documentation should provide greater examples, not just examples being a few tokens long. I would be interested to see what happens with long program, if it looks alien code or not . Perheaps also it is better in infix , perheaps it is interesting to correlate Qi with SRFI-105/curly infix notation, i do not know. Anyway as far as i know the 2 syntaxes, Qi and Scheme+/SRFI 105 are still envolving.