[Omake] SVN Commit: OMake Build System (Rev. 12510)

[Aleksey Nogin]

On 09.11.2007 12:58, Jason Hickey wrote:

>> My proposal would be to:
>>
>> 1. Add:
>>
>> .PUBLIC: var1 var2 ...
> 
> We have talked about this before, but I don't remember the exact reason.
> 
> Why is
> 
>    .PUBLIC: foo
> 
> better than
> 
>    declare public.foo?

The new syntax is a lot less verbose if you declare many variables at 
once. It is way more verbose if you want to spread the variables over 
multiple lines (for SVN-friendliness, shorter lines that do not wrap in 
the editor, etc).

The new syntax does force using separate declarations for different 
variables kinds, but this is probably a good thing.

>>   - The "public./private." sections. As we have often discovered it is
>> way too easy to do things wrong in them.
> 
> Can you take a look at lib/parse/C/Parse.om first?  I suppose it can all 
> be transformed, but I'm not convinced it would be better.

There are about 115 public/private variables in that file; I believe it 
would not be that bad to have to declare them upfront. The this.const. 
blocks are a bigger issue in that file. BTW, do they need to be 
this.const., or would just const. be sufficient? I would imagine that 
const. block would not be a problem (can they be interpreted as simply 
adding a modifier on the variables being declared, but not affecting the 
previously declared variables?)

Another possibility would be to introduce a usual ignore/warn/error kind 
of variable defaulting to "error" (or to "warn" if we want to allow a 
transition period). This way one could set it to "ignore" in files like 
C/Parse.om - essentially enabling an "expert" mode.

Aleksey
-- 
Aleksey Nogin, Research Scientist
Advanced Technologies Department, Information & System Sciences Lab
HRL Laboratories, LLC, Malibu, CA