There's a post over on gmane about MCL possibly going open source:
"MCL 5.2 will soon be released as on open source project.
It is Unicode based. It is PPC only.
Perhaps this release will enable some combination of financial
and engingeering resources to provide an Intel implementation.
Alice"
http://article.gmane.org/gmane.lisp.mcl.general/2500
On Oct 12, 11:26 am, ············@gmail.com wrote:
> There's a post over on gmane about MCL possibly going open source:
>
> "MCL 5.2 will soon be released as on open source project.
> It is Unicode based. It is PPC only. ...
Aren't all new Macs Intel based?
In article <························@e9g2000prf.googlegroups.com>,
Brian Adkins <···········@gmail.com> wrote:
> On Oct 12, 11:26 am, ············@gmail.com wrote:
> > There's a post over on gmane about MCL possibly going open source:
> >
> > "MCL 5.2 will soon be released as on open source project.
> > It is Unicode based. It is PPC only. ...
>
> Aren't all new Macs Intel based?
Yes.
(If you count OSX based iPhones and iPod touch. Then, no.
Those are ARM-based.)
On Oct 12, 11:26 am, ············@gmail.com wrote:
> Perhaps this release will enable some combination of financial
> and engingeering resources to provide an Intel implementation.
So they're hoping that by open-sourcing MCL, they will instantly gain
an army of high-quality, unpaid, volunteers willing to dive right into
10+ year old legacy code built on legacy APIs, and implement all the
missing features?
Classic mistake.
Slava
On Oct 12, 9:15 pm, Slava Pestov <·····@jedit.org> wrote:
> So they're hoping that by open-sourcing MCL, they will instantly gain
> an army of high-quality, unpaid, volunteers willing to dive right into
> 10+ year old legacy code built on legacy APIs, and implement all the
> missing features?
>
Even If it's just a platoon, I won't be objecting.
In article <························@q5g2000prf.googlegroups.com>,
Slava Pestov <·····@jedit.org> wrote:
> On Oct 12, 11:26 am, ············@gmail.com wrote:
> > Perhaps this release will enable some combination of financial
> > and engingeering resources to provide an Intel implementation.
>
> So they're hoping that by open-sourcing MCL, they will instantly gain
> an army of high-quality, unpaid, volunteers willing to dive right into
> 10+ year old legacy code built on legacy APIs, and implement all the
> missing features?
are they?
>
> Classic mistake.
>
I guess you don't know what you are talking about - why post then?
> Slava