This is the mail archive of the kawa@sourceware.org mailing list for the Kawa project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: supporting dynamic/interactive procedure re-definition


On 10/03/2010 11:10 PM, Helmut Eller wrote:
* Per Bothner [2010-09-06 04:43] writes:

There are probably other limitations (and bugs); please let me know.

... Isn't baz supposed to call version 2?

Indeed. Things I had working no longer seem to be. I guess another look is in order ...

Also isn't there a more direct way to call non-exported toplevel
functions?  E.g. there could be a namespace for the module foo and
foo:bar could refer the non-exported function.

One of the reasons for module-private variables is so that the compiler can see every use. That means a variable might be optimized away, or represented in a non-standard way.

But the bigger reason is for information hiding.  So the programmer
can change module internals and not have to worry about clients
depending on those internals.

Of course a debugger needs access to internal definitions, and I could
see it might be useful during development.  So perhaps there could be
a debug mode allowing what you're asking for.  How much of an
annoyance is this?
--
	--Per Bothner
per@bothner.com   http://per.bothner.com/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]