Hi,

"Sean L. Palmer" <seanpalmer@earthlink.net> wrote in message news:afek1t$pev$1@digitaldaemon.com...
> You know what?   SCREW OS/390.

You might not care about portability, but it is a primary concern to me. At work, we develop software to whatever platforms the customers are using, and we don't expect the customers to change platform to whatever is supported by our tools. Instead we have to select our tools, such as compilers and languages, to fit the customers needs. OS/390 is big in big businesses such as the financial sector, and to address such markeds, you have to support it. C/C++ supports wierd platforms like this very fine, and so should any viable successor.

Regards,
Martin M. Pedersen

"Martin M. Pedersen" <mmp@www.moeller-pedersen.dk> wrote in message news:aff9o4$1n7m$1@digitaldaemon.com...
> Hi,
>
> "Sean L. Palmer" <seanpalmer@earthlink.net> wrote in message news:afek1t$pev$1@digitaldaemon.com...
> > You know what?   SCREW OS/390.
>
> You might not care about portability, but it is a primary concern to me.
At
> work, we develop software to whatever platforms the customers are using,
and
> we don't expect the customers to change platform to whatever is supported
by
> our tools. Instead we have to select our tools, such as compilers and languages, to fit the customers needs. OS/390 is big in big businesses
such
> as the financial sector, and to address such markeds, you have to support it. C/C++ supports wierd platforms like this very fine, and so should any viable successor.
>
> Regards,
> Martin M. Pedersen
>
>


Still, C/C++ also allow pathnames in
includes, so what's your point?

If you need portability, just don't
use pathnames in imports. Me personally
I couldn't care less about OS/390...

--
Stijn
OddesE_XYZ@hotmail.com
http://OddesE.cjb.net
_________________________________________________
Remove _XYZ from my address when replying by mail

"Sean L. Palmer" <seanpalmer@earthlink.net> wrote in message news:afek1t$pev$1@digitaldaemon.com...
> You know what?   SCREW OS/390.
>
> Sean
>


I tend to agree.
If an OS you want to target doesn't
support directories, then simply
don't use them in your source.

Portability is good, but it shouldn't
be enforced. If I want to write platform
dependant code, then please let me.

--
Stijn
OddesE_XYZ@hotmail.com
http://OddesE.cjb.net
_________________________________________________
Remove _XYZ from my address when replying by mail

"Martin M. Pedersen" <mmp@www.moeller-pedersen.dk> wrote in message news:aff9o4$1n7m$1@digitaldaemon.com...

> "Sean L. Palmer" <seanpalmer@earthlink.net> wrote in message news:afek1t$pev$1@digitaldaemon.com...
> > You know what?   SCREW OS/390.
>
> You might not care about portability, but it is a primary concern to me.
At
> work, we develop software to whatever platforms the customers are using,
and
> we don't expect the customers to change platform to whatever is supported
by
> our tools. Instead we have to select our tools, such as compilers and languages, to fit the customers needs. OS/390 is big in big businesses
such
> as the financial sector, and to address such markeds, you have to support it. C/C++ supports wierd platforms like this very fine, and so should any viable successor.

   Can't you cross-compile from a development system that's nicer than that?
Do you really need to compile in the OS/360 itself?

Salutaciones,
                         JCAB

I'm ok with forward slashes, they're the "de facto" standard path separator for every OS except windoze.

Sean

"C.R.Chafer" <blackmarlin@nospam.asean-mail.com> wrote in message news:afeolg$tnn$1@digitaldaemon.com...
> Sean L. Palmer wrote:
>
> > Global search and replace is commonly available.
> >
> > Seriously this kind of change is rare and isn't that hard to accomplish.
> >
> > I'd rather support easier compilation for *small* apps (D will have to
be
> > a
> > grassroots effort at first).  I really don't mind the path being in the
> > source files, in fact I think it belongs there.
> >
> > Relative paths would also reduce problems with more than one library having a module with the same name.
> >
> > Imagine:
> >
> > import engine\math;
> > import phobos\math;
> > import common\math;
> > import utility\extras\mystuff\math;
> >
> > Sean
>
> Agreed, but please please please do not use back slashes (use forward slashes instead, or colons).  The backslash key on each of my 6 keyboard
is
> in a different place - and on one it is completely absent.
>
> C 2002/6/27

Any OS that doesn't support directories is going to have serious problematic issues as a development platform.  It's ok for the target platform not to support directories.  Some embedded systems may not even have an OS or filesystem at all..  But the development platform *MUST* support directories.  This is 2002 dammit.

Sean

"Martin M. Pedersen" <mmp@www.moeller-pedersen.dk> wrote in message news:aff9o4$1n7m$1@digitaldaemon.com...
> Hi,
>
> "Sean L. Palmer" <seanpalmer@earthlink.net> wrote in message news:afek1t$pev$1@digitaldaemon.com...
> > You know what?   SCREW OS/390.
>
> You might not care about portability, but it is a primary concern to me.
At
> work, we develop software to whatever platforms the customers are using,
and
> we don't expect the customers to change platform to whatever is supported
by
> our tools. Instead we have to select our tools, such as compilers and languages, to fit the customers needs. OS/390 is big in big businesses
such
> as the financial sector, and to address such markeds, you have to support it. C/C++ supports wierd platforms like this very fine, and so should any viable successor.
>
> Regards,
> Martin M. Pedersen

But we have packages in D, which are simular but more portable. In Unix the slash goes one way while in windows the slash goes the other. Java also uses packages for cross-portability. Why do we need directory hierarchies as well?

"Sean L. Palmer" <seanpalmer@earthlink.net> wrote in message news:afgon3$h3b$1@digitaldaemon.com...
> Any OS that doesn't support directories is going to have serious
problematic
> issues as a development platform.  It's ok for the target platform not to support directories.  Some embedded systems may not even have an OS or filesystem at all..  But the development platform *MUST* support directories.  This is 2002 dammit.
>
> Sean
>
> "Martin M. Pedersen" <mmp@www.moeller-pedersen.dk> wrote in message news:aff9o4$1n7m$1@digitaldaemon.com...
> > Hi,
> >
> > "Sean L. Palmer" <seanpalmer@earthlink.net> wrote in message news:afek1t$pev$1@digitaldaemon.com...
> > > You know what?   SCREW OS/390.
> >
> > You might not care about portability, but it is a primary concern to me.
> At
> > work, we develop software to whatever platforms the customers are using,
> and
> > we don't expect the customers to change platform to whatever is
supported
> by
> > our tools. Instead we have to select our tools, such as compilers and languages, to fit the customers needs. OS/390 is big in big businesses
> such
> > as the financial sector, and to address such markeds, you have to
support
> > it. C/C++ supports wierd platforms like this very fine, and so should
any
> > viable successor.
> >
> > Regards,
> > Martin M. Pedersen
>
>
>

"Sean L. Palmer" <seanpalmer@earthlink.net> wrote in message news:afgok0$h31$1@digitaldaemon.com...
> I'm ok with forward slashes, they're the "de facto" standard path
separator
> for every OS except windoze.
>
> Sean
>

Unfortunately Windows is the de facto standard operating system for every consumer computer. And that's a lot!

Personally I do not see why all OS'es, Windows as well
as all the others don't just make both characters valid?

However, C/C++ allow forward slashes in their includes
and it works perfectly, also on Windows. So this shouldn't
be a problem.


--
Stijn
OddesE_XYZ@hotmail.com
http://OddesE.cjb.net
_________________________________________________
Remove _XYZ from my address when replying by mail

"C.R.Chafer" <blackmarlin@nospam.asean-mail.com> wrote in message
news:afeolg$tnn$1@digitaldaemon.com...
<SNIP>
>
> Agreed, but please please please do not use back slashes (use forward slashes instead, or colons).  The backslash key on each of my 6 keyboard
is
> in a different place - and on one it is completely absent.
>
> C 2002/6/27


So buy a decent keyboard!  ;)


--
Stijn
OddesE_XYZ@hotmail.com
http://OddesE.cjb.net
_________________________________________________
Remove _XYZ from my address when replying by mail

Hi,

"Sean L. Palmer" <seanpalmer@earthlink.net> wrote in message news:afgon3$h3b$1@digitaldaemon.com...
> Any OS that doesn't support directories is going to have serious
problematic
> issues as a development platform.

Other OS'es have other concepts, and might support development very well. This is eg. the case with OS/390. I'm haven't worked on such big iron myself, but I have part of a development group writing software being compiled on it.

> But the development platform *MUST* support directories.  This is 2002
dammit.

You can expect any platform to support modules and packages, but it might be implemented differently. You cannot, however, expect to always being able to address directories using a Microsoft or UNIX syntax.

Regards,
Martin M. Pedersen