comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: Machine Specific Code
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Re: Machine Specific Code [message #73134] Mon, 25 October 2010 19:31
wlandsman is currently offline  wlandsman
Messages: 743
Registered: June 2000
Senior Member
On Oct 25, 8:30 pm, Ben Tupper <ben.bigh...@gmail.com> wrote:

> IDL> help, !version,/str
> ** Structure !VERSION, 8 tags, length=104, data length=100:
>     ARCH            STRING    'x86_64'
>     OS              STRING    'darwin'
>     OS_FAMILY       STRING    'unix'
>     OS_NAME         STRING    'Mac OS X'

Interestingly, there are still 12 procedures in the V8.0 ITTVIS
library distribution (e.g. write_gif.pro) that test for !VERSION.OS EQ
'MacOS'. These go back to the pre- Mac OS X days (pre- 2001) when
the Mac OS was not Unix-based, and there were a much larger number of
difference between Mac IDL and IDL on other operating systems. I
suspect that these procedures still work with current Macs, because
after not recognizing !VERSION.OS EQ 'darwin' they will default to
Unix.

--Wayne
Re: Machine Specific Code [message #73135 is a reply to message #73134] Mon, 25 October 2010 18:05 Go to previous message
penteado is currently offline  penteado
Messages: 866
Registered: February 2018
Senior Member
Administrator
On Oct 25, 9:54 pm, David Fanning <n...@dfanning.com> wrote:
> I can never find this in the IDL documentation. Maybe I'll write
> it down somewhere. How does one search for IDL running on
> a Mac in, say, a CASE statement? I presume a Mac is in
> the UNIX OS family, but if I wanted to tell a Mac from
> a LINUX or Sun box I would do... what?
>
> Could someone provide me with the contents of
> !Version for a Mac and maybe a Sun machine?

It is not what you asked for, but in case anyone comes here looking
for the contents of !version in Linux (64-bit):

ARCH STRING 'x86_64'
OS STRING 'linux'
OS_FAMILY STRING 'unix'
OS_NAME STRING 'linux'
RELEASE STRING '8.0'
BUILD_DATE STRING 'Jun 18 2010'
MEMORY_BITS INT 64
FILE_OFFSET_BITS INT 64
Re: Machine Specific Code [message #73137 is a reply to message #73135] Mon, 25 October 2010 17:49 Go to previous message
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
Ben Tupper writes:

> IDL> help, !version,/str
> ** Structure !VERSION, 8 tags, length=104, data length=100:
> ARCH STRING 'x86_64'
> OS STRING 'darwin'
> OS_FAMILY STRING 'unix'
> OS_NAME STRING 'Mac OS X'
> RELEASE STRING '7.1'
> BUILD_DATE STRING 'Apr 21 2009'
> MEMORY_BITS INT 64
> FILE_OFFSET_BITS
> INT 64

Thanks, Ben. :-)

Cheers,

David


--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
Re: Machine Specific Code [message #73138 is a reply to message #73137] Mon, 25 October 2010 17:30 Go to previous message
ben.bighair is currently offline  ben.bighair
Messages: 221
Registered: April 2007
Senior Member
On 10/25/10 7:54 PM, David Fanning wrote:
> wlandsman writes:
>
>> I find this also -- so it looks like for Macs we can avoid the
>> flashing to get the maximum useable image area, and that a program
>> GetRealScreenSize() should have separate branches for Mac, Windows,
>> and Linux.
>
> I can never find this in the IDL documentation. Maybe I'll write
> it down somewhere. How does one search for IDL running on
> a Mac in, say, a CASE statement? I presume a Mac is in
> the UNIX OS family, but if I wanted to tell a Mac from
> a LINUX or Sun box I would do... what?
>
> Could someone provide me with the contents of
> !Version for a Mac and maybe a Sun machine?
>

IDL> help, !version,/str
** Structure !VERSION, 8 tags, length=104, data length=100:
ARCH STRING 'x86_64'
OS STRING 'darwin'
OS_FAMILY STRING 'unix'
OS_NAME STRING 'Mac OS X'
RELEASE STRING '7.1'
BUILD_DATE STRING 'Apr 21 2009'
MEMORY_BITS INT 64
FILE_OFFSET_BITS
INT 64
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Least Cost Path using Dijkstra's Algorithm
Next Topic: POLY_2D shift

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 15:11:01 PDT 2025

Total time taken to generate the page: 0.00711 seconds