[06 Feb 2010] Compile form multi-OS question...

Contains all messages from the Hollywood mailing list between 01/2006 and 08/2012
Locked
User avatar
Tuxedo
Posts: 355
Joined: Sun Feb 14, 2010 12:41 pm

[06 Feb 2010] Compile form multi-OS question...

Post by Tuxedo »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Sat, 06 Feb 2010 15:37:50 -0000

Hi! I wonder if there's a way or better a possibility to get that feature implemented in the future:

Include in the code some TAGs that the compiler will use to compile for a specified OS... So in single source we can write the code that can work for every OS without will change llittle tihngs(like the requester type availabel only for OS4.x atmand not supported in aother OSes) every time we have to port our code to another OS... Something like:

[OS4.x] [/OS4.x]

or

[Win32] [/Win32]

So we can easly write same routine command with little changes for every use we need...

What do you think about?

Simone.
Simone"Tuxedo"Monsignori, Perugia, ITALY.
alfkil
Posts: 26
Joined: Sun Feb 14, 2010 1:54 pm

[06 Feb 2010] Re: Compile form multi-OS question...

Post by alfkil »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Sat, 6 Feb 2010 17:16:33 +0100

I think this would be great, I have really been looking for such a feature for a long time!

- Alfkil
User avatar
airsoftsoftwair
Posts: 5914
Joined: Fri Feb 12, 2010 2:33 pm
Location: Germany
Contact:

[09 Feb 2010] Re: Compile form multi-OS question...

Post by airsoftsoftwair »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Tue, 09 Feb 2010 13:41:25 +0100
Hi! I wonder if there's a way or better a possibility to get that feature implemented in the future:

Include in the code some TAGs that the compiler will use to compile for a specified OS... So in single source we can write the code that can work for every OS without will change llittle tihngs(like the requester type availabel only for OS4.x atmand not supported in aother OSes) every time we have to port our code to another OS... Something like:

[OS4.x] [/OS4.x]

or

[Win32] [/Win32]

So we can easly write same routine command with little changes for every use we need...

What do you think about?
Something like this is planned for the preprocessor, but more in the way of:

Code: Select all

@IFDEF __WIN32__

@ENDIF
etc.
Locked