Or, more conservatively, every struct and object in a given package, file,
or set of files.
On Wed, Jan 21, 2015 at 11:03 AM, Byron Davies byrondav...@starshine.us
wrote:
Would it be easy to create a compiler flag that would make every struct
and object transparent? This would then make it
Sounds like a straightforward change to the existing macros. Why don't you
create a fork and experiment?
On Jan 21, 2015, at 1:15 PM, Byron Davies byrondav...@starshine.us wrote:
Or, more conservatively, every struct and object in a given package, file, or
set of files.
On Wed, Jan 21,
Would it be easy to create a compiler flag that would make every struct and
object transparent? This would then make it easy to create a Lisp
Machine-style Inspector that would be able to roam through every data
structure during debugging.
Byron
_
Racket Developers
[Reposted from -users, since it seems likely I erred in my initial
selection of that list]
Hi all,
Over the past few months, more and more subsystems have started logging
at info level as part of regular compilation.
I prefer having PLTSTDERR=info in order to catch log-info that happens
at
Nice parry! What may be straightforward to you may not be so obvious to
me. But I'll take a look.
I'm deep into a project using Racket for weakest precondition analysis.
Every time I'm debugging it seems like I have to write another
special-purpose accessor, or export some existing accessor up
5 matches
Mail list logo
