3(({."1 ~>:)~ (* [:^/~ i.@#@,)) 0 0 1 1 1

R.E. Boss


-----Original Message-----
From: Programming <[email protected]> On Behalf Of 'Bo 
Jacoby' via Programming
Sent: vrijdag 21 augustus 2020 12:49
To: [email protected]
Subject: Re: [Jprogramming] Code smells in J

 How to de-smell this:
 3([* i.@#@,@[ ^/ i.@>:@])~ 0 0 1 1 1

?
I tried but in vain.

Thank you!
Bo    Den fredag den 21. august 2020 08.18.16 CEST skrev Bo Jacoby 
<[email protected]>:  
 
  How to remove the smell (the "[" and the "]") from
   3(i.@>:@[ ^/~ ])2 3 4
?
Thanks!  Bo.






    Den fredag den 21. august 2020 07.06.50 CEST skrev Raul Miller 
<[email protected]>:  
 
 The code smell which bothers me worst, in J, is the "not getting started" 
smell.

When I am afraid of writing a rough draft because it would be ugly, I don't get 
anywhere. And, once I have a working draft, I can use that to test variations 
which would be more concise, more understandable, which get past machine 
bottlenecks, which have clearer interfaces and/or more straightforward 
documentation.

Anyways, not putting my heart into it is a smell.

Thanks,

--
Raul

On Thu, Aug 20, 2020 at 6:24 AM ethiejiesa via Programming 
<[email protected]> wrote:
>
> What are some classes of code smell in J?
>
> For clarity, "code smell" means any characteristic of source code that 
> indicates a potentially deeper problem. These are anti-patterns that 
> occur at the source code level.
>
> The canonical example is probably duplicated code, which indicates a 
> potential for abstraction or merging of the repeated code. In C-like 
> languages, deeply nested if statements are typically considered 
> smelly, suggesting a potential need for better data structures, 
> separation of mixed concerns, etc. In haskell "boolean blindness" is another.
>
> When writing tacit verbs, I find that trying to avoid ("), ([) or (]), 
> and parentheses as much as possible often helps me find better 
> solutions. That's what prompted this question.
>
> Anyway, what are similar code anti-patterns in J (or APL) that have 
> helped you write better J by recognizing and avoiding them?
>
>
> Cheers!
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
    
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to