Pascal, you are right. I would say that it is "generally accepted" that in
J, power is the way to do iteration. I would bet very few people use $:
much given that (^:) and (/), (\) etc. can easily model most problems. But
for some people using recursion is more (or equally) instinctive. So, this
wa
also if you really wanted to call it dyadically,
fib =: (<:X, {:Y , +/Y)Guard (0 < {.) Cleanup {: (@:,)
or
fib =: (<:X, {:Y , +/Y) Guard(0 < {.) Cleanup{: @:,
10 fib 0 1x
89
- Original Message -
From: 'Pascal Jasmin' via Programming
To: "programm...@jsoftware.com"
Cc:
Sent: W
In case it is not obvious - if you really wanted a layout with a root
project and subprojects in its subdirectories, just make the Folder one
level higher.
On Wed, Aug 27, 2014 at 7:54 AM, chris burke wrote:
> > Does it make sense to enable pointing directly at a project root with a
> user fold
> Does it make sense to enable pointing directly at a project root with a
user folder too? i.e. search root as well as sub-folders for .jproj files.
Allowing a project in the Folder root complicates things in that it needs
special treatment (e.g. in the Open Project dialog) compared to all other
Thanks both.
There's been quite a lot of subsequent correspondence about the relative
performance
of u/\ and u/\..
What I was actually griping about was the relatively poor performance of
M&|@:u (distributed across an array in some manner) compared to plain u,
as here with add32 cf +
Hi Chris & Ric,
Thanks for explaining about the shallow search. I went back to using upper
case too. So, I went one level up in the path, and now *jqt *is working
now as you'd expect it to.
e.g. from *C:/dev/projectA/* to *c:/dev/*
Does it make sense to enable pointing directly at a project ro
