Git OS X packages are over here:

code.google.com/p/git-osx-installer/

Tim

--- In iolanguage@yahoogroups.com, Jon Kleiser <jon.kleiser@...> wrote:
>
> What's the best way to install git (the new source control system for
> Io) on Mac OS X?
> I downloaded git-1.5.0.tar.bz2.tar and followed the instructions
> ("make" followed by "make install"). The make ended with a
> make: *** [git-http-fetch] Error 1
>
> When I try "~/git-1.5.0/git clone git://www.iolanguage.com/Io", I get
> "git: 'clone' is not a git-command".
>
> I'm using a G5 PPC Mac.
>
> /Jon
>

Io enters the top 50 (at position 49) of the TIOBE Programming
Community Index for May 2008 [1].

Congratulation!

[1] http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html

Hello! =)

My name is Paulo Köch. I'm from Porto, Portugal. I discovered Io through _why's
post and I'm
enjoying it very much!

I already tried to contribute, putting two issues up on Io's website. Is that
the best place to
submit them? I also sent a path for the TextMate bundle to Rob. I hope to hear
from him
soon.

And, for the challenge!!! =P How can you implement a function that outputs the
name of the
receiver? For example, calling 'obj receiverName' would return "obj". I tried to
explore "call
message"'s capabilities but didn't find anything appropriate (previous was the
closest thing).

I ran into this problem when I was trying to implement a generic "printf style
debug" helper,
somewhat like var_dump in PHP (this was before using slotSummary). Since Io is
King on
reflection, i wanted to output the callee's name. Any tips on better debugging
solutions will
also be greatly appreciated! =)

Thanks for the wonderful language!
Paulo Köch

IMHO, the best way to submit bugs is either to this list or directly
to Steve Dekorte.

You can write: pDebug := method(call message prev name print; self)

I don't understand exactly what you mean about debugging. Is something
like: {{{ object println method }}} not enough?

Cheers,
- Danya

Unfortunately there is no easy way to to get the previous message. You
can go through all the message objects returned by Collector
allObjects, check for the next message attached to the message you're
at's unqiueId that's the same as your message (call message)... for
instance:

Message previous := method(
      Collector allObjects foreach(o,
          if(o isKindOf(Message),
              if(o next uniqueId == self uniqueId, return o)
          )
      )
)

But that's highly inefficient as it traverses all objects in the
heap... but it's better than nothing. Unfortunately, since Io is an
eager language (don't take the fact it lets you delay evaluation as
being lazy, all messages are evaluated as messages at the very least,
all the time)... it's very difficult to implement a "previous" pointer
on the AST when the AST allows you to make manipulations to it. It
would have to be special, and I'm all for that, but it's a tough sell
to many.

--
Jeremy Tregunna
jtregunna@...



On 6-May-08, at 10:06 AM, Paulo Köch wrote:

> Hello! =)
>
> My name is Paulo Köch. I'm from Porto, Portugal. I discovered Io
> through _why's post and I'm
> enjoying it very much!
>
> I already tried to contribute, putting two issues up on Io's
> website. Is that the best place to
> submit them? I also sent a path for the TextMate bundle to Rob. I
> hope to hear from him
> soon.
>
> And, for the challenge!!! =P How can you implement a function that
> outputs the name of the
> receiver? For example, calling 'obj receiverName' would return
> "obj". I tried to explore "call
> message"'s capabilities but didn't find anything appropriate
> (previous was the closest thing).
>
> I ran into this problem when I was trying to implement a generic
> "printf style debug" helper,
> somewhat like var_dump in PHP (this was before using slotSummary).
> Since Io is King on
> reflection, i wanted to output the callee's name. Any tips on better
> debugging solutions will
> also be greatly appreciated! =)
>
> Thanks for the wonderful language!
> Paulo Köch
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

>  You can write: pDebug := method(call message prev name print; self)
Oops. A while ago it seemed to me that message tree does have previous
pointer...

Since it's not there, you're left with inspecting the 'self' object
for it's type and slots, but not for the name it was referenced
under...

- Danya

Very funny! The slot 'previous' is implemented in internal
representation, accessor method for it is implemented too and it is
even documented -- but not bound into Message namespace!

Steve, please fix this :)

On Tue, May 6, 2008 at 10:16 PM, Danya Alexeyevsky <me.dendik@...> wrote:
> >  You can write: pDebug := method(call message prev name print; self)
>  Oops. A while ago it seemed to me that message tree does have previous
>  pointer...
>
>  Since it's not there, you're left with inspecting the 'self' object
>  for it's type and slots, but not for the name it was referenced
>  under...
>
>  - Danya
>

Currently, Io treats interactive input, program code and program
arguments as UTF8 (ignoring locale, too). The only way you can pass
non-UTF data to Io is through file read operations (e.g., standard
input).

Here's a piece of code I played around with to check it. I hope that helps.

{{{
#!/usr/bin/env io

p := method(s,
  for(i, 0, s size println, s at(i) println)
)

# p(System args println at(1))
p(File standardInput contents)
}}}

Cheers,
- Danya

On 2008-05-06, at 7:06 AM, Paulo Köch wrote:
> And, for the challenge!!! =P How can you implement a function that
> outputs the name of the
> receiver? For example, calling 'obj receiverName' would return "obj".


There's no Message previous method, which AFACT, is what you're asking
for. One trick to get around it that's reasonably efficient would be
to do this (which only works when called within a block/method:

Message messageBefore := method(m,
	 if(next == m, return self)
	 if(next, return next messageBefore(m))
	 nil
)

Object receiverName := method(
	 call sender call activated message messageBefore(call message) name
)


test := method(
	 foo := Object clone
	 foo receiverName println
)

test

On 2008-05-06, at 11:20 AM, Danya Alexeyevsky wrote:
> Very funny! The slot 'previous' is implemented in internal
> representation, accessor method for it is implemented too and it is
> even documented -- but not bound into Message namespace!

It was ifdef'd out - I've pushed a version with it enabled and it
seems to work but this is experimental.

Cheers,
- Steve

Hello!

On Tue, May 6, 2008 at 7:06 PM, Danya Alexeyevsky <me.dendik@...> wrote:
> IMHO, the best way to submit bugs is either to this list or directly
>  to Steve Dekorte.

Why do we have the issues section in the page, then? Shouldn't it just
point here? It confuses people (as it confused me! =P).

>  I don't understand exactly what you mean about debugging. Is something
>  like: {{{ object println method }}} not enough?
Debugging printf style is just printing all values (from most to least
suspicious) to find a bug.
I didn't quite understand that snippet of code. =/

On Wed, May 7, 2008 at 2:00 AM, Steve Dekorte <steve@...> wrote:
>  It was ifdef'd out - I've pushed a version with it enabled and it
>  seems to work but this is experimental.
  Why was it def'ed out? Any particular reason?

Steve, just to make things clear, what you did was just iterate all
the method tokens until we found the one before our target, right?

Cheers!

On Wed, May 7, 2008 at 3:11 PM, Oscar Martinez <wasi.network@...> wrote:
> PD: My aplogizes for not preppending "[Io]" to the subject. Sorry.

I think it's added automatically by the mailing list, no need to apologise. =P

Setup:
obj := Object clone
obj a := method( deprecatedWarning("b"))
obj b := method( "hello!" println )


Current behaviour:
Io> obj a
Warning in Command Line: 'a' is deprecated.
   Exception: Object does not respond to 'name'
   ---------
   Object name                          A2_Object.io 476
   Object a                             Command Line 1
   Object deprecatedWarning             Command Line 1

Expected behaviour:
Io> obj a
Warning in Command Line: 'a' is deprecated. use 'b' instead.

Reason:
In the deprecatedWarning method, the if is testing the wrong variable.

Proposed implementation:
Object deprecatedWarning := method(newName,
                 writeln("Warning in ", call sender call message label,
": '", call sender call message name, "' is deprecated. ", if(newName,
"use '" .. newName .. "' instead.", ""))
                 self
         )

Current behaviour:
$ make RandomAddon
[make's output]
make: *** [install] Error 71

   Exception: nil does not respond to 'build'
   ---------
   nil build                            Project.io 35
   Project buildAddon                   build.io 13

Expected behaviour:
$ make RandomAddon
[make's output]
No addon named 'RandomAddon' found!

Reason:
Project buildAddon doesn't check if the selected addon exists.

Proposed implementation:
Project buildAddon := method(name,
                 currentAddon := addons detect(addon, addon name == name)
                 if(currentAddon,
                         currentAddon build(options),
                         "No addon named '#{name}' found!" interpolate println
                 )
         )

>  > I don't understand exactly what you mean about debugging. Is something
>  > like: {{{ object println method }}} not enough?
>  Debugging printf style is just printing all values (from most to least
>  suspicious) to find a bug.
>  I didn't quite understand that snippet of code. =/

The {{{ println }}} method prints some representation of object the
message is sent to and returns the object unmodified. So, you can
insert it seamlessly anywhere within your code to see what data is
passed there. So, the code {{{ object method }}} differs from {{{
object println method }}} only in object's value being printed to
standard output. That's the simplest of all printf-style debug
approaches in Io (and among other languages, probably, too).

----------
There are also very flexible debug hooks built into language that
require some wrapper code to create a useable debuggers. I use it for
some very basic profiling my code. Try inserting this snippet
somewhere in the beginning of your code:

{{{
Debugger vmWillSendMessage := method(
         if(self message label beginsWithSeq("io/"), return) # filter
some messages
         write(self message label, ":")
         write(self message lineNumber, ":")
         write(self message asString asMutable escape slice(0, 60), "\n")
)
Coroutine currentCoroutine setMessageDebugging(true)
}}}

Cheers,
- Danya

On 2008-05-07, at 7:17 AM, Paulo Köch wrote:

> Steve, just to make things clear, what you did was just iterate all
> the method tokens until we found the one before our target, right?

I iterated the message objects in the method, yes.

On 2008-05-07, at 7:25 AM, Paulo Köch wrote:

> Current behaviour:
> $ make RandomAddon
> [make's output]
> make: *** [install] Error 71
>
>  Exception: nil does not respond to 'build'

This was fixed with a recent push. Please do a git pull, a clean build
and try again.

On 2008-05-07, at 11:43 AM, Steve Dekorte wrote:

>
> On 2008-05-07, at 7:17 AM, Paulo Köch wrote:
>
>> Steve, just to make things clear, what you did was just iterate all
>> the method tokens until we found the one before our target, right?
>
> I iterated the message objects in the method, yes.

BTW, here's how to implement it using the latest Io with Message
previous support:

receiverName := method(call message previous name)

In wanting to learn more about how Io is built, I've run Doxygen
against the Io C internals and have posted the output here:

http://io.jesseross.com/docs/current/

Hopefully this will be helpful to someone else as well. Happy hacking!


J.

On Wed, May 7, 2008 at 4:11 PM, Jesse Ross <io@...> wrote:
> In wanting to learn more about how Io is built, I've run Doxygen
>  against the Io C internals and have posted the output here:
>
>  http://io.jesseross.com/docs/current/
>
>  Hopefully this will be helpful to someone else as well. Happy hacking!

It looks great actually.  This will make a great reference and might
come in handy when going through something with gdb.

Rock on,
Brian.

On Wed, May 7, 2008 at 3:26 PM, Danya Alexeyevsky <me.dendik@...> wrote:
>  The {{{ println }}} method prints some representation of object the
>  message is sent to and returns the object unmodified. So, you can
>  insert it seamlessly anywhere within your code to see what data is
>  passed there. So, the code {{{ object method }}} differs from {{{
>  object println method }}} only in object's value being printed to
>  standard output. That's the simplest of all printf-style debug
>  approaches in Io (and among other languages, probably, too).

Yes, I got that. What struck me as odd was it being written as {{{
object println method }}} instead of {{{ object method println}}}.
I guess it's just personal preference (and the fact that most other
languages don't return self in println =P).

>  There are also very flexible debug hooks built into language that
>  require some wrapper code to create a useable debuggers. I use it for
>  some very basic profiling my code. Try inserting this snippet
>  somewhere in the beginning of your code:
>
>  {{{
>  <snip>
>  }}}

I've just read about it in the docs. At first glance, it was somehow
not clear how to use the hook (as in, what to call in the method for
it to be useful), but you example is a wonderful starting point. Maybe
it should be the default method, since it's only called when the flag
is on (the default impl. seems too bare). Just an opinion. =)

On Wed, May 7, 2008 at 8:43 PM, Steve Dekorte <steve@...> wrote:
>  BTW, here's how to implement it using the latest Io with Message
>  previous support:
>
>  receiverName := method(call message previous name)

Yes, it becomes very simple with previous. =)

>  Yes, I got that. What struck me as odd was it being written as {{{
>  object println method }}} instead of {{{ object method println}}}.
>  I guess it's just personal preference (and the fact that most other
>  languages don't return self in println =P).

I wanted to show that you can inspect intermediate results besides
finite results of expressions. I should've explained it. (There is an
unspoken rule in mathematics to give first non-trivial case as
example. {{{ object method println }}} would feel almost the same as
{{{ object println }}}, which does not work well as an example of
approach to debugging).

>  I've just read about it in the docs. At first glance, it was somehow
>  not clear how to use the hook (as in, what to call in the method for
>  it to be useful), but you example is a wonderful starting point. Maybe
>  it should be the default method, since it's only called when the flag
>  is on (the default impl. seems too bare). Just an opinion. =)

Thanks :) I think, it's up to Steve to decide: there actually is
already a little more primitive example in the Debugger object (either
{{{ Debugger getSlot("vmWillSendMessage") }}} or look at
libs/iovm/io/Debugger.io) and I built my version by expanding that
one.

There are also a few people on the list that are willing to write a
full-featured debugger... But I think it won't happen soon.

Cheers,
- Danya

There are other messages about building Io on OSX Leopard but they
don't seem to apply.  I've built the VM and it works fine, but I can't
build the add-ons; well the addon dependencies.  I use the command
'sudo make port' and it fails because of a missing file called
libsgml.a.  I've tried building libsgml with the makefile in the
folder (addons/SGML/source/libsgml) but this also fails.  I'm afraid I
ran out of steam at that point.  Does anyone have a suggestion as to
how I can progress?

On 2008-05-07, at 1:50 PM, Brian Mitchell wrote:

> It looks great actually.  This will make a great reference and might
> come in handy when going through something with gdb.

It would be nice if github generated these on the latest master
automatically...

On 2008-05-07, at 2:57 PM, Danya Alexeyevsky wrote:

> There are also a few people on the list that are willing to write a
> full-featured debugger... But I think it won't happen soon.

I'd be willing to set aside some time to help with this if we can get
someone willing to get it talking to TextMate so we can step through
code and have it highlighted in the editor.

On Wed, May 7, 2008 at 8:31 PM, Steve Dekorte <steve@...> wrote:
>  On 2008-05-07, at 1:50 PM, Brian Mitchell wrote:
>
>  > It looks great actually. This will make a great reference and might
>  > come in handy when going through something with gdb.
>
>  It would be nice if github generated these on the latest master
>  automatically...

It would be nice if they supported doxygen but I have my doubts that
they will.  It wouldn't be hard to setup a hook however. They have the
URL post back that could set off some sort of script on a machine that
has doxygen, graphviz, and git installed. I've got a server I could
attempt this with, though, I have never used doxygen before so I might
need some guidance from Jesse Ross to get the same results.

Brian.