Hi
I want to generalize a debugging routine.
Instead of writing a horrible hardcoded
43: player:tell(now come to verb `:go_crazy', line 43);
44: player:tell(value at this point: , value);
and the like all the time, I have written a verb
#1:debug(?msg)
--
{?msg = {}} =
Andrew Wendt wrote:
Using callers() won't reveal the line, but callers(1) will, right?
*bonk* *bonk* *bonk* = my head against the wall
*blush*
humbleThanks/humble
- Daniel
#
This message is sent to you because you are subscribed to
the
Dr Robert Sanderson wrote:
Historically, as I'm sure you're all aware, the only reason for these
forks is that moo-cows and similar contact with the 'main' 'developers'
has been intermittent at best. And when people have tried to make
contact in person, there's been no response.
Me too I had
Sean Davis wrote:
Yes. In fact, it surprises me very much that I can load a core on a MSB LP64
machine (UltraSPARC in this case) and have it work just fine. Then again,
UltraSPARC is not nearly as picky as Alpha when it comes to unaligned memory
access.
It's exactly as picky, but your SPARC OS
There are still another few things I could wish we could incorporate into a
possible new lamdaMOO release. I wonder if we could compute a list of
changes that have been done in the various versions, and then possibly
merge them into one?
A 2.0 release goal would be mega cool. Please keep this
On Monday 06 December 2004 15:55, H. Peter Anvin wrote:
Dr Robert Sanderson wrote:
Minor enhancement request:
* Remove the auto-aliases for : ; into a simple configuration file.
(Eg to allow for ' - say ; : - emote | - eval)
Probably should just be a server object control property.
Or
As far as all this goes, I have a few suggestions.
First, no offence to Luke-Jr, but I've ran into a lot of compilation
glitches with GammaMoo and its code-quality isn't all that great. I'd
suggest either starting from the current Lambda CVS and merging
third-party patches for a 2.0 release or
