Missing semicolon after do

[mattunlv]

import std.io;

public proc void main(string args[]) { int a; do { break; } while (true) a = 9;

}

[cabelshrestha]

Fixed. But there could be more stuff related to semicolon issue as I recently changed the StringTemplate default delim. I'll run more tests. Let me know if you find any other.

[cabelshrestha]

Found a couple more. I'm fixing it right now. Wait for about an hour before you do anything.

[mattunlv]

I don’t know if I ever wanna do anything again ;-)

ok - I will wait

Matt

On Dec 1, 2016, at 4:44 PM, Cabel Shrestha notifications@github.com wrote:

Found a couple more. I'm fixing it right now. Wait for about an hour before you do anything.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/mattunlv/ProcessJ/issues/13#issuecomment-264340945, or mute the thread https://github.com/notifications/unsubscribe-auth/AAFQHaZvLd-bx2FAY8PUY9q-eNYUen8Zks5rD2nigaJpZM4LCCey.

---

• Jan 'Matt' Pedersen, Ph.D. Office: TBE B384 *
• Associate Professor E-mail: matt.pedersen@unlv.edu mailto:matt.pedersen@unlv.edu *
• School of Computer Science Phone : +1 (702) 895-2557 *
• University of Nevada at Las Vegas Fax : +1 (702) 895-2639 *
• Las Vegas, NV, 89154-4019 *
• *
• Home Page: http://www.egr.unlv.edu/~matt http://www.cs.unlv.edu/~matt *
• Note: This email is meant for the original recipients only - that means *
• that you may NOT forward it to anyone nor include it as part of a reply *
• to me if that reply involves recipients not part of the original email. *

  ---

[cabelshrestha]

Never say never. 😛

[cabelshrestha]

Ok, committed a couple of fixes. There are more to be fixed...which won't be done tonight. Hoping you'll have what you need for the time being.

[mattunlv]

Yes thank you :-)

Sent from my iPhone, which now again is better than Kelvin's.

On Dec 1, 2016, at 19:21, Cabel Shrestha notifications@github.com wrote:

Ok, committed a couple of fixes. There are more to be fixed...which won't be done tonight. Hoping you'll have what you need for the time being.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[mattunlv]

So I was thinking about this:

chan[] chans = new chan[100];

chans.read <---- that is currently illegal.

However, that is just a type checking trick

chans is of type Array(Chan), but chans.read is of type Array(ChannelEndRead)

so I just need to fiddle around with building a new type but you STILL need to pass in the same cause

chans and chans.read and chans.write for YOU is the same as channels in the runtime are not by end but by the entire channel.

;-) that makes that easier

Matt

On Dec 1, 2016, at 7:21 PM, Cabel Shrestha wrote:

Reopened #13.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[cabelshrestha]

closing this one out and moving your last comment related to chan array endtype access to appropriate issue.