anyway maybe not useful at moment but in future.

Hey, so it was more just a conversation about why haxe (by default) doesnt do things that way in the first place, i dont think that haxe should throw exceptions "all the time" for anything (like making sure commas are in the right place etc), i think, as you say, thats a job for a NumberTools class or whatever - however, i do think that by default exceptions would ideally be thrown for "123xyz" or "1.2.3"... but its kinda academic as it aint gonna happen, and once you know, well, you know so its not a big deal 🙂

If you have a list of pass/fail tests then please do add an issue, and I can tweak it to provide what you think is ideal. If you find target issues/bugs etc... I think something like this could be added to StringTools, since it would provide robust numerical check - the current holes can be justified.. but having a StringTools fall back would make language comparisoms better in Haxe's favour. Haxe is all about robust and if this is fleshed out it helps. I guess it really needs some optional parameters like accept ',' allow 'scientific exponents' , 'allow space separations, limit hex ( Utf32 or RGB length perhaps ), options to convert binary etc...

Also it could allow runtime of some of the proposed changes for number formats.

I am guessing at the moment they have to be ignored.

But I think something like this would provide runtime support when parsing xml/json into haxe.

obviously it may add cost so some formats would need explicit passing perhaps via a static inline constructor.

Yer tricky to think about the best form. But certainly my code will stop use of 123xyz and 1.2.3

I think this could be useful Evolution via an addition to StringTools ?? But would need to be super robust and some decisions made before trying to submit otherwise it stands no chance.

anyway sorry in wrong channel.

Does anyone know why the view class is not included in concnut?

I'm learning coconut

#570655075660464140 and #565569107701923852 aren't the same thing

Well I'm trying to find a way to use React in Heaps and I'm still looking around for tutorials 🤓

Would it be possible to write a custom rule parser? I would love to write a less parser (if only to avoid depending on it's npm package)

or just variables to be supported

I only use less for variables

that regex parser looks interesting 😅

I could try to write a css parser with my (weak) knowledge of parsing

Well I can defo generate a style sheet

nothing stopping me there

😵 I'm not writting out all of these properties

What is the vertical & horizontal spacing in the

Style

class? there is no (spec compliant) css property for that

there is loads of stuff in haxeui css that isnt css compliant... its not really meant to be "compliant"

Is everything in the

Style

class able to be defined as a property?

essentially... although there are shorthands for alot of it

lord 😅

I just wanted to write a custom parser

but now I have to deal with all this

i bet that isnt even a quarter of the css your browser understands