zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
	zsh-workers@sunsite.dk
Subject: Re: PATCH: doshfunc
Date: Tue, 10 Jul 2001 16:06:16 +0000	[thread overview]
Message-ID: <1010710160616.ZM29244@candle.brasslantern.com> (raw)
In-Reply-To: <200107100942.LAA17143@beta.informatik.hu-berlin.de>

On Jul 10, 11:42am, Sven Wischnowsky wrote:
} Subject: Re: PATCH: doshfunc
}
} Bart Schaefer wrote:
} 
} > 	foo () {
} > 		bar () {
} > 			print oops
} > 		}
} > 		foo "$@"
} > 	}
} > 
} > Something has magically supplied the `foo "$@"' at the end of the file!
} 
} It's eval_autoload() -- which you wrote this way in 8404 ;-)

No, it's not eval_autoload():

2122        if (!(shf->flags & PM_UNDEFINED))
(gdb) n
2125        if (shf->funcdef) {
(gdb) 
2126            freeeprog(shf->funcdef);
(gdb) 
2127            shf->funcdef = &dummy_eprog;
(gdb) 
2129        if (ops['X'] == 1) {
(gdb) 
2138        return !loadautofn(shf, (ops['k'] ? 2 : (ops['z'] ? 0 : 1)), 1);

The code that does `name "$@"' in eval_autoload() is assembling a command
to pass to bin_eval().  It doesn't append anything to the function def'n.

} > ...
} > 
} > So I still can't reach the `goto doneshfunc'.
} 
} You were asking about EF_RUN, that's what I tried to explain.

Right, I asked about EF_RUN because that error message is inside an
`if (prog->flags & EF_RUN)'.

} If you want that error message:
} 
}   % echo 'bar() { echo foobar }' >foo
}   % zcompile -k foo
}   % fpath=(. $fpath)
}   % autoload foo
}   % foo
}   zsh: foo: function not defined by file

That error message came from line 3253, not line 3381.

} or:
} 
}   % rm -f foo.zwc
}   % echo 'bar() { echo foobar }' >foo
}   % setopt kshautoload
}   % fpath=(. $fpath)
}   % autoload foo
}   % foo
}   zsh: foo: function not defined by file

Same thing there; the error is from line 3253.

Once again, what I want to know is how you reach line 3372 with EF_RUN in
the Eprog flags, and hence get the error from line 3381.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2001-07-10 16:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-15 13:22 Is PRINT_EXIT_VALUE supposed to work? Peter Stephenson
2001-06-24  4:06 ` PATCH: " Bart Schaefer
2001-07-03 17:13   ` Peter Stephenson
2001-07-03 17:46     ` Bart Schaefer
2001-07-08 15:19     ` Bart Schaefer
2001-07-09  8:22       ` Sven Wischnowsky
2001-07-09 11:08         ` PATCH: doshfunc() Bart Schaefer
2001-07-09 11:28           ` PATCH: doshfunc Sven Wischnowsky
2001-07-09 16:11             ` Bart Schaefer
2001-07-10  9:42               ` Sven Wischnowsky
2001-07-10 16:06                 ` Bart Schaefer [this message]
2001-07-11  7:18                   ` Sven Wischnowsky

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=1010710160616.ZM29244@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.dk \
    /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).