Services & Resources / Wolfram Forums
-----
 /
MathGroup Archive
2007
*January
*February
*March
*April
*May
*June
*July
*August
*September
*October
*Archive Index
*Ask about this page
*Print this page
*Give us feedback
*Sign up for the Wolfram Insider

MathGroup Archive 2007

[Date Index] [Thread Index] [Author Index]

Search the Archive

Re: Module inside Module. Conflict between inner Module local variable

  • To: mathgroup at smc.vnet.net
  • Subject: [mg79678] Re: Module inside Module. Conflict between inner Module local variable
  • From: Christian & Nicky Chong-White <christian_chongwhite at hotmail.com>
  • Date: Wed, 1 Aug 2007 05:13:58 -0400 (EDT)
  • References: <f8n1jt$j9h$1@smc.vnet.net>

Jean-Marc,

I second Cliffords comments. Well specified. A quality reply indeed.

As an exploratory aside:
Code re-writing or not, it would seem sensible to have the option in
Module to assign a level specification to which parameter variables
(patterns) are rewritten. This option would allow a user to specify
that only the first level (or others specified) within Module would
have the parameter values rewritten. The effect would allow the user
to create "re-writing scope" within functions This would follow
similar Mathematica theme to how one uses the levelspec in Map to
apply a function at a level specification, or a more relevant example,
use a levelspec in Replace to apply a rewriting rule to a level
specification.

Module[{x,y, ...}, expr,levelspec]

Just an idea. (For interested readers look at the new related
functions Interpretation and DynamicModule for different perhaps
already extended Module 'interpretations' - excuse the pun :-) ).

Happy re-writing rules,
Christian



  • Prev by Date: Multi-variable Integration
  • Next by Date: Re: presence of Wolfram Research in this mailing list
  • Previous by thread: Re: Multi-variable Integration
  • Next by thread: Re: Re: Module inside Module. Conflict between inner Module local variable