Landon Curt Noll

> Stack values can be returned as text or in Calc-native form. So when a "history" item, even if retrieved from a stored history file, is reused, it retains its...

Hello @pmetzger, Interesting idea for calc v3. Ignoring the "__" parser issues, and as you say, "but let's go with it for the moment for imaginative purposes": How would you...

> I'd have to re-read the papers about F# units of measure work first I think. Before planning code, one needs to have a clear idea of what it will...

Hello @cburgmer, Our pull request #16 also addresses your issue, or you may wish to use the [lcn2 JSONPath.sh fork](https://github.com/lcn2/JSONPath.sh).

Hello @pmetzger, You raise some valid concerns concerning this pull request as it initially was presented. Let us see how @vike2000 responds to this change request review and see if...

Hello @vike2000, We might wish to consider adding the general concepts relating to "pipes, forks, and I/O with other processes, etc." to calc version 3. Maybe not in the initial...

> Hello :) > > > > I said I was unsure whether to add these "development files", so I understand your concerns and have now removed those files. Are...

BTW @vike2000, In regards to the [defer to calc v3](https://github.com/lcn2/calc/pull/153#issuecomment-2223682290) comment we made above. That does not represent a final decision, but rather our "thinking out load". We will still...

Hello @vike2000, > As with everything else, naming and/or prefixing is open for discussion, especially in pfe, pread, and pwrite, being higher level utilities implemented first in calc/.cal and then...

> I'm finding reading large chunks of this very difficult to read because of unusual choices in code formatting. It would be best if these were cleaned up and made...