Boo Programming Language Google Group

Re: A bribe to Fully Support AutoComplete/Intellisense & Debugger?

mwaynewal...@gmail.com (Wayne Walter) — Wed, 11 Nov 2009 00:38:35 UT

Well, I will only consider a fixed price agreement and never the full cost
of a developer.
My feeling is others need and can benefit from the same features so,
somehow,
the cost can be shared.

In fact, Justin you said you would appreciate those features. Since you will
use
the resulting work wait kind of flat fee would chart to make it happen?

(nessun oggetto)

freel...@gmail.com (Gpanz) — Tue, 10 Nov 2009 21:25:04 UT

Re: Operator '<=' cannot be used with a left hand side of type 'double' and a right hand side of type 'TickZoom.Api.Elapsed'

wpwoo...@gmail.com (Bill Wood) — Tue, 10 Nov 2009 20:28:41 UT

Rodrigo, it would be nice to add implicit casting too!

- Bill

On Nov 9, 10:10 am, "Rodrigo B. de Oliveira" <rodrigobam...@gmail.com>
wrote:

Re: Distinguishing between Generic and non-generic type with same name?

cneuw...@gmail.com (cneuwirt) — Tue, 10 Nov 2009 19:47:44 UT

Thats what I thought it was, but it doesn't seem to work with version
0.9.1
I guess it requires 0.9.2

thanks

Re: Distinguishing between Generic and non-generic type with same name?

justin.m.ch...@gmail.com (Justin Chase) — Tue, 10 Nov 2009 19:32:31 UT

I didn't know this one either but I was just playing around and this seems
to work:

class Foo:
pass
class Foo[of T]:
pass
print typeof(Foo)
print typeof(Foo[of *])

+1 intutiveness

--
Justin Chase
[link]

Distinguishing between Generic and non-generic type with same name?

cneuw...@gmail.com (cneuwirt) — Tue, 10 Nov 2009 19:19:45 UT

If I have a generic class SomeClass<T> and a non-generic class called
SomeClass, how can I distinguish them in BOO?

If I specify SomeClass, I'll get the non-generic version. How can I
identify the open-generic version? I have tried SomeClass[of] but
that is not legal

thanks,
craig

Re: A bribe to Fully Support AutoComplete/Intellisense & Debugger?

nrst...@gmail.com (Nathan Stott) — Tue, 10 Nov 2009 15:18:35 UT

I hope someone takes your bribe. I'd love to have these features as well.

If you want to pay regular contracting rates, my company will take on the
project. I don't have the free-time to devote to it outside of company
hours.

Re: A bribe to Fully Support AutoComplete/Intellisense & Debugger?

mwaynewal...@gmail.com (Wayne Walter) — Mon, 09 Nov 2009 20:20:06 UT

What I mean is money. Since the developers will likely do this work
eventually
anyway and benefit in various ways, a bribe for open source means a
significant
token of money to raise priority.

It doesn't really compensate for the effort like contracting or hiring a
programmer
but it certainly tells us the customer is serious and gives us a valid

Re: A bribe to Fully Support AutoComplete/Intellisense & Debugger?

justin.m.ch...@gmail.com (Justin Chase) — Mon, 09 Nov 2009 19:34:49 UT

Can you define "bribe" more specifically? :)

--
Justin Chase
[link]

A bribe to Fully Support AutoComplete/Intellisense & Debugger?

mwaynewal...@gmail.com (Wayne Walter) — Mon, 09 Nov 2009 18:49:14 UT

What's the status or plans to make the AutoComplete/Intellisense
full featured in both Boo Addin for #D and BoolangPro for VS?
Please answer for either or both.
Hey, could we bribe one of you recognized Boo language developers
to work on this as a priority? Maybe Daniel who did the Boo Addin
for #D to begin with?

Re: Operator '<=' cannot be used with a left hand side of type 'double' and a right hand side of type 'TickZoom.Api.Elapsed'

gbena...@gmail.com (gbenatti@gmail.com) — Mon, 09 Nov 2009 16:26:43 UT

I Agree ;) + 1
On Mon, Nov 9, 2009 at 2:24 PM, Daniel Grunwald

Re: Operator '<=' cannot be used with a left hand side of type 'double' and a right hand side of type 'TickZoom.Api.Elapsed'

dan...@danielgrunwald.de (Daniel Grunwald) — Mon, 09 Nov 2009 16:24:21 UT

"as" already has two meanings:
x as object = SomeClass()
a as string = x # InvalidCastException
b = x as string # null
c as int = x # InvalidCastException
d = x as int # Compiler error
Adding a third meaning in the case 'd' would be even more confusing.
I like the idea of "cast" and "cast?"; then 'as' would unambiguously

Re: Operator '<=' cannot be used with a left hand side of type 'double' and a right hand side of type 'TickZoom.Api.Elapsed'

gbena...@gmail.com (gbenatti@gmail.com) — Mon, 09 Nov 2009 16:03:38 UT

Hummm.. Well, i don't really see a problem in overloading the meaning
of as, in the case of value types.
But, i like the idea of this cast and cast?, and if the dual meaning
of as is not desirable, i would be glad of have this cast forms

On Mon, Nov 9, 2009 at 12:10 PM, Rodrigo B. de Oliveira

Re: Operator '<=' cannot be used with a left hand side of type 'double' and a right hand side of type 'TickZoom.Api.Elapsed'

rodrigobam...@gmail.com (Rodrigo B. de Oliveira) — Mon, 09 Nov 2009 14:10:34 UT

'as' is a try cast. It returns null to signal failure.
It could return a nullable value type version for value types but
that's not where I intend to go with it.
I've been thinking for some time now in unifying casts and nullable
casts and about removing the overloaded meaning of the 'as' keyword.
Regular Casts (throw upon failure)

Re: Operator '<=' cannot be used with a left hand side of type 'double' and a right hand side of type 'TickZoom.Api.Elapsed'

mwaynewal...@gmail.com (Wayne Walter) — Mon, 09 Nov 2009 13:54:10 UT

Understood. Only, there may be value to using different syntax even if it's
not the
ugly cast( double, value).

Why?

Well, as is very specific functionality more than a cast. It will make the
reference
null of it's not castable. With a valuetable, null is impossble. So what
value would
you assign if it's not castable?