gcc-coco-os-9 — For discussing OS-9 development for gcc

[Gcc-coco-os-9] FASD project: Online survey launched

[<ben...@id...>]

Dear Open Source developer

I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate.
You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it.

With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development.


With many thanks for your participation,
Benno Luthiger


PS:
The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/.
We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list.

_______________________________________________________________________

Benno Luthiger
Swiss Federal Institute of Technology Zurich
8092 Zurich

Mail: benno.luthiger(at)id.ethz.ch
_______________________________________________________________________

[Gcc-coco-os-9] Compiler options - GNU .v.s. ANSI

[John E. M. <wb...@qs...>]

First,

Hello to who ever is also on this mailing list.


Next,

I looked up to see if GCC supports the GCC the #pragma directive.

What I found is that they do not like it, and have implemented a 
__attribute__(x) feature.

They are providing limited #pragma for compatability with source code 
meant for other platforms.


It seems to me the best way to implement this for code that you would 
want to be able to build on both the COCO and other plaforms would be to 
use a macro structure like:

#ifdef __6809
#define direct __attribute__(direct)
#else
#define direct
#endif

direct int foo;


Normally on an ANSI compliant compiler, such an attribute would be 
defined with a similar sequence:

#ifdef __COMPILER_NAME
#ifdef __6809
#pragma section_name save
#pragma section_name ".direct."
#endif
#endif

int foo;

#ifdef __COMPILER_NAME
#ifdef __6809
#pragma section_name restore
#endif
#endif

So as you can see, the GNU way is much clearer to read than the ANSI method.

Because #pragma directives are compiler specific, they need to be 
conditionally compiled around the #pragma directives.

Theoretically a compiler should ignore #pragma directives that it does 
not understand, but there is no coordination of the namespace so it is 
possible that a compiler could misunderstand a #pragma that is not meant 
for it.

-John
wb...@qs...
Persoanl Opinion Only