Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[XXXXYYYY]

is java even regular

Generalizations and all that but no programming languages are regular.

Not quite true.

Black, for example, is just { |#|\n}* (where \n represents a newline and # represents any non-whitespace character (I didn't want to write them all in, and it's not like it matters syntactically anyway, as they're all treated identically)).
I'm pretty sure it qualifies, as the rule for it is just a couple unions and a Kleene star of the three regular languages (as they are singletons) { }, {#}, and {\n}, which I'm pretty sure means it in turn is a regular language.

I mean, it's not very useful, but it is still technically a programming language, even if an esoteric one.

Though I'm just being kinda pedantic, so it's safe to disregard me.

[Skyrunner]

Reminds me of a snippet from a login;logout article..

it went along the lines if

l. Here’s a life tip: when you’re confused about what
something is, DON’T EXECUTE IT TO DISCOVER MORE
CLUES. This is like observing that your next-door neighbor
is a creepy, bedraggled man with weird eyes, and then you start
falling asleep on his doorstep using a chloroform rag as a pillow,
just to make sure that he’s not going to tie you to a radiator and
force you to paint tiny figurines. Here’s how your life story ends:
YOU ARE A PAINTER OF TINY FIGURINES.

[Dutrius]

Does anyone know if you can use get and set properties on arrays in C#?

Infact, can use use get and set on enumerations as well?

[jaked122]

Does anyone know if you can use get and set properties on arrays in C#?

Infact, can use use get and set on enumerations as well?

What do you mean? Are you overriding an array? Otherwise no, you shouldn't set the properties that I can think of. It would help to see what you're trying to do.

Enumerations aren't a datatype with instances. It's just a list of acceptable values for a certain artificial type, usually just aliases and typechecking sugar for constants.

[Dutrius]

Does anyone know if you can use get and set properties on arrays in C#?

Infact, can use use get and set on enumerations as well?

What do you mean? Are you overriding an array? Otherwise no, you shouldn't set the properties that I can think of. It would help to see what you're trying to do.

Enumerations aren't a datatype with instances. It's just a list of acceptable values for a certain artificial type, usually just aliases and typechecking sugar for constants.

Fair enough. Just wanted to see if I could use getters and setters instead of writing regular methods to do it.

[Rose]

You can override the [] operator, and you can have an accessor that returns an entire array, but you can't have an accessor that takes an index.

So if you have a class foo, you can define a foo[3] or a foo.array that returns an entire array, but you can't have foo.bar[2] and put your own separate logic for that.

You can have multiple [] operators though if each takes a different type. I use that for my stuff, where foo[int] and foo[string] work differently.

[Reelya]

In C# enumerations are in fact treated like a data type, they're just an int obviously under the hood but making instances of them is how you roll in C#. So they should have the same get;set; interface as any other variable.

[jaked122]

In C# enumerations are in fact treated like a data type, they're just an int obviously under the hood but making instances of them is how you roll in C#. So they should have the same get;set; interface as any other variable.

I believe you are thinking about Java. Otherwise Microsoft doesn't know about it


Unless of course, you happen to mean that you can set instances of the enums, which wasn't what I responded to.

[Reelya]

"Enumerations aren't a datatype with instances."

Is what you wrote, and what I responded to. Well, they are as much a datatype with instances as other primitive types are, and the rules are basically the same with getters/setters for them, so you can make an enum, create an instance of that in your class and use get/set:

Code: [Select]

public class Date
{
    public enum Months
    {
        jan, feb, mar, etc
    }
public class Date
{
    public enum Months
    {
        jan, feb, mar, etc
    }

    public Months month { get; set; } = Months.jan;
}

}
Which seems perfectly acceptable behavior. You'd write e.g. "date.month = Months.feb" to set the date.

[jaked122]

I meant that they don't have properties like those in java. You're right. They do have instances, but they are not reference based, like those in java, but instead primitives.


You are correct, I think I misunderstood.

[Dutrius]

"Enumerations aren't a datatype with instances."

Is what you wrote, and what I responded to. Well, they are as much a datatype with instances as other primitive types are, and the rules are basically the same with getters/setters for them, so you can make an enum, create an instance of that in your class and use get/set:

Code: [Select]

public class Date
{
    public enum Months
    {
        jan, feb, mar, etc
    }
public class Date
{
    public enum Months
    {
        jan, feb, mar, etc
    }

    public Months month { get; set; } = Months.jan;
}

}
Which seems perfectly acceptable behavior. You'd write e.g. "date.month = Months.feb" to set the date.

Thanks. This was exactly what I wanted to know.

[Shadowlord]

P.S. You can also write

Code: [Select]

public Months month { get; private set; } = Months.jan;

Then only that class can use the setter. Or, use protected, and subclasses can use it too.

[3man75]

Finished my C++ class with a..C. I have to say I'm not sure if I earned it after bombing two tests towards the end but what I get is what I get.

I'd like to give this to all those who helped me and pray to a merry christmas to all.

Spoiler (click to show/hide)

http://4pawsforability.org/wp-content/uploads/2013/07/DSC_0151.jpg

NOTE: SPOILER tag leads to another site but it should show an adorable dog with a sign.

[Orange Wizard]

Spoiler (click to show/hide)

FTFY

[Gatleos]

Man, it's surprisingly hard to add following behavior for entities pathfinding on a connected graph. Each node on the graph can only hold one entity, so when the entities are pathfinding I need to set nodes which already contain entities as impassible. This means that an entity which is trying to follow one node behind another keeps "bumping into it", but only if the following entity takes its turn before the followed entity.

The obvious solution is to set an entity's current node to passable if it's going to be moving this turn, but whether an entity will move could depend entirely on a third entity which may or may not block its path depending on whether that entity has moved already and AUGH

This is reminding me of network programming