meerkat-dist-devel — Meerkat Developer's Mailing List

[Meerkat-dist-devel] What's happening

[Travis A. <ia...@gm...>]

I know I haven't posted anything new about meerkat fora while. That's
because I've realized that meerkat is in desperate need of developer
documentation. Until this documentation is completed, I don't think it
will be prudent to go on with development. So, I'm asking all of you,
the meerkat developers, what kind of documentation would you like to
see?

Being the original writer of meerkat, everything about it makes sense
to me. It's difficult to know what you might not understand when
everything seems so intuitive to me. I really need your help in
writing this documentation.

Give me examples, give me questions. Tell me what you want to know and
I'll document it. If you don't understand resources and think a
diagram would help, I'll do that. If you still don't understand and
want a 3d animation, I'll do that too.

If we work together, I think we could get some rough documenation done
in a week. This documentation will then be there for future
developers.

Hoping to hear from you soon,
Travis.

-- 
Travis Athougies

[Meerkat-dist-devel] Meeting Sunday

[Travis A. <ia...@gm...>]

Devs,

Okay, in a last ditch attempt to have everyone together at a meeting,
I'm moving the developer meeting this Sunday to 7:00 pm PST (GMT +8).
Which I think means that are farthest developers in India will have it
at 7:00 or 7:30 AM on monday, which I think is semi-feasible.

I want everyone to be there. At least just pop in to say hi, so I know
you still have interest in this project. If you really can't come,
e-mail me. Basically, I want to assess all your skills and expose you
to parts that need lots of improvement.

If you don't come to this meeting or e-mail the list, I'll remove you
from the project.

Travis.

-- 
Travis Athougies

Re: [Meerkat-dist-devel] Meeting tomorrow

[Travis A. <ia...@gm...>]

That's fine, it's better to be honest.

It was nice to have had you on the team.

If you ever want to rejoin the project, we'll be more than happy to
have you back.

Travis.

On Sun, Jan 17, 2010 at 3:27 PM, Brian Sheppard
<bri...@gm...> wrote:
> Hey guys,
>
> Unfortunately, I don't think I'll have the time to work on Meerkat, which
> sucks because I think it's a great project. However with the issues at work
> and lack of man power, I just don't have time. I thought it would be better
> after New Year's, but we still have not managed to hire anyone else on my
> team at work and I'm having to devote much of my personal time to that.
> Sorry for any inconvenience and I hope you understand.
>
> Best Wishes,
>
> - Brian
>
> On Jan 16, 2010 9:19 PM, "Travis Athougies" <ia...@gm...> wrote:
>
> Tomorrow at 3:00PM PST (GMT +8), we will have a live meeting in
> #meerkat-dist on irc.freenode.net.
>
> As I said earlier this week, I need everyone to be there.
>
> Travis.
>
> --
> Travis Athougies
>
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> _______________________________________________
> Meerkat-dist-devel mailing list
> Mee...@li...
> https://lists.sourceforge.net/lists/listinfo/meerkat-dist-devel
>



-- 
Travis Athougies

Re: [Meerkat-dist-devel] Meeting tomorrow

[Brian S. <bri...@gm...>]

Hey guys,

Unfortunately, I don't think I'll have the time to work on Meerkat, which
sucks because I think it's a great project. However with the issues at work
and lack of man power, I just don't have time. I thought it would be better
after New Year's, but we still have not managed to hire anyone else on my
team at work and I'm having to devote much of my personal time to that.
Sorry for any inconvenience and I hope you understand.

Best Wishes,

- Brian

On Jan 16, 2010 9:19 PM, "Travis Athougies" <ia...@gm...> wrote:

Tomorrow at 3:00PM PST (GMT +8), we will have a live meeting in
#meerkat-dist on irc.freenode.net.

As I said earlier this week, I need everyone to be there.

Travis.

--
Travis Athougies

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for
Conference
attendees to learn about information security's most important issues
through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Meerkat-dist-devel mailing list
Mee...@li...
https://lists.sourceforge.net/lists/listinfo/meerkat-dist-devel

[Meerkat-dist-devel] Meeting tomorrow

[Travis A. <ia...@gm...>]

Tomorrow at 3:00PM PST (GMT +8), we will have a live meeting in
#meerkat-dist on irc.freenode.net.

As I said earlier this week, I need everyone to be there.

Travis.

-- 
Travis Athougies

Re: [Meerkat-dist-devel] Developer needed for Distributed Com

[deenadayalan k <day...@gm...>]

Hi Tavis,

Can you please send me the meerkat source package tarball?

Thanks,
Deenadayalan


On Tue, Jan 12, 2010 at 1:48 PM, deenadayalan k <day...@gm...>wrote:

> Hi Travis,
>
> Googled informartion for the above error.
>
> http://forums.site5.com/showthread.php?p=149150
> http://www.gelato.unsw.edu.au/archives/git/0605/20509.html
>
> --Deenadayalan
>   On Tue, Jan 12, 2010 at 1:15 PM, deenadayalan k <day...@gm...>wrote:
>
>> Hi Travis,
>>
>> Can you please send me the meerkat source package tarball?
>>
>> Thanks & Regards
>> Deenadayalan
>>
>>   On Tue, Jan 12, 2010 at 12:10 PM, Travis Athougies <ia...@gm...>wrote:
>>
>>> Deenadayalan,
>>>
>>> I'm not too familiar with rhel. I would suggest trying again. If this
>>> really doesn't work, I can send you a package tarball, but that would
>>> be a last resort.
>>>
>>> Travis
>>>
>>> On Monday, January 11, 2010, deenadayalan k <day...@gm...>
>>> wrote:
>>> > Hi Travis,
>>> >
>>> > I was not able to come to #meerkat-dist on irc.freenode.net <
>>> http://irc.freenode.net/>? because i was in office at that time.
>>> >
>>> > Im using RHEL 4, Kernal 2.6.9-67.
>>> >
>>> > I am also thinking that the issue im getting is related with git.
>>> >
>>> > I searched git 1.6.3.3 release but i could only find the source not the
>>> binaries for RHEL linux, if you have any information on where i can download
>>> git 1.6.3.3 binary for RHEL4 linux then please let me know.
>>> >
>>> > Thanks,
>>> > Deenadayalan
>>> >
>>> >
>>> > On Mon, Jan 11, 2010 at 9:10 AM, Travis Athougies <ia...@gm...>
>>> wrote:
>>> >
>>> >
>>> > Deenadayalan,
>>> >
>>> >
>>> > This is very weird behavior. If you can contact the server, that means
>>> that something is wrong with git itself. I'm thinking maybe the first error,
>>> the one about missing templates might be your problem. You should ask on the
>>> git mailing list or irc chatroom what this message means.
>>> >
>>> >
>>> >
>>> > Btw, what Linux distro are you using? Whatever it is, you might want to
>>> try reinstalling git. If you are online right now, could you head over to
>>> #meerkat-dist on irc.freenode.net <http://irc.freenode.net/>? I can help
>>> you there.
>>> >
>>> >
>>> >
>>> > Travis
>>> >
>>> >
>>> >
>>> > On Jan 10, 2010, at 7:30 PM, deenadayalan k <day...@gm...>
>>> wrote:
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > Hi Travis,
>>> >
>>> > I am able to ping the following URL address.
>>> >
>>> > ping meerkat-dist.git.sourceforge.net
>>> >
>>> > PING gitscm.sourceforge.net <http://gitscm.sourceforge.net/>
>>> (216.34.181.91) 56(84) bytes of data.
>>> > 64 bytes from gitscm.sf.net <http://gitscm.sf.net/> (216.34.181.91):
>>> icmp_seq=0 ttl=242 time=266 ms
>>> > 64 bytes from gitscm.sf.net <http://gitscm.sf.net/> (216.34.181.91):
>>> icmp_seq=1 ttl=242 time=265 ms
>>> > 64 bytes from gitscm.sf.net <http://gitscm.sf.net/> (216.34.181.91):
>>> icmp_seq=2 ttl=242 time=266 ms
>>>  >
>>> > Thanks,
>>> > Deenadayalan
>>> >
>>> >
>>> > On Mon, Jan 11, 2010 at 7:59 AM, Travis Athougies <ia...@gm...>
>>> wrote:
>>> > Deenadayalan,
>>> >
>>> > I don't know what to tell you. The command works on my computer and I
>>> > can definitely connect to the git repository.
>>> >
>>> > From the error it looks like somewhere along the line the dns
>>> > resolution for the domain name isn't working. This might be because
>>> > the name is blocked by whatever network you're on or it could be
>>> > because there has been a temporary error in Dns resolution. You should
>>> > contact your system administrator or ISP in the first case. In the
>>> > second case, you might have to wait a day or two and wait.
>>> >
>>> > You might want to try pinging meerkat-dist.git.sourceforge.net.
>>> >
>>> > I hope that helps.
>>> >
>>> > Travis.
>>> >
>>> >
>>> >
>>> > On Sunday, January 10, 2010, deenadayalan k <day...@gm...>
>>> wrote:
>>> >> Hi Travis,
>>> >>
>>> >> I am using GIT (1.6.2.5,  1.6.3.1, 1.6.5.2) with all these version, it
>>> fails with the following error.
>>> >>
>>> >> /depot/git-1.6.5.2/bin/git clone git://
>>> meerkat-dist.git.sourceforge.net/gitroot/meerkat-dist/meerkat-dist
>>> >>
>>> >> warning: templates not found
>>> //remote/ecisapps/depottst/git-1.6.5.2-bin/share/git-core/templates
>>> >> Initialized empty Git repository in
>>> /home/ddayalan/meerkat/meerkat-dist/.git/
>>> >> meerkat-dist.git.sourceforge.net[0: 216.34.181.91]: errno=Connection
>>> timed out
>>> >> fatal: unable to connect a socket (Connection timed out)
>>> >>
>>> >> Thanks,
>>> >> Deenadayalan
>>> >>
>>> >>
>>> >> On Sun, Jan 10, 2010 at 10:40 PM, Travis Athougies <
>>>
>>> --
>>> Travis Athougies
>>>
>>
>>
>

[Meerkat-dist-devel] Sunday meeting

[Travis A. <ia...@gm...>]

Attention:

we will have our first live meeting if 2010 this coming Sunday at
3:00pm pst (gmt+8). if you're interested in getting involved in
development you must be there. If this is an absolute inconvenient
time, let me know now so I can reschedule. I will answer all questions
for new developers.

I expect all those willing to participate to be in attendance.

Travis.

-- 
Travis Athougies

Re: [Meerkat-dist-devel] Developer needed for Distributed Com

[Travis A. <ia...@gm...>]

Deenadayalan,

I don't know what to tell you. The command works on my computer and I
can definitely connect to the git repository.

>From the error it looks like somewhere along the line the dns
resolution for the domain name isn't working. This might be because
the name is blocked by whatever network you're on or it could be
because there has been a temporary error in Dns resolution. You should
contact your system administrator or ISP in the first case. In the
second case, you might have to wait a day or two and wait.

You might want to try pinging meerkat-dist.git.sourceforge.net.

I hope that helps.

Travis.

On Sunday, January 10, 2010, deenadayalan k <day...@gm...> wrote:
> Hi Travis,
>
> I am using GIT (1.6.2.5,  1.6.3.1, 1.6.5.2) with all these version, it fails with the following error.
>
> /depot/git-1.6.5.2/bin/git clone git://meerkat-dist.git.sourceforge.net/gitroot/meerkat-dist/meerkat-dist
>
> warning: templates not found //remote/ecisapps/depottst/git-1.6.5.2-bin/share/git-core/templates
> Initialized empty Git repository in /home/ddayalan/meerkat/meerkat-dist/.git/
> meerkat-dist.git.sourceforge.net[0: 216.34.181.91]: errno=Connection timed out
> fatal: unable to connect a socket (Connection timed out)
>
> Thanks,
> Deenadayalan
>
>
> On Sun, Jan 10, 2010 at 10:40 PM, Travis Athougies <ia...@gm...> wrote:
> Deenadayalan,
>
> That command should work. Why don't you try again? I find that git is
> very sensitive to versions. What version are you using? I'm using git
> 1.6.3.3.
>
> As I said, we have most of the code documented. The most important
> source file is by far resource.c which contains the entire resource
> subsystem. I'd also look into the src/lang/ directory because that's
> where the meerkat language layer is.
>
> Hope that helps.
>
>
>
> On Sun, Jan 10, 2010 at 12:30 AM, deenadayalan k <day...@gm...> wrote:
>> Hi Travis,
>>
>> Thank for your support.
>>
>> I have already tried cloning of Meerkat source code using the below command
>> but there was "Unable to connect a socket" error.
>>
>> CMD: git clone
>> git://meerkat-dist.git.sourceforge.net/gitroot/meerkat-dist/meerkat-dist
>>
>> I am not sure the above error (time out error) is because of the server
>> busy? or the requested resource (URL location) is not exist.
>>
>> Can somebody help me on this issue?
>>
>> Travis, after i download the source code successfully, What should i start
>> looking in to in the source as starting point?
>>
>> Thanks & Regards
>> Deenadayalan
>>
>>
>> On Sun, Jan 10, 2010 at 1:42 AM, Travis Athougies <ia...@gm...> wrote:
>>>
>>> Deenadayalan,
>>>
>>> Sorry for the late reply. I haven't had a chance to get on the
>>> computer since our chat.
>>>
>>> Basically, once you have git installed, navigate to a directory where
>>> you'd like to put the source files and run
>>>
>>> git clone
>>> git://meerkat-dist.git.sourceforge.net/gitroot/meerkat-dist/meerkat-dist
>>>
>>> This should create directory called meerkat-dist where you can check
>>> out the source files.
>>>
>>> We do have doxygen documentation, with an appropriate doxygen.cfg in
>>> the doc directory. You run doxygen like doxygen doxygen.cfg and it
>>> will produce documentation.
>>>
>>> I hope that helps.
>>>
>>> Just so you know, we won't be meeting this sunday, but definitely next
>>> sunday.
>>>
>>> If you have any questions, forward them to the mailing list and me or
>>> another dev will get back to you ASAP.
>>>
>>> Regards,
>>> Travis.
>>>
>>> On Fri, Jan 8, 2010 at 9:45 AM, deenadayalan k <day...@gm...>
>>> wrote:
>>> > Hi Travis,
>>> >
>>> > Thanks for the information.
>>> > Can you please let me know where i can download meerkat open source
>>> > code?
>>> > I would like to have look at the source files.
>>> >
>>> > --Deenadayalan
>>> >
>>> > On Thu, Jan 7, 2010 at 9:24 PM, Travis Athougies <ia...@gm...>
>>> > wrote:
>>> >>
>>> >> Here is the link to join the meerkat-dist-devel mailing list:
>>> >> https://lists.sourceforge.net/lists/listinfo/meerkat-dist-devel
>>> >>
>>> >> Let me give you a quick overview of meerkat. It's a
>>> >> distributed/parallel programming environment. It's distributed in the
>>> >> sense that it runs accross many different computers and its parallel
>>> >> in that it attempts to run things concurrently.
>>> >>
>>> >> Meerkat is based loosely on the concept of actors, which are like
>>> >> objects in OOP. Instead of calling an actor's method, though, you send
>>> >> the actor a message. This means an actor can respond however it wants.
>>> >> It can handle the message right then and there or it

-- 
Travis Athougies

Re: [Meerkat-dist-devel] Developer needed for Distributed Com

[Travis A. <ia...@gm...>]

Deenadayalan,

That command should work. Why don't you try again? I find that git is
very sensitive to versions. What version are you using? I'm using git
1.6.3.3.

As I said, we have most of the code documented. The most important
source file is by far resource.c which contains the entire resource
subsystem. I'd also look into the src/lang/ directory because that's
where the meerkat language layer is.

Hope that helps.

On Sun, Jan 10, 2010 at 12:30 AM, deenadayalan k <day...@gm...> wrote:
> Hi Travis,
>
> Thank for your support.
>
> I have already tried cloning of Meerkat source code using the below command
> but there was "Unable to connect a socket" error.
>
> CMD: git clone
> git://meerkat-dist.git.sourceforge.net/gitroot/meerkat-dist/meerkat-dist
>
> I am not sure the above error (time out error) is because of the server
> busy? or the requested resource (URL location) is not exist.
>
> Can somebody help me on this issue?
>
> Travis, after i download the source code successfully, What should i start
> looking in to in the source as starting point?
>
> Thanks & Regards
> Deenadayalan
>
>
> On Sun, Jan 10, 2010 at 1:42 AM, Travis Athougies <ia...@gm...> wrote:
>>
>> Deenadayalan,
>>
>> Sorry for the late reply. I haven't had a chance to get on the
>> computer since our chat.
>>
>> Basically, once you have git installed, navigate to a directory where
>> you'd like to put the source files and run
>>
>> git clone
>> git://meerkat-dist.git.sourceforge.net/gitroot/meerkat-dist/meerkat-dist
>>
>> This should create directory called meerkat-dist where you can check
>> out the source files.
>>
>> We do have doxygen documentation, with an appropriate doxygen.cfg in
>> the doc directory. You run doxygen like doxygen doxygen.cfg and it
>> will produce documentation.
>>
>> I hope that helps.
>>
>> Just so you know, we won't be meeting this sunday, but definitely next
>> sunday.
>>
>> If you have any questions, forward them to the mailing list and me or
>> another dev will get back to you ASAP.
>>
>> Regards,
>> Travis.
>>
>> On Fri, Jan 8, 2010 at 9:45 AM, deenadayalan k <day...@gm...>
>> wrote:
>> > Hi Travis,
>> >
>> > Thanks for the information.
>> > Can you please let me know where i can download meerkat open source
>> > code?
>> > I would like to have look at the source files.
>> >
>> > --Deenadayalan
>> >
>> > On Thu, Jan 7, 2010 at 9:24 PM, Travis Athougies <ia...@gm...>
>> > wrote:
>> >>
>> >> Here is the link to join the meerkat-dist-devel mailing list:
>> >> https://lists.sourceforge.net/lists/listinfo/meerkat-dist-devel
>> >>
>> >> Let me give you a quick overview of meerkat. It's a
>> >> distributed/parallel programming environment. It's distributed in the
>> >> sense that it runs accross many different computers and its parallel
>> >> in that it attempts to run things concurrently.
>> >>
>> >> Meerkat is based loosely on the concept of actors, which are like
>> >> objects in OOP. Instead of calling an actor's method, though, you send
>> >> the actor a message. This means an actor can respond however it wants.
>> >> It can handle the message right then and there or it can delay
>> >> processing and process the message in a separate thread. The
>> >> possibilities are endless and actors have complete control over their
>> >> own internal data.
>> >>
>> >> In meerkat, a resource is how we implement the concept of actors. A
>> >> resource is essentially where actors live. A resource is identified by
>> >> a unique 64-bit id. The meerkat network can locate a resource anywhere
>> >> on the network, and can send a message to it. This is how meerkat can
>> >> be distributed, it stores its actors on different computers. Since the
>> >> actors are in charge of handling their own messages, computations tend
>> >> to take place accross many computers at once, instead of in a serial
>> >> fashion.
>> >>
>> >> A meerkat network is arranged in a tree. At the top is the brain node,
>> >> which manages the entire network. Underneath the brain are vertebrae
>> >> nodes. Underneath vertebrae nodes are more vertebrae nodes or regular
>> >> nodes. Together, the connections between nodes make up the backbone.
>> >>
>> >> So what's the point of meerkat? The meerkat library will provide
>> >> several programming abstractions which lend themselves naturally to
>> >> parallel computation. This will let programmers take advantage of
>> >> multicore chips, which are becoming the way of the future. In
>> >> addition, due to meerkat's lightweight pervasive threading model,
>> >> threads become more common, and therefore more parallel. More
>> >> importantly though, meerkat provides Software Transactional Memory,
>> >> which lifts the burden of mutial exclusion and locking from the
>> >> programmer. Without having to worry about synchronization, the
>> >> programmer is free to implement whatever program he wants. Meerkat's
>> >> distributed nature will allow the creation of rich internet
>> >> applications. A program written under meerkat could be used accross
>> >> the internet, thus allowing true software-as-a-service.
>> >>
>> >> We already have the resource framework, the backbone, an execution
>> >> layer (with JIT compiler), and a preliminary language compiler. More
>> >> work needs to be done on the resource layer, and the language layer
>> >> needs to get some more features (like list and dictionary support). A
>> >> standard library must be implemented. Software Transactional Memory
>> >> must be implemented. Actors must be given the ability to migrate
>> >> between nodes. Finally, we need to implement the parallel programming
>> >> abstractions I was talking about.
>> >>
>> >> As you can see, there's a lot to be done, and I think your skill set
>> >> for immensely benefit the language layer. I think you're in a great
>> >> position to become langauge layer maintainer. That's great, because we
>> >> really need one of those.
>> >>
>> >> If you have any questions, e-mail the list or me.
>> >>
>> >> Regards,
>> >> Travis.
>> >>
>> >> On Wed, Jan 6, 2010 at 7:32 PM, deenadayalan k <day...@gm...>
>> >> wrote:
>> >> > Hi,
>> >> >
>> >> > Can you please let me know the meerkat-dist-devel mail list?
>> >> > I am fine to join the live meeting on Sunday.
>> >> >
>> >> > Thanks & Regards
>> >> > Deenadayalan
>> >> >
>> >> > On Thu, Jan 7, 2010 at 5:49 AM, iammisc
>> >> > <ia...@us...>
>> >> > wrote:
>> >> >>
>> >> >> Message body follows:
>> >> >>
>> >> >> Great,
>> >> >>
>> >> >> We really need people who can take a look at the language
>> >> >> layer. Given
>> >> >> your experience with lex/yacc, you'll seem to make a great fit.
>> >> >>
>> >> >> To join, please join the meerkat-dist-devel mailing list.
>> >> >> Also, please
>> >> >> fetch a copy of the git repository and take a look at the
>> >> >> src/lang
>> >> >> directory. We already have a basic language (look at the
>> >> >> syntax in
>> >> >> test.mk in the repository). We need list and dictionary
>> >> >> support and
>> >> >> global variable resolution support.
>> >> >>
>> >> >> On sunday at 3:00PM PST (GMT +8), we usually have a live
>> >> >> meeting, I
>> >> >> announce it on the mailing list. If you can make it, please
>> >> >> do. If
>> >> >> this isn't a convenient time for you, let me know and we can
>> >> >> change
>> >> >> it.
>> >> >>
>> >> >> If you have any questions about the code, how something
>> >> >> works, etc.
>> >> >> Please e-mail the mailing list, we'll help you out.
>> >> >>
>> >> >> If you want any more information on how you can help out, don't
>> >> >> hesitate to e-mail the list.
>> >> >>
>> >> >> Thanks for your interest in the project. Once you join the list,
>> >> >> please send an email introducing yourself and I'll add you
>> >> >> to the
>> >> >> project. Once you start contributing code, I'll give you git
>> >> >> access
>> >> >> rights.
>> >> >>
>> >> >> Regards,
>> >> >> Travis.
>> >> >>
>> >> >> --
>> >> >> This message has been sent to you, a registered SourceForge.net
>> >> >> user,
>> >> >> by another site user, through the SourceForge.net site.  This
>> >> >> message
>> >> >> has been delivered to your SourceForge.net mail alias.  You may
>> >> >> reply
>> >> >> to this message using the "Reply" feature of your email client, or
>> >> >> using the messaging facility of SourceForge.net at:
>> >> >> https://sourceforge.net/sendmessage.php?touser=1338714
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Travis Athougies
>> >
>> >
>>
>>
>>
>> --
>> Travis Athougies
>
>



-- 
Travis Athougies

Re: [Meerkat-dist-devel] Meerkat-dist-devel Digest, Vol 3, Issue 2

[deenadayalan k <day...@gm...>]

Hi All,

*Some general questions:*

Does meerkat is has abbreviation? What is it means?
What is JIT compiler? Is this open source compiler? Where can i find the
source (its in meerkat?) for the JIT compiler?

Thanks,
Deenadayalan

On Sun, Jan 10, 2010 at 2:00 PM, <
mee...@li...> wrote:

> Send Meerkat-dist-devel mailing list submissions to
>        mee...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://lists.sourceforge.net/lists/listinfo/meerkat-dist-devel
> or, via email, send a message with subject or body 'help' to
>        mee...@li...
>
> You can reach the person managing the list at
>        mee...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Meerkat-dist-devel digest..."
>
>
> Today's Topics:
>
>   1. Developer Meeting (Travis Athougies)
>   2. Re: Developer Meeting (Jonathan Nguyen)
>   3. Re: Developer needed for Distributed Com (deenadayalan k)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 9 Jan 2010 12:13:07 -0800
> From: Travis Athougies <ia...@gm...>
> Subject: [Meerkat-dist-devel] Developer Meeting
> To: mee...@li...
> Message-ID:
>        <91f...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> This Sunday we will not have a live meeting.
>
> However, next Sunday we will. It would be great if all meerkat devs
> could be there.
>
> Please RSVP.
>
> Travis.
>
> --
> Travis Athougies
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 9 Jan 2010 13:11:53 -0800
> From: Jonathan Nguyen <jng...@gm...>
> Subject: Re: [Meerkat-dist-devel] Developer Meeting
> To: Travis Athougies <ia...@gm...>
> Cc: mee...@li...
> Message-ID:
>        <601...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hey all,
>
> I'll def. be there at the next meeting, assuming the scheduled time is
> semi-reasonable.
>
> To deenadayalan:
>
> Nice to have you on the team!  If you have any questions feel free to post
> on the mailing list.  Several of us have had a lot of other things to do
> recently (for myself I've just finished my first week at a new job in a new
> place) but I'm sure someone will get back to you quickly with what you want
> to know.
>
> Best,
> Jonathan
>
> On Sat, Jan 9, 2010 at 12:13 PM, Travis Athougies <ia...@gm...>
> wrote:
>
> > This Sunday we will not have a live meeting.
> >
> > However, next Sunday we will. It would be great if all meerkat devs
> > could be there.
> >
> > Please RSVP.
> >
> > Travis.
> >
> > --
> > Travis Athougies
> >
> >
> >
> ------------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Verizon Developer Community
> > Take advantage of Verizon's best-in-class app development support
> > A streamlined, 14 day to market process makes app distribution fast and
> > easy
> > Join now and get one step closer to millions of Verizon customers
> > http://p.sf.net/sfu/verizon-dev2dev
> > _______________________________________________
> > Meerkat-dist-devel mailing list
> > Mee...@li...
> > https://lists.sourceforge.net/lists/listinfo/meerkat-dist-devel
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 3
> Date: Sun, 10 Jan 2010 14:00:14 +0530
> From: deenadayalan k <day...@gm...>
> Subject: Re: [Meerkat-dist-devel] Developer needed for Distributed Com
> To: Travis Athougies <ia...@gm...>,
>        mee...@li...
> Message-ID:
>        <4df...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Travis,
>
> Thank for your support.
>
> I have already tried cloning of Meerkat source code using the below command
> but there was "Unable to connect a socket" error.
>
> CMD: git clone git://
> meerkat-dist.git.sourceforge.net/gitroot/meerkat-dist/meerkat-dist
>
> I am not sure the above error (time out error) is because of the server
> busy? or the requested resource (URL location) is not exist.
>
> Can somebody help me on this issue?
>
> Travis, after i download the source code successfully, What should i start
> looking in to in the source as starting point?
>
> Thanks & Regards
> Deenadayalan
>
>
>
> On Sun, Jan 10, 2010 at 1:42 AM, Travis Athougies <ia...@gm...>
> wrote:
>
> > Deenadayalan,
> >
> > Sorry for the late reply. I haven't had a chance to get on the
> > computer since our chat.
> >
> > Basically, once you have git installed, navigate to a directory where
> > you'd like to put the source files and run
> >
> > git clone git://
> > meerkat-dist.git.sourceforge.net/gitroot/meerkat-dist/meerkat-dist
> >
> > This should create directory called meerkat-dist where you can check
> > out the source files.
> >
> > We do have doxygen documentation, with an appropriate doxygen.cfg in
> > the doc directory. You run doxygen like doxygen doxygen.cfg and it
> > will produce documentation.
> >
> > I hope that helps.
> >
> > Just so you know, we won't be meeting this sunday, but definitely next
> > sunday.
> >
> > If you have any questions, forward them to the mailing list and me or
> > another dev will get back to you ASAP.
> >
> > Regards,
> > Travis.
> >
> > On Fri, Jan 8, 2010 at 9:45 AM, deenadayalan k <day...@gm...>
> > wrote:
> > > Hi Travis,
> > >
> > > Thanks for the information.
> > > Can you please let me know where i can download meerkat open source
> code?
> > > I would like to have look at the source files.
> > >
> > > --Deenadayalan
> > >
> > > On Thu, Jan 7, 2010 at 9:24 PM, Travis Athougies <ia...@gm...>
> > wrote:
> > >>
> > >> Here is the link to join the meerkat-dist-devel mailing list:
> > >> https://lists.sourceforge.net/lists/listinfo/meerkat-dist-devel
> > >>
> > >> Let me give you a quick overview of meerkat. It's a
> > >> distributed/parallel programming environment. It's distributed in the
> > >> sense that it runs accross many different computers and its parallel
> > >> in that it attempts to run things concurrently.
> > >>
> > >> Meerkat is based loosely on the concept of actors, which are like
> > >> objects in OOP. Instead of calling an actor's method, though, you send
> > >> the actor a message. This means an actor can respond however it wants.
> > >> It can handle the message right then and there or it can delay
> > >> processing and process the message in a separate thread. The
> > >> possibilities are endless and actors have complete control over their
> > >> own internal data.
> > >>
> > >> In meerkat, a resource is how we implement the concept of actors. A
> > >> resource is essentially where actors live. A resource is identified by
> > >> a unique 64-bit id. The meerkat network can locate a resource anywhere
> > >> on the network, and can send a message to it. This is how meerkat can
> > >> be distributed, it stores its actors on different computers. Since the
> > >> actors are in charge of handling their own messages, computations tend
> > >> to take place accross many computers at once, instead of in a serial
> > >> fashion.
> > >>
> > >> A meerkat network is arranged in a tree. At the top is the brain node,
> > >> which manages the entire network. Underneath the brain are vertebrae
> > >> nodes. Underneath vertebrae nodes are more vertebrae nodes or regular
> > >> nodes. Together, the connections between nodes make up the backbone.
> > >>
> > >> So what's the point of meerkat? The meerkat library will provide
> > >> several programming abstractions which lend themselves naturally to
> > >> parallel computation. This will let programmers take advantage of
> > >> multicore chips, which are becoming the way of the future. In
> > >> addition, due to meerkat's lightweight pervasive threading model,
> > >> threads become more common, and therefore more parallel. More
> > >> importantly though, meerkat provides Software Transactional Memory,
> > >> which lifts the burden of mutial exclusion and locking from the
> > >> programmer. Without having to worry about synchronization, the
> > >> programmer is free to implement whatever program he wants. Meerkat's
> > >> distributed nature will allow the creation of rich internet
> > >> applications. A program written under meerkat could be used accross
> > >> the internet, thus allowing true software-as-a-service.
> > >>
> > >> We already have the resource framework, the backbone, an execution
> > >> layer (with JIT compiler), and a preliminary language compiler. More
> > >> work needs to be done on the resource layer, and the language layer
> > >> needs to get some more features (like list and dictionary support). A
> > >> standard library must be implemented. Software Transactional Memory
> > >> must be implemented. Actors must be given the ability to migrate
> > >> between nodes. Finally, we need to implement the parallel programming
> > >> abstractions I was talking about.
> > >>
> > >> As you can see, there's a lot to be done, and I think your skill set
> > >> for immensely benefit the language layer. I think you're in a great
> > >> position to become langauge layer maintainer. That's great, because we
> > >> really need one of those.
> > >>
> > >> If you have any questions, e-mail the list or me.
> > >>
> > >> Regards,
> > >> Travis.
> > >>
> > >> On Wed, Jan 6, 2010 at 7:32 PM, deenadayalan k <day...@gm...>
> > >> wrote:
> > >> > Hi,
> > >> >
> > >> > Can you please let me know the meerkat-dist-devel mail list?
> > >> > I am fine to join the live meeting on Sunday.
> > >> >
> > >> > Thanks & Regards
> > >> > Deenadayalan
> > >> >
> > >> > On Thu, Jan 7, 2010 at 5:49 AM, iammisc <
> > ia...@us...>
> > >> > wrote:
> > >> >>
> > >> >> Message body follows:
> > >> >>
> > >> >> Great,
> > >> >>
> > >> >> We really need people who can take a look at the language
> > >> >> layer. Given
> > >> >> your experience with lex/yacc, you'll seem to make a great fit.
> > >> >>
> > >> >> To join, please join the meerkat-dist-devel mailing list.
> > >> >> Also, please
> > >> >> fetch a copy of the git repository and take a look at the
> > >> >> src/lang
> > >> >> directory. We already have a basic language (look at the
> > >> >> syntax in
> > >> >> test.mk in the repository). We need list and dictionary
> > >> >> support and
> > >> >> global variable resolution support.
> > >> >>
> > >> >> On sunday at 3:00PM PST (GMT +8), we usually have a live
> > >> >> meeting, I
> > >> >> announce it on the mailing list. If you can make it, please
> > >> >> do. If
> > >> >> this isn't a convenient time for you, let me know and we can
> > >> >> change
> > >> >> it.
> > >> >>
> > >> >> If you have any questions about the code, how something
> > >> >> works, etc.
> > >> >> Please e-mail the mailing list, we'll help you out.
> > >> >>
> > >> >> If you want any more information on how you can help out, don't
> > >> >> hesitate to e-mail the list.
> > >> >>
> > >> >> Thanks for your interest in the project. Once you join the list,
> > >> >> please send an email introducing yourself and I'll add you
> > >> >> to the
> > >> >> project. Once you start contributing code, I'll give you git
> > >> >> access
> > >> >> rights.
> > >> >>
> > >> >> Regards,
> > >> >> Travis.
> > >> >>
> > >> >> --
> > >> >> This message has been sent to you, a registered SourceForge.net
> user,
> > >> >> by another site user, through the SourceForge.net site.  This
> message
> > >> >> has been delivered to your SourceForge.net mail alias.  You may
> reply
> > >> >> to this message using the "Reply" feature of your email client, or
> > >> >> using the messaging facility of SourceForge.net at:
> > >> >> https://sourceforge.net/sendmessage.php?touser=1338714
> > >> >>
> > >> >
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Travis Athougies
> > >
> > >
> >
> >
> >
> > --
> > Travis Athougies
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
>
> ------------------------------
>
> _______________________________________________
> Meerkat-dist-devel mailing list
> Mee...@li...
> https://lists.sourceforge.net/lists/listinfo/meerkat-dist-devel
>
>
> End of Meerkat-dist-devel Digest, Vol 3, Issue 2
> ************************************************
>

Re: [Meerkat-dist-devel] Developer needed for Distributed Com

[deenadayalan k <day...@gm...>]

Hi Travis,

Thank for your support.

I have already tried cloning of Meerkat source code using the below command
but there was "Unable to connect a socket" error.

CMD: git clone git://
meerkat-dist.git.sourceforge.net/gitroot/meerkat-dist/meerkat-dist

I am not sure the above error (time out error) is because of the server
busy? or the requested resource (URL location) is not exist.

Can somebody help me on this issue?

Travis, after i download the source code successfully, What should i start
looking in to in the source as starting point?

Thanks & Regards
Deenadayalan



On Sun, Jan 10, 2010 at 1:42 AM, Travis Athougies <ia...@gm...> wrote:

> Deenadayalan,
>
> Sorry for the late reply. I haven't had a chance to get on the
> computer since our chat.
>
> Basically, once you have git installed, navigate to a directory where
> you'd like to put the source files and run
>
> git clone git://
> meerkat-dist.git.sourceforge.net/gitroot/meerkat-dist/meerkat-dist
>
> This should create directory called meerkat-dist where you can check
> out the source files.
>
> We do have doxygen documentation, with an appropriate doxygen.cfg in
> the doc directory. You run doxygen like doxygen doxygen.cfg and it
> will produce documentation.
>
> I hope that helps.
>
> Just so you know, we won't be meeting this sunday, but definitely next
> sunday.
>
> If you have any questions, forward them to the mailing list and me or
> another dev will get back to you ASAP.
>
> Regards,
> Travis.
>
> On Fri, Jan 8, 2010 at 9:45 AM, deenadayalan k <day...@gm...>
> wrote:
> > Hi Travis,
> >
> > Thanks for the information.
> > Can you please let me know where i can download meerkat open source code?
> > I would like to have look at the source files.
> >
> > --Deenadayalan
> >
> > On Thu, Jan 7, 2010 at 9:24 PM, Travis Athougies <ia...@gm...>
> wrote:
> >>
> >> Here is the link to join the meerkat-dist-devel mailing list:
> >> https://lists.sourceforge.net/lists/listinfo/meerkat-dist-devel
> >>
> >> Let me give you a quick overview of meerkat. It's a
> >> distributed/parallel programming environment. It's distributed in the
> >> sense that it runs accross many different computers and its parallel
> >> in that it attempts to run things concurrently.
> >>
> >> Meerkat is based loosely on the concept of actors, which are like
> >> objects in OOP. Instead of calling an actor's method, though, you send
> >> the actor a message. This means an actor can respond however it wants.
> >> It can handle the message right then and there or it can delay
> >> processing and process the message in a separate thread. The
> >> possibilities are endless and actors have complete control over their
> >> own internal data.
> >>
> >> In meerkat, a resource is how we implement the concept of actors. A
> >> resource is essentially where actors live. A resource is identified by
> >> a unique 64-bit id. The meerkat network can locate a resource anywhere
> >> on the network, and can send a message to it. This is how meerkat can
> >> be distributed, it stores its actors on different computers. Since the
> >> actors are in charge of handling their own messages, computations tend
> >> to take place accross many computers at once, instead of in a serial
> >> fashion.
> >>
> >> A meerkat network is arranged in a tree. At the top is the brain node,
> >> which manages the entire network. Underneath the brain are vertebrae
> >> nodes. Underneath vertebrae nodes are more vertebrae nodes or regular
> >> nodes. Together, the connections between nodes make up the backbone.
> >>
> >> So what's the point of meerkat? The meerkat library will provide
> >> several programming abstractions which lend themselves naturally to
> >> parallel computation. This will let programmers take advantage of
> >> multicore chips, which are becoming the way of the future. In
> >> addition, due to meerkat's lightweight pervasive threading model,
> >> threads become more common, and therefore more parallel. More
> >> importantly though, meerkat provides Software Transactional Memory,
> >> which lifts the burden of mutial exclusion and locking from the
> >> programmer. Without having to worry about synchronization, the
> >> programmer is free to implement whatever program he wants. Meerkat's
> >> distributed nature will allow the creation of rich internet
> >> applications. A program written under meerkat could be used accross
> >> the internet, thus allowing true software-as-a-service.
> >>
> >> We already have the resource framework, the backbone, an execution
> >> layer (with JIT compiler), and a preliminary language compiler. More
> >> work needs to be done on the resource layer, and the language layer
> >> needs to get some more features (like list and dictionary support). A
> >> standard library must be implemented. Software Transactional Memory
> >> must be implemented. Actors must be given the ability to migrate
> >> between nodes. Finally, we need to implement the parallel programming
> >> abstractions I was talking about.
> >>
> >> As you can see, there's a lot to be done, and I think your skill set
> >> for immensely benefit the language layer. I think you're in a great
> >> position to become langauge layer maintainer. That's great, because we
> >> really need one of those.
> >>
> >> If you have any questions, e-mail the list or me.
> >>
> >> Regards,
> >> Travis.
> >>
> >> On Wed, Jan 6, 2010 at 7:32 PM, deenadayalan k <day...@gm...>
> >> wrote:
> >> > Hi,
> >> >
> >> > Can you please let me know the meerkat-dist-devel mail list?
> >> > I am fine to join the live meeting on Sunday.
> >> >
> >> > Thanks & Regards
> >> > Deenadayalan
> >> >
> >> > On Thu, Jan 7, 2010 at 5:49 AM, iammisc <
> ia...@us...>
> >> > wrote:
> >> >>
> >> >> Message body follows:
> >> >>
> >> >> Great,
> >> >>
> >> >> We really need people who can take a look at the language
> >> >> layer. Given
> >> >> your experience with lex/yacc, you'll seem to make a great fit.
> >> >>
> >> >> To join, please join the meerkat-dist-devel mailing list.
> >> >> Also, please
> >> >> fetch a copy of the git repository and take a look at the
> >> >> src/lang
> >> >> directory. We already have a basic language (look at the
> >> >> syntax in
> >> >> test.mk in the repository). We need list and dictionary
> >> >> support and
> >> >> global variable resolution support.
> >> >>
> >> >> On sunday at 3:00PM PST (GMT +8), we usually have a live
> >> >> meeting, I
> >> >> announce it on the mailing list. If you can make it, please
> >> >> do. If
> >> >> this isn't a convenient time for you, let me know and we can
> >> >> change
> >> >> it.
> >> >>
> >> >> If you have any questions about the code, how something
> >> >> works, etc.
> >> >> Please e-mail the mailing list, we'll help you out.
> >> >>
> >> >> If you want any more information on how you can help out, don't
> >> >> hesitate to e-mail the list.
> >> >>
> >> >> Thanks for your interest in the project. Once you join the list,
> >> >> please send an email introducing yourself and I'll add you
> >> >> to the
> >> >> project. Once you start contributing code, I'll give you git
> >> >> access
> >> >> rights.
> >> >>
> >> >> Regards,
> >> >> Travis.
> >> >>
> >> >> --
> >> >> This message has been sent to you, a registered SourceForge.net user,
> >> >> by another site user, through the SourceForge.net site.  This message
> >> >> has been delivered to your SourceForge.net mail alias.  You may reply
> >> >> to this message using the "Reply" feature of your email client, or
> >> >> using the messaging facility of SourceForge.net at:
> >> >> https://sourceforge.net/sendmessage.php?touser=1338714
> >> >>
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Travis Athougies
> >
> >
>
>
>
> --
> Travis Athougies
>

Re: [Meerkat-dist-devel] Developer Meeting

[Jonathan N. <jng...@gm...>]

Hey all,

I'll def. be there at the next meeting, assuming the scheduled time is
semi-reasonable.

To deenadayalan:

Nice to have you on the team!  If you have any questions feel free to post
on the mailing list.  Several of us have had a lot of other things to do
recently (for myself I've just finished my first week at a new job in a new
place) but I'm sure someone will get back to you quickly with what you want
to know.

Best,
Jonathan

On Sat, Jan 9, 2010 at 12:13 PM, Travis Athougies <ia...@gm...> wrote:

> This Sunday we will not have a live meeting.
>
> However, next Sunday we will. It would be great if all meerkat devs
> could be there.
>
> Please RSVP.
>
> Travis.
>
> --
> Travis Athougies
>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Meerkat-dist-devel mailing list
> Mee...@li...
> https://lists.sourceforge.net/lists/listinfo/meerkat-dist-devel
>

[Meerkat-dist-devel] Developer Meeting

[Travis A. <ia...@gm...>]

This Sunday we will not have a live meeting.

However, next Sunday we will. It would be great if all meerkat devs
could be there.

Please RSVP.

Travis.

-- 
Travis Athougies

[Meerkat-dist-devel] Introduction

[deenadayalan k <day...@gm...>]

Hello All,

I am deenadayalan, I am new to meerkat, looking forward to work with you.

-Deenadayalan

Re: [Meerkat-dist-devel] Happy New Year

[Travis A. <ia...@gm...>]

John,

I didn't know you were still moving. I don't want to bother you too  
much but just a quick reply sometimes would be nice. I do hope you  
enjoy California. About the language layer, I'll try to put together  
some documentation for everyone to work with.

Everyone,

We'll be going back to our old system of weekly meetings once everyone  
tells me when they're available. Also, if everyone could respond to my  
emails, even if it's just a short reply that would be nice. I don't  
want to be talking to air.

Best wishes in the new year,
Travis.

On Dec 29, 2009, at 9:31 PM, Jonathan Nguyen <jng...@gm...>  
wrote:

> Hey all,
>
> I wish you all well as the comes to a close and the next  
> approaches.  With regards to the numerous topics posted by Travis:
>
> 1) Starting next Monday I will be on PST time.  Generally Monday  
> evenings, Saturday morning/noon and Sunday afternoons/evenings work  
> fine for me, though exact specifics will have to wait until I start  
> my new job.
>
> 2) I'm planning to start writing some unit tests using the testing  
> suite format already laid out.  I'm going to start with the mempool  
> functions and work from there.
>
> 3) I've been looking at the parser and language, in particular  
> trying to figure out syntax so that I could implement lists and  
> dictionaries.  However, this is a topic which I know next to nothing  
> about, so if someone wants to jump in I'd be more than willing to  
> follow your lead.
>
> Sorry for the long delay in replies.  Preparing to move to a  
> different state is a lot more time-consuming than I imagined.  Hope  
> you're all doing well and happy new year!
>
> Best,
> Jonathan Nguyen
>
> On Tue, Dec 29, 2009 at 5:49 PM, Travis Athougies  
> <ia...@gm...> wrote:
> Hey everyone,
>
> Happy New Year!
>
> Travis.
>
> PS, are you guys receiving my messages? I haven't gotten a response  
> from anyone.
>
> --
> Travis Athougies
>
> --- 
> --- 
> --- 
> ---------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast  
> and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Meerkat-dist-devel mailing list
> Mee...@li...
> https://lists.sourceforge.net/lists/listinfo/meerkat-dist-devel
>

Re: [Meerkat-dist-devel] Happy New Year

[Jonathan N. <jng...@gm...>]

Hey all,

I wish you all well as the comes to a close and the next approaches.  With
regards to the numerous topics posted by Travis:

1) Starting next Monday I will be on PST time.  Generally Monday evenings,
Saturday morning/noon and Sunday afternoons/evenings work fine for me,
though exact specifics will have to wait until I start my new job.

2) I'm planning to start writing some unit tests using the testing suite
format already laid out.  I'm going to start with the mempool functions and
work from there.

3) I've been looking at the parser and language, in particular trying to
figure out syntax so that I could implement lists and dictionaries.
However, this is a topic which I know next to nothing about, so if someone
wants to jump in I'd be more than willing to follow your lead.

Sorry for the long delay in replies.  Preparing to move to a different state
is a lot more time-consuming than I imagined.  Hope you're all doing well
and happy new year!

Best,
Jonathan Nguyen

On Tue, Dec 29, 2009 at 5:49 PM, Travis Athougies <ia...@gm...> wrote:

> Hey everyone,
>
> Happy New Year!
>
> Travis.
>
> PS, are you guys receiving my messages? I haven't gotten a response from
> anyone.
>
> --
> Travis Athougies
>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Meerkat-dist-devel mailing list
> Mee...@li...
> https://lists.sourceforge.net/lists/listinfo/meerkat-dist-devel
>

[Meerkat-dist-devel] Happy New Year

[Travis A. <ia...@gm...>]

Hey everyone,

Happy New Year!

Travis.

PS, are you guys receiving my messages? I haven't gotten a response from anyone.

-- 
Travis Athougies

[Meerkat-dist-devel] Time zones

[Travis A. <ia...@gm...>]

Hey all,

So we need a new meeting time so we can all chat together and in order
for that to happen, I'm going to need to know everyone's timezone and
when they are available on Friday, Saturday, Sunday, and Monday.
Please reply with this information.

Travis.

-- 
Travis Athougies

[Meerkat-dist-devel] Another task

[Travis A. <ia...@gm...>]

Hey all,

Here's another task anyone can do. The resource.c file is getting too
big, it would be really nice if it could be split of into a resource
folder and then source files with more appropriate names could contain
the implementations of the functions currently in resource.c

Travis.

-- 
Travis Athougies

[Meerkat-dist-devel] Simple tasks anyone can complete

[Travis A. <ia...@gm...>]

Hey meerkat devs,

Here is a list of outstanding tasks anyone can do:

1. Refactor unit tests. Due to time, I haven't really written much of
these and we really need them
2. Create a programming manual and meerkat language documentation. If
you'd like to do this, check out test.mk for a quick syntactic
overview.
3. Design and implement the actor type object. To complete this task,
you'd propose a system to create actor instances based on an actor
definition. We really need this to go forward
4. Begin work on a standard library. You'd have to first design and
document(not fully) and begin implementation of a standard library
5. Update the meerkat website. We really need  someone to be in charge
of communication who can update the website, write blogs, etc

if you'd like to work on any of these, make sure to let everyone else know.

We will not be having a meeting tomorrow. Have fun at this time of
year. We will have a new meeting time in the new year and I will
announce it before Jan 3rd.

Regards,
Travis

-- 
Travis Athougies

[Meerkat-dist-devel] Merry Christmas!

[Travis A. <ia...@gm...>]

Just wanted to wish you all a merry christmas or whatever you  
celebrate this time of year. Take a break and spend some quality time  
with those you care about.

Regards as always,
Travis.

[Meerkat-dist-devel] Language subsystem

[Travis A. <ia...@gm...>]

Hey everyone,

Just a quick report on the current state of the language system.
Here's what's lacking:

* Sending messages to objects. In meerkat, we don't call functions on
objects (or actors or resources), we send messages, much like
Objective-C.
* Lists and dictionaries. We need a syntax for lists and dictionaries.

If anyone wants to start work on these, the framework is largely in place.

I'm going to explain to you a little of how message sending works.

For sending messages, consider the message specifier
"System.Console.Write". System.Console is the receiver object. Write
is the message. The System object exists under the global namespace
and the Console actor exists under the System object. Basically, to
get your hands on the System.Console actor, you'd have to find the
message numbers for both System and Console. These can be retrieved
using the NameToMessage function. Then you'd use Object_GetAttr on
g_global_ns with the returned value of NameToMessage('System') as the
key. Now you'll do NameToMessage('Console') and use Object_GetAttr on
the returned object to get the console object. Finally you'll use
NameToMessage on Write and use SendMsg to send the write message to
the console object.  The purpose of using NameToMessage is that is
maps strings to integers. Integers are easier to embed into bytecode
and they take up less space. It is also easier to use integers as keys
than strings. NameToMessage is a one-to-one mapping, each string
identifier will have exactly one integer equivalent and these integers
will remain the same throughout the execution of a program. If
NameToMessage is called with a new name, it will allocate a new
message number automatically.

In the bytecode, this can be handled using the LOAD_NS_OP and
GETATTR_OP and SEND_OP. As said, NameToMessage returns constants, so
we can resolve names at compile-time. This speeds up the execution
time because we don't have to do messy string handling.

As for lists and dictionaries, syntax needs to be formalized. The
lexer and parser need to be updated as well. New AST node types will
have to be added. These new types will have to be added to the
compiler. Finally, new opcodes will have to be added. For example,
these could be NEWLIST_OP, NEWDICT_OP, etc.

If any of you are interested in implementing these, let me know and
I'll help you. The more independent projects you take on, the more
familiar you'll get with the meerkat code.

Travis.

-- 
Travis Athougies

Re: [Meerkat-dist-devel] Tomorrow

[Travis A. <ia...@gm...>]

Rohit,

No problem. I don't expect you to get up early just to come. The
minutes of all our meetings are posted on the wiki
(http://sourceforge.net/apps/trac/meerkat-dist/wiki/MeerkatDeveloperCentral).
Scroll down to developer meeting minutes.

Regards,
Travis.

On Sun, Dec 20, 2009 at 9:55 AM, Rohit Shekhar <roh...@gm...> wrote:
>
> Hi Travis,
>     3.00 PM PST is 4:30AM here as per IST. I was looking forward
> to attend it but its bit awkward time for me to plan for at short notice. I
> will go through the documents and also go try to understand initial code.
>     Will post my issues on this forum. Meanwhile request one of you to send
> minutes of the meeting.
> Regards,
> Rohit
> On Sat, Dec 19, 2009 at 6:45 PM, Travis Athougies <ia...@gm...> wrote:
>>
>> We've had an onslaught of new developers on our team, which is good
>> for meerkat, but which makes it a little harder to keep everyone
>> up-to-date.
>>
>> Just for everyone's information, tomorrow at 3:00PM Pacific Standard
>> Time (GMT +8) on Sunday (which for some of you might be Monday), we
>> will be having a live chat developer conference at #meerkat-dist on
>> irc.freenode.net.
>>
>> I encourage everyone to be there, the new devs moreso than the old
>> ones. It'll last about an hour, but if any of you could stay on, I
>> plan on making lots of headway on code.
>>
>> Travis.
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Verizon Developer Community
>> Take advantage of Verizon's best-in-class app development support
>> A streamlined, 14 day to market process makes app distribution fast and
>> easy
>> Join now and get one step closer to millions of Verizon customers
>> http://p.sf.net/sfu/verizon-dev2dev
>> _______________________________________________
>> Meerkat-dist-devel mailing list
>> Mee...@li...
>> https://lists.sourceforge.net/lists/listinfo/meerkat-dist-devel
>
>
>
> --
>
>
> First they ignore you, then they laugh at you, then they fight you, then you
> win
> -Gandhi
>



-- 
Travis Athougies

Re: [Meerkat-dist-devel] Tomorrow

[Rohit S. <roh...@gm...>]

Hi Travis,

    3.00 PM PST is 4:30AM here as per IST. I was looking forward
to attend it but its bit awkward time for me to plan for at short notice. I
will go through the documents and also go try to understand initial code.
    Will post my issues on this forum. Meanwhile request one of you to send
minutes of the meeting.

Regards,
Rohit

On Sat, Dec 19, 2009 at 6:45 PM, Travis Athougies <ia...@gm...> wrote:

> We've had an onslaught of new developers on our team, which is good
> for meerkat, but which makes it a little harder to keep everyone
> up-to-date.
>
> Just for everyone's information, tomorrow at 3:00PM Pacific Standard
> Time (GMT +8) on Sunday (which for some of you might be Monday), we
> will be having a live chat developer conference at #meerkat-dist on
> irc.freenode.net.
>
> I encourage everyone to be there, the new devs moreso than the old
> ones. It'll last about an hour, but if any of you could stay on, I
> plan on making lots of headway on code.
>
> Travis.
>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Meerkat-dist-devel mailing list
> Mee...@li...
> https://lists.sourceforge.net/lists/listinfo/meerkat-dist-devel
>



-- 


First they ignore you, then they laugh at you, then they fight you, then you
win
-Gandhi

[Meerkat-dist-devel] Tomorrow

[Travis A. <ia...@gm...>]

We've had an onslaught of new developers on our team, which is good
for meerkat, but which makes it a little harder to keep everyone
up-to-date.

Just for everyone's information, tomorrow at 3:00PM Pacific Standard
Time (GMT +8) on Sunday (which for some of you might be Monday), we
will be having a live chat developer conference at #meerkat-dist on
irc.freenode.net.

I encourage everyone to be there, the new devs moreso than the old
ones. It'll last about an hour, but if any of you could stay on, I
plan on making lots of headway on code.

Travis.