zsh-workers
 help / color / mirror / code / Atom feed
From: ramos@ih4ess.ih.lucent.com
To: zsh-workers@math.gatech.edu
Subject: leftover debugging statements?
Date: Sat, 1 Nov 1997 16:01:07 -0600	[thread overview]
Message-ID: <199711012201.QAA13863@ihnns581.ih.lucent.com> (raw)


hello,

Did somebody leave some leftover debugging statements in
zsh 3.0.5?

Some assignments to a local (typeset) variable cause
some garbage to be printed out.

Example script & output (sorry I don't have time to
isolate this any further... I hope this is enough to
jog someone's memory):

PS1='zsh> '
 
zsh> which bug
bug () {
        typeset fred
        fred=NULL 
        typeset sourcefile
        echo 'Start loop...'
        for sourcefile in $*
        do
                typeset bar
                if [[ $fred = NULL ]]
                then
                        typeset foo
                        foo=(`echo output from some process`) 
                        bar=$foo[0] 
                else
                        bar=$fred 
                fi
        done
        echo 'End loop...'
        return 0
}
 
zsh> bug X Y Z
Start loop...
bar=output
foo=(output from some process)
bar=output
foo=(output from some process)
End loop...
 
zsh> setopt
allexport
autocd
autolist
autopushd
cdablevars
extendedglob
interactive
nolistbeep
login
menucomplete
monitor
pushdignoredups
pushdsilent
rmstarsilent
shinstdin
zle
 
zsh> echo $ZSH_VERSION
3.0.5
 
zsh> uname -a
SunOS ihnns581 5.5.1 Generic_103640-12 sun4u sparc SUNW,Ultra-1
 
##

Obviously, the function was not supposed to print anything out
except "Start loop..." and "End loop...".

Thanks,

--
Alex Ramos


             reply	other threads:[~1997-11-01 22:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-01 22:01 ramos [this message]
1997-11-02 11:24 ` C. v. Stuckrad
1997-11-02 16:48 ` stringfellow.n.d

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

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

  git send-email \
    --in-reply-to=199711012201.QAA13863@ihnns581.ih.lucent.com \
    --to=ramos@ih4ess.ih.lucent.com \
    --cc=zsh-workers@math.gatech.edu \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).