Re: APL & Programming Concepts

On May 8, 4:13=A0pm, Mb <meb...@[EMAIL PROTECTED]
> wrote:
> > I understand that you think J more or less meets your criteria
> > (basically APL2 does meet your criteria too as far as I can gather)
>
> Right.
>
> > Even so you still do not want to use J (nor APL2 for that matter) ?
>
> Yes and no, here. I'd like to, but I'm still at the beginning of a long
> learning curve, and I don't know if it's worth. For sure, it does not if
> I have to invest a bunch of money in the dark .... not in a world in
> which I can choose from a myriad of other programming languages,
> standardized (more or less) and freely distributed and supported.
>

You do not have to invest any money.
APL2 has a free version to start on and J is free.

If/when you come to a point where you are stuck you can send in
questions to forums and there are a lot of eager hands to assists for
free.

One thing you may be surprised about is how your example you may have
been experimenting with will shrink in size when the experts start to
work on them.

It should be pretty obvious that a program with very few lines will
have less places to hide bugs.

I always found it funny (actually more irritating) in the past when
product assurance looking over APL code with measurements sticks made
for someother language that code with so and so many lines was
"supposed" to have so and so many bugs.
When they did not find any bugs they assumed they were still there
just had not been discovered yet.
Those bug have still not been found after number of years and in the
hands of lots of users.