Changeset 1921

Show
Ignore:
Timestamp:
04/07/08 04:06:42 (9 months ago)
Author:
gary
Message:

merge R1920, LOCAL_DATA_PATH changed to CLOUDY_DATA_PATH

Location:
branches/c08_branch/source
Files:
4 modified

Legend:

Unmodified
Added
Removed
  • branches/c08_branch/source/cpu.cpp

    r1824 r1921  
    208208 
    209209        /* if the environment variable was not set, the default set in path.h takes effect */ 
    210         string chSearchPathRaw = ( path != NULL ) ? string( path ) : string( LOCAL_DATA_PATH ); 
     210        string chSearchPathRaw = ( path != NULL ) ? string( path ) : string( CLOUDY_DATA_PATH ); 
    211211 
    212212#       ifdef _WIN32 
     
    490490                        fprintf( ioQQQ, "the most likely reason is that the path has not been properly set.\n"); 
    491491                        fprintf( ioQQQ, "Please have a look at the file path.h in the source directory.\n"); 
    492                         fprintf( ioQQQ, "Check how the variable LOCAL_DATA_PATH is set - "); 
     492                        fprintf( ioQQQ, "Check how the variable CLOUDY_DATA_PATH is set - "); 
    493493                        fprintf( ioQQQ, "it should give the location of the data files I need.\n"); 
    494494                        fprintf( ioQQQ, "These are the files in the data download from the web site.\n"); 
  • branches/c08_branch/source/Makefile

    r1900 r1921  
    113113 
    114114cpu.o: 
    115         ${CXX} ${CXXFLAGS} -c -DLOCAL_DATA_PATH=\"${CDP}\" $< 
     115        ${CXX} ${CXXFLAGS} -c -DCLOUDY_DATA_PATH=\"${CDP}\" $< 
    116116 
    117117# an explicit -O0 is needed for some compilers like icc 
  • branches/c08_branch/source/path.h

    r1817 r1921  
    1111 * The location of these data on your system is specified by  
    1212 * 
    13  * #define LOCAL_DATA_PATH "XXXX"  
     13 * #define CLOUDY_DATA_PATH "XXXX"  
    1414 * 
    1515 * below, so the code is set up so that data will be automatically 
     
    2222 * The data path can also be set by the CLOUDY_DATA_PATH environment 
    2323 * variable, but it is generally easier to provide the permanent 
    24  * location at compile time by editing LOCAL_DATA_PATH below. 
     24 * location at compile time by editing CLOUDY_DATA_PATH below. 
    2525 */ 
    2626 
    2727/* The value below will be superseded if 
    2828 * specified by a compiler argument */ 
    29 #ifndef LOCAL_DATA_PATH  
     29#ifndef CLOUDY_DATA_PATH  
    3030 
    3131/*  
     
    3636 * can enter as many paths as you like. One example could be: */ 
    3737 
    38 #define LOCAL_DATA_PATH "/usr/local/cloudy/data:/home/user/cloudy/data" 
     38#define CLOUDY_DATA_PATH "/usr/local/cloudy/data:/home/user/cloudy/data" 
    3939 
    4040 
     
    4444 * NB - note that the backslash "\" always needs to be typed twice, as shown below: */ 
    4545 
    46 // #define LOCAL_DATA_PATH "c:\\projects\\cloudy\\data;c:\\users\\gary\\data" 
     46// #define CLOUDY_DATA_PATH "c:\\projects\\cloudy\\data;c:\\users\\gary\\data" 
    4747 
    4848/* The // makes the above line of code a comment 
  • branches/c08_branch/source/vs.txt

    r1799 r1921  
    33set path 
    44project / trunk properties / c/c++ / preprocessor / preprocessor definiation - at after ;    
    5 LOCAL_DATA_PATH="\"c:\\projects\\cloudy\\trunk\\data\\\\\"" 
     5CLOUDY_DATA_PATH="\"c:\\projects\\cloudy\\trunk\\data\\\\\"" 
    66 
    77inline functions - use even in debug - factor of 2 speedup: 
     
    2727in an error and a failed compile. You can also manage this from your code by  
    2828including a header file listing all the rules and their default state. You  
    29 can then upgrade warnings to errors or disable warnings using the #pragma directive. 
     29can then upgrade warnings to errors or disable warnings using the #pragma  
     30directive. 
    3031 
    3132================================ 
     
    4243and how it was called. Instrumentation involves inserting new code that  
    4344reports back the state of the application as it executes. As such it is much  
    44 more intrusive, but instrumentation profiling does illicit more information than sampling. 
     45more intrusive, but instrumentation profiling does illicit more information  
     46than sampling. 
    4547 
    4648Application performance has become a major issue today. To help developers get an