ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Gerben Wierda <gerben.wierda@rna.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: METAPOST vardef returning multiple and non-numeric types as a single answer?
Date: Mon, 16 Mar 2020 10:48:56 +0100	[thread overview]
Message-ID: <FFBC9F7E-A5E1-4257-9ACE-74D2A355A28E@rna.nl> (raw)
In-Reply-To: <23515AF0-D380-4D3D-BC62-078A179ED65F@elvenkind.com>


[-- Attachment #1.1: Type: text/plain, Size: 3363 bytes --]



> On 16 Mar 2020, at 10:23, Taco Hoekwater <taco@elvenkind.com> wrote:
> 
> 
> 
>> On 16 Mar 2020, at 10:10, Taco Hoekwater <taco@elvenkind.com> wrote:
>> 
>> 
>> 
>>> On 16 Mar 2020, at 09:53, Gerben Wierda <gerben.wierda@rna.nl> wrote:
>>> 
>>> Hola! So, the arguments passed to macros are by reference and not by value? I could have known of course, they are simple expansions, but I’d like to be sure. IfI assign to a variable inside a vardef macro and that variable is not ’save’d I’m changing the original?
>> 
>> Yes. (A simple test would have confirmed that)
> 
> Oops, sorry, no! I was wrong on that… it must be too early for me.

Coffee! Thanks anyway, Taco, your help is really appreciated.

> 
>  vardef Foo(text y) = 
>    scantokens(y&":=5”);
>  enddef;
>  Foo("x");
> 
> This would work, but that is weird.

Which is somewhat intuitive to parse as a human. I understand it as that after the last statement x has the value 5.

> This also works, and that is why
> I had the erroneous memory that it would work always:
> 
>  vardef Foo(expr a)(text y) = 
>    y[a] := 5;
>  enddef;
>  numeric foo[]; 
>  foo[1] = 6;
>  Foo(1,foo);

This was initially complete gobbledegook to me. But I now think that after the last statement foo[1] equals 5. Very weird/counterintuitive that y[a] := 5 works here without the use of scantokens. The first one is less weird to me because scantokens actually calls the METAPOST parser on a string as if read from a file.

> or you could use global variables, of course.
> 
> Main point: Metapost is not an easy language to grasp. If you want to
> really understand how it works, you should study the Metafont book by DEK.

I actually have that book and did a try small bit of METAFONT long, long ago to create a logo in it. Maybe that explains things better. (Unearthing the book for later use…)

> As you can clearly see, even experienced users are likely to make mistakes.

The main problem with all of this (ConTeXt, METAPOST, etc.) remains the learning curve and the lack of good and up-to-date educational materials. I.e. the METAPOST manual is terse, probably because it relies on people understanding the background that is in the METAFONT book.

And, if one is used to thinking in terms of functional programming, all that ‘expansion’ stuff (‘replacement’  programming?) is very counterintuitive for me. Lua then adds a functional model to the mix (or I think it does). Very hard to make progress. I learned Python in a day and produced a complex program in a matter of weeks. This is far less easy. And not being able so far to see what intermediate results lea to errors adds to the slow going.

I.e., the whole chapter on vardef in the METAFONT book is 

G

> 
> 
> Best wishes,
> Taco
> 
> 
> 
> 
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________


[-- Attachment #1.2.1: Type: text/html, Size: 6144 bytes --]

[-- Attachment #1.2.2: dangerous-bend.jpeg --]
[-- Type: image/jpeg, Size: 10230 bytes --]

[-- Attachment #1.2.3: dangerous-bend.jpeg --]
[-- Type: image/jpeg, Size: 10230 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      parent reply	other threads:[~2020-03-16  9:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 10:22 Gerben Wierda
2020-03-16  8:31 ` Taco Hoekwater
2020-03-16  8:53   ` Gerben Wierda
2020-03-16  9:10     ` Taco Hoekwater
2020-03-16  9:23       ` Taco Hoekwater
2020-03-16  9:38         ` Hans Hagen
2020-03-16  9:52           ` Gerben Wierda
2020-03-16  9:48         ` Gerben Wierda [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FFBC9F7E-A5E1-4257-9ACE-74D2A355A28E@rna.nl \
    --to=gerben.wierda@rna.nl \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).