Absolutely. Allowing the code to compile and printing warnings when a
missing method is called would be very helpful.
Dne 13. září 2013 2:01:01 Gregory Casamento <[email protected]> napsal:
One of the ways I approached the Xcode library implementation (a library in
GNUstep which interprets xcodeproj files and builds them) was to analyze
what was missing and generate skeletons for those things that were not
present. I'm wondering if a similar approach might not be practical here
as well.
On Thu, Sep 12, 2013 at 2:03 PM, Muhammad Hussein Nasrollahpour <
[email protected] <javascript:_e({}, 'cvml',
'[email protected]');>> wrote:
>
> On Sep 12, 2013, at 10:52 AM, Doc O'Leary <
> [email protected] <javascript:_e({}, 'cvml',
> '[email protected]');>> wrote:
>
> > In article
<[email protected]<javascript:_e({},
'cvml',
> '[email protected]');>>,
> > Doug Simons <[email protected] <javascript:_e({}, 'cvml',
> '[email protected]');>> wrote:
> >
> >> On Sep 12, 2013, at 4:03 AM, David Chisnall wrote:
> >>
> >>> We could almost certainly provide them with an automated tool that
> they can
> >>> run on their codebase that would give them a pretty clear idea of the
> OS X
> >>> APIs that they use. Actually, providing such a tool with the ability
> to
> >>> produce a report against the current version of GNUstep showing what is
> >>> missing would be very helpful for a lot of projects.
> >>
> >> If such a tool could be produced, I think it would be a tremendous
> asset for
> >> GNUstep. I suspect there are plenty of developers of applications for
> OS X
> >> who would be interested in porting to GNUstep but are put off by the
> daunting
> >> task involved in making the effort, especially knowing that there are
> almost
> >> certainly some things missing but not knowing how extensive those gaps
> might
> >> be.
> >
> > I disagree. What you want to do is engage developers as much as
> > possible with as little effort as possible. Don't give them a tool that
> > has them holding GNUstep at arms length like a stinky diaper. Instead,
> > you have to make the porting effort less daunting from the get-go. Or,
> > rather, make the effort in line with the reward. Like Graham said, many
> > developers won't be bothered with even zero effort mainly, I think,
> > because they expect zero reward.
>
> Completely agree. We shouldn't engage developers in a lot of effort.
>
>
> _______________________________________________
> Discuss-gnustep mailing list
> [email protected] <javascript:_e({}, 'cvml',
> '[email protected]');>
> https://lists.gnu.org/mailman/listinfo/discuss-gnustep
>
>
--
Gregory Casamento
Open Logic Corporation, Principal Consultant
yahoo/skype: greg_casamento, aol: gjcasa
(240)274-9630 (Cell)
http://www.gnustep.org
http://heronsperch.blogspot.com
--
Gregory Casamento
Open Logic Corporation, Principal Consultant
yahoo/skype: greg_casamento, aol: gjcasa
(240)274-9630 (Cell)
http://www.gnustep.org
http://heronsperch.blogspot.com
_______________________________________________
Gnustep-dev mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/gnustep-dev
