On 11/17/11 10:00, MacArthur, Ian (SELEX GALILEO, UK) wrote:
>>      Any #include's for FLTK stuff should be '#include <FL\bla.H>',
>>      which is why you don't need (or want) the trailing \fl when
>>      telling the compiler where to find fltk's include headers.
> 
> And of course, what I'm sure Greg meant to say was that it should really
> be:
> 
>   #include <FL/bla.H>
> 
> (note slash direction!) [..]

        LOL, yes, the curse of backslashes.. sorry.

        Was doing a bit of windows stuff just before sending
        that msg, and my muscle memory remained in 'backslash mode'.

        One day, Microsoft will understand their kernel understands both
        fronts and backs, and adjust their front end tools accordingly.

        I would have thought the new 'powershell' would be their big
        opportunity to rid us of the curse.. at least you can type
        fronts in commands now, but last I looked their tab completion
        turns fronts into backs.. so apparently not.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to