hi glynn:
i spent a little time yesterday trying to get openstep to compile on a fresh install of cygwin; no luck yet, as there's some unrecognized chmod option that kills the make install. i'll try again this afternoon and let you know how it goes.
andy
Glynn Clements wrote:
andy agena wrote:
i did a quick look around the gcc page, and obj-C is supported
(couldn't find which version it start with).
I'm aware that gcc supports it; however:
a) Most distributions relegate it to a separate package, and not many
people install the objective-C component.
b) I have no idea how reliable it is on minority platforms (i.e. other
than Linux and Mac). Even gcc's C++ support has tended to be flaky on
commercial Unices, which doesn't bode well for objective-C.
c) What's the state of Windows support?
as for learning obj-C,
there's been this claim on the osx developers' pages that if one knows
C, one can learn obj-C in an afternoon...
Even if people can learn it, will they? Or will they turn away as soon
as they realise that it's in a language they don't currently
understand?
Also, it isn't just a matter of being able to write code. We need to
be able to handle bug reports (which means understanding the awkward
cases, not just typical usage). Can you call objective-C code from C?
What about binary compatibility? E.g. C++ is very "fragile" in this
area; note how many GDAL problems are C++ related. Will we have
similar problems with objective-C?
nisn't it possible to have GRASS for windows without cygwin.
i.e., a fereware GIS for windows.
( native)
On Fri, 18 Oct 2002, andy agena wrote:
hi glynn:
i spent a little time yesterday trying to get openstep to compile on a
fresh install of cygwin; no luck yet, as there's some unrecognized
chmod option that kills the make install. i'll try again this
afternoon and let you know how it goes.
andy
Glynn Clements wrote:
> andy agena wrote:
>
>> i did a quick look around the gcc page, and obj-C is supported
>> (couldn't find which version it start with).
>
> I'm aware that gcc supports it; however:
>
> a) Most distributions relegate it to a separate package, and not many
> people install the objective-C component.
>
> b) I have no idea how reliable it is on minority platforms (i.e. other
> than Linux and Mac). Even gcc's C++ support has tended to be flaky on
> commercial Unices, which doesn't bode well for objective-C.
>
> c) What's the state of Windows support?
>
>> as for learning obj-C,
>> there's been this claim on the osx developers' pages that if one knows
>> C, one can learn obj-C in an afternoon...
>
> Even if people can learn it, will they? Or will they turn away as soon
> as they realise that it's in a language they don't currently
> understand?
>
> Also, it isn't just a matter of being able to write code. We need to
> be able to handle bug reports (which means understanding the awkward
> cases, not just typical usage). Can you call objective-C code from C?
> What about binary compatibility? E.g. C++ is very "fragile" in this
> area; note how many GDAL problems are C++ related. Will we have
> similar problems with objective-C?
_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5
hi sharma:
i did install cygwin; i'm just having difficulties compiling openstep on top of it.
andy
On Friday, October 18, 2002, at 09:55 AM, Sharma Ojaswa wrote:
nisn't it possible to have GRASS for windows without cygwin.
i.e., a fereware GIS for windows.
( native)
On Fri, 18 Oct 2002, andy agena wrote:
hi glynn:
i spent a little time yesterday trying to get openstep to compile on a
fresh install of cygwin; no luck yet, as there's some unrecognized
chmod option that kills the make install. i'll try again this
afternoon and let you know how it goes.
andy
Glynn Clements wrote:
andy agena wrote:
i did a quick look around the gcc page, and obj-C is supported
(couldn't find which version it start with).
I'm aware that gcc supports it; however:
a) Most distributions relegate it to a separate package, and not many
people install the objective-C component.
b) I have no idea how reliable it is on minority platforms (i.e. other
than Linux and Mac). Even gcc's C++ support has tended to be flaky on
commercial Unices, which doesn't bode well for objective-C.
c) What's the state of Windows support?
as for learning obj-C,
there's been this claim on the osx developers' pages that if one knows
C, one can learn obj-C in an afternoon...
Even if people can learn it, will they? Or will they turn away as soon
as they realise that it's in a language they don't currently
understand?
Also, it isn't just a matter of being able to write code. We need to
be able to handle bug reports (which means understanding the awkward
cases, not just typical usage). Can you call objective-C code from C?
What about binary compatibility? E.g. C++ is very "fragile" in this
area; note how many GDAL problems are C++ related. Will we have
similar problems with objective-C?
_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5
Sharma Ojaswa wrote:
nisn't it possible to have GRASS for windows without cygwin.
i.e., a fereware GIS for windows.
At present, no; there are a substantial number of calls to Unix API
functions. However, it wouldn't be particularly difficult to create a
native Windows version.
Most of the Unix API calls are gratuitous (e.g. using Unix
I/O instead of ANSI I/O); those could be removed fairly easily.
There are quite a few calls to system() which invoke Unix commands.
Again, a fair number of those are gratuitous (e.g. using
system("rm ...") instead of remove()).
There are a small number of less trivial dependencies; e.g. a number
of programs use fork() for one reason or another. Most of the
non-trivial work in producing a native Windows version would be in
creating a set of process management primitives which could be
implemented on both Unix and Windows.
--
Glynn Clements <glynn.clements@virgin.net>