- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Jun 2024 11:32:49 +0000
- To: public-css-archive@w3.org
> By the time you get to the first value, you know what your separator is, so there’s no ambiguity in if(style(...), foo, bar). urgh, i really wouldn't want `if(style(...); foo, bar; ...)`. Gives me aesthetic icks. > In general "if" means branching but here we are not branching, we are "selecting" a value depending on an expression, correct? This is equivalent to an if/elif/elif/else chain. Whether an `if` is a *statement* (just executing code) or an *expression* (evaluating to some value) varies between languages. In the context where this exists in CSS, it's clearly an expression-level thing; the equivalent of an `if` "statement" would be [an `@if` rule](https://drafts.csswg.org/css-conditional/#when-rule) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10064#issuecomment-2165393314 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 June 2024 11:32:50 UTC