unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "gebser@mousecar.com" <gebser@mousecar.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Quickly check for differences in code and locate possible errors.
Date: Tue, 28 Mar 2023 10:40:37 -0400	[thread overview]
Message-ID: <dbe054e1-b884-1349-ace0-dff307a603c1@mousecar.com> (raw)
In-Reply-To: <CAGP6POK9NMsh6WtE5uORwofsCwOmxO07MGADRROrw3Pq-mBB-w@mail.gmail.com>

On 3/28/23 9:56 AM, Hongyi Zhao wrote:
> Hi here,
> 
> I've the following two lines of wolfram code written in two versions:
> 
> Version 1. This is the correct version:
> 
> getPGRotMat =getRotMat[If[MemberQ[RotMat[[1]]["CubiPrim"],
> #],"CubiPrim","HexaPrim"],#]&;
> Grid[Table[{PGinfo[[i,;;2]],{#\[RightArrow]getPGRotMat[#]} &
> /@getPGElem[i]},{i,32}],Frame -> All]
> 
> Version 2. This is the wrong version:
> 
> getPGRotMat =getRotMat[If[MemberQ[RotMat[[1]]["CubiPrim"],#],"CubiPrim","HexaPrim"],#]&;
> Grid[Table[{PGinfo[i,;;2],{#\[RightArrow]getPGRotMat[#]} &
> /@getPGElem[i]},{i,3}],Frame \[RightArrow] All]
> 
> I would like to know whether it's possible to quickly check for
> differences in code and locate possible errors with the help of Emacs.
> Any tips will be appreciated.
> 
> Regards,
> Zhao

It's been a long time since I've compiled something in an emacs buffer, 
so I can't speak to locating code errors, and have no experience with 
wolfram.  "C-h a diff ENTER" displays a few possibilities for finding 
differences.



  reply	other threads:[~2023-03-28 14:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 13:56 Quickly check for differences in code and locate possible errors Hongyi Zhao
2023-03-28 14:40 ` gebser [this message]
2023-03-28 15:03 ` Gregory Heytings
2023-03-29  2:04   ` Hongyi Zhao
2023-03-29  8:34     ` Gregory Heytings

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=dbe054e1-b884-1349-ace0-dff307a603c1@mousecar.com \
    --to=gebser@mousecar.com \
    --cc=help-gnu-emacs@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).